Agimon

Core concepts

Five entities carry everything Agimon does. This page defines each one and the fields that matter, so the guides can use the words without redefining them.

Product

One product the company operates. Products are scoped to the organization, so the portfolio is every product the company runs rather than a workspace you switch between.

Fields that matter

name, summaryWhat the product is called and a short description of it.
stageWhere the product sits in its lifecycle. Defaults to idea.
postureHow the company is currently treating it. Defaults to maintain. A focus decision writes this field.
monthly_budget_minorMonthly budget in minor currency units, so amounts stay exact. Defaults to 0. A budget decision writes this field.
currencyCurrency for the budget. Defaults to USD.
archivedRetires a product from the active portfolio without removing its evidence or decisions. Defaults to false.

Weekly Snapshot

One week of evidence for one product. A product can hold only one snapshot per week, which is what makes evidence freshness comparable across the portfolio.

Fields that matter

product_idThe product this week of evidence belongs to.
week_startThe week the evidence covers. Unique per product, so a week cannot hold two competing records.
submitted_atWhen the snapshot was submitted, which is what freshness reads.

Area Signal

One area of evidence inside a weekly snapshot. Every snapshot carries exactly three areas: product, sales, and marketing, each appearing once. Metric name, target, and unit are copied onto the signal, so later KPI changes do not rewrite past evidence.

Fields that matter

areaOne of product, sales, or marketing. Unique per snapshot.
focus_textWhat the area was working toward that week.
current_valueThe KPI value observed for the week.
metric_name_snapshotThe KPI name as it stood that week, copied from the metric definition.
target_value_snapshotThe target as it stood that week.
unit_snapshotThe unit as it stood that week.
trendOne of up, down, or flat.
statusOne of populated, not_applicable, or missing. Defaults to populated, so a gap is recorded rather than left ambiguous.
noteFree text for anything the numbers do not carry.

Metric Definition

The current focus and KPI target for one area of one product. Exactly one definition per product and area. It is the standing target; the weekly signal is what actually happened.

Fields that matter

product_id, areaThe product and area this target belongs to. Unique together.
focus_textThe standing focus for that area.
nameThe KPI name, such as activation rate.
target_valueThe number the area is aiming at.
unitThe unit the target is expressed in. A metric decision writes name, target, and unit.

Decision

One recorded company call. A decision is exactly one of focus, budget, or metric, and recording it applies its single effect to live company state in the same action. Decisions are never edited; a later decision supersedes an earlier one and both stay readable. There is no draft or approval state on the record.

Fields that matter

typeOne of focus, budget, or metric. The type determines which single field the decision writes.
statementThe call itself, in one sentence.
rationaleThe reasoning behind it, which is what survives for whoever reads it later.
effective_dateWhen the decision takes effect.
review_dateOptional date to revisit the call.
changeThe typed effect. focus carries the product and its focus, budget carries the monthly budget and currency, metric carries the area, KPI name, target, and unit.
supersedes_decision_idThe earlier decision this one replaces, when it replaces one.
product_idOptional, and carries no foreign key, so the decision log stays readable after a product is gone.