operation-convergence — After the alpha, the time from an intent to its verified satisfaction is measured from the records

✕BLOCKED 0 of 1 issues done

ready

0

blocked

1

active

0

verify

0

done

0

cancelled

0

Problem

The method's value is asserted, not measured: nothing derives how long an intent takes from its proposal to a verified verdict, or what governance and rework it cost, and the alpha's conditions are recorded only as invariants of the intent. Sources: chatgpt-majordomus:c147#7, chatgpt-majordomus:c198#15, chatgpt-majordomus:c221#4, chatgpt-majordomus:c270#8, chatgpt-majordomus:c275#25, chatgpt-majordomus:c286#21.

Outcome

Intent-to-verified-done, interventions, replans, governance time and rework are derived per intent from git history and the evidence ledger, and the with/without comparison is read from matched benchmark runs behind ADR 0082's rule.

Current state

cost-per-accepted-outcome (I0401-I0404) measures tasks, not intents, and reads BLOCKED behind execution-telemetry. The alpha's conditions (green tag commit, pre-release isolation, clean install, refusal at finish, the IDD case, compute labelled experimental) are invariants of operation-convergence carried by work outside this milestone (I2829, I2812 and cases 1024 and 3220, on branches or in the 0.30.0 top), and this milestone does not judge them.

Desired state

I3276 lands and the criterion the-method-is-measured-after-the-alpha is rebound to its test and reads current from it.

Scope

• apps/majordomus-cli/src/economics
• apps/majordomus-cli/tests/economics.rs
• docs/ECONOMICS.md

Out of scope

• Verifying the alpha conditions on the tag commit; the release seat owns that verdict
• Running the matched benchmark itself (I3133)

Acceptance criteria

• Time from intent to verified satisfaction, governance time, tokens and rework are derived for matched tasks with and without Majordomus, and published only past ADR 0082's rule

Validation

• majordomus plan validate

Risks

• The criterion stays a command placeholder until I3276 writes its test; until I3255 refuses a criterion's own explain as proof, one explain run could read it current

Issues

Each one is an execution contract with its own acceptance criteria, validation command and required evidence. The wave column is the layer of the dependency graph it sits in.

The graph

flowchart LR
    I3276["I3276<br/>The time from an intent's proposal to its verified satisfaction is derived from the records, with the interventions on the way"]:::blocked
    classDef done stroke:#16a34a,fill:#dcfce7,color:#14532d,stroke-width:2px
    classDef active stroke:#2563eb,fill:#eff6ff,color:#1e3a8a,stroke-width:2px
    classDef verify stroke:#7c3aed,fill:#f5f3ff,color:#4c1d95,stroke-width:2px
    classDef ready stroke:#0891b2,fill:#ecfeff,color:#164e63,stroke-width:2px
    classDef planned stroke:#0891b2,fill:#ecfeff,color:#164e63,stroke-width:2px
    classDef blocked stroke:#b45309,fill:#fffbeb,color:#78350f,stroke-width:2px
    classDef cancelled stroke:#6b7280,fill:#f9fafb,color:#374151,stroke-width:2px
    classDef superseded stroke:#6b7280,fill:#f9fafb,color:#374151,stroke-width:2px

Canonical record: .ai/repo/project/milestones/operation-convergence.yaml. Read it back with majordomus plan show operation-convergence.