Record a decision
Turn a week of evidence into one typed call that applies to live company state. Run this whenever the portfolio makes a call obvious.
Goal
One decision in the ledger, of type focus, budget, or metric, with its single effect already applied to live company state.
Steps
Choose the type
A decision is exactly one of three types, and the type determines the one field it writes. If a call needs two of these, it is two decisions.
Write the statement and the reasoning
The statement is the call in one sentence. The rationale is optional in the schema but is the part that survives for whoever reads the ledger in six months, including your agents.
Set the dates
effective_date is when the decision takes effect and is required. review_date is optional and marks when you intend to revisit the call.
Record it through your agent
Decisions are written over MCP with record_decision. There is no HTTP write route; the REST surface is read-only. The call requires an idempotencyKey, so a retry cannot record the same call twice.
Confirm the effect landed
Recording the decision applies its effect in the same action. Check the product: a focus decision has changed its posture, a budget decision its monthly budget, a metric decision the KPI for that area.
Worth knowing
One decision, one applied effect
The effect is applied atomically with the record. There is no separate step that pushes the change into live state afterwards.
Recorded means live
A decision is not stored as a draft or a proposal awaiting sign-off. It exists in the ledger and its effect is applied. If it turns out to be wrong, supersede it.