Decision types and applied effects
Every decision is exactly one of three types. The type determines the shape of its change payload and the single field it writes to live company state.
focus
Sets how the company is treating a product. Writes product.posture.
kindThe literal focus.
productIdThe product the decision applies to.
focusThe posture being set on that product.
budget
Sets what a product costs per month. Writes product.monthly_budget_minor and product.currency.
kindThe literal budget.
productIdThe product the decision applies to.
monthlyBudgetMinorThe monthly budget in minor currency units, so amounts stay exact.
currencyThe currency the budget is expressed in.
metric
Sets the KPI target for one area of a product. Writes the metric definition for that product and area.
kindThe literal metric.
productIdThe product the decision applies to.
areaOne of product, sales, or marketing.
nameThe KPI name.
targetValueThe target being set. Nullable.
unitThe unit the target is expressed in. Nullable.
Rules that hold for every type
one effectA decision applies exactly one change. A call that needs two effects is two decisions.
applied on recordThe effect lands in the same action that records the decision. There is no separate apply step.
no status columnThe decision table has no status, draft, or approval field. A decision exists and is applied, or it does not exist.
supersedes_decision_idThe only way to change a call. Records a new decision pointing at the one it replaces, leaving the original intact.