hand-on-the-obligations

# Hand on the obligations ## What it does Writes what the signed terms owe out as work with owners and dates, so the obligations the agreement created have somebody behind them before anybody starts. ## Where it happens The agent does this in one activity across one reference process. Each one names the activity as that process words it. - **Hand On the Obligations** - `ref/prt/structure-an-alliance`, activity 16 - [Structure an Alliance](../../../../processes/partners/structure-an-alliance.md) ## What to record What each side must get, written before any shape was chosen. The shape chosen and why it beat the others considered. The money model, naming who charges the customer, who invoices whom, and who keeps what. The term and the exit, with the notice each ending needs. The economics at a version, with the assumptions and the downside case stated. Every diligence finding, priced into a term or named as a stop. The internal mandate and its walk-away terms. The term sheet at a version. Every ask the other side made, the position taken on it, and the date it closed. Every redline read against the term sheet, saying what moved and who was told. The obligation register at handover, so the work the agreement created has owners before anybody starts it. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.