Ledger
What a full migration needs
Demand comes from PolicyEngine's production usage inventory: every output variable partners requested, weighted by the request volume of the clients that use it. Supply is what Axiom maps and executes today. The gap, ranked by unlocked volume, is the encoding roadmap.
Partner demand data is not bundled in this deployment.
Three shares, three questions. In the serving map: variables that /v1/household/us/calculate answers today. The corpus can answer: the resolver's mapped plus executable rows, which also counts rules that are encoded but not yet in the serving map. Partners at gate 4: requests from partners for whom this API covers every input and output, aligned and servable. A partner moves only on the last one.
Partners
Who can move, and what holds each one
One row per PolicyEngine partner (opaque client id). The stage is the customer's place on one ladder: 0 PE rules → 1 shadow → 2 tentative Axiom serving → 3 fully Axiom-answered (all three in Door 1, PolicyEngine's household API with Axiom underneath) → 4 cutover to this API → 5 PE path closed. It shows what the evidence supports; a manifest may declare more, and is then marked OVERCLAIMED. Stages 1–3 need Door 1 production records, which do not exist yet. Gate 4, "Door 2 covers it", is three checks on this API, each measured, not declared: covered — every variable the partner uses is served today, the outputs they ask for and the inputs they send (an unmapped output returns null; an input nothing consumes is dropped, and the answer still looks complete); aligned — their own payloads replay, and every value matches or has a named known difference; servable — every replayed case answers, inside the latency budget, next to PolicyEngine's own time on the same case. A cutover is honored only when all three hold. Hover a cell for what it measured.
| Partner | Requests | Stage evidence supports | Gate 4 · Covered inputs + outputs | Gate 4 · Aligned shapes + values | Gate 4 · Servable latency + errors | Holding it back |
|---|
Next to encode
Highest-leverage gaps
Ledger
Every demanded variable
| Variable | Served today | Encoding status | Axiom root / package | Entity | Clients | Demand weight |
|---|
Coverage map
What the map covers, and what blocks it
The supply side, one row per PolicyEngine variable the shared map (axiom-mappings) names. Note the denominator: the Migration tab counts what partners request, this counts what the map names, whether anyone asks for it or not. The two are joined further down. A variable reaches customers through two doors, each with its own stage. Door 1 is PolicyEngine's household API with Axiom rules underneath (policyengine-axiom): there it climbs unmapped → mapped → bound → shadow → on, and on needs the ledger's certification inside the program's time window, not only a status that says on. Door 2 is this API's compat endpoint: a variable in its serving maps is served. Only shadow and on run anything; mapped is a name pairing with no binding and no evidence behind it, so it is counted apart rather than shown as progress.
The coverage map is not bundled in this deployment. Regenerate it with python -m axiom_mappings export coverage --out data/coverage-map.json.
Executing
What runs or is served today, by door
Short enough to read in full. A row can be on and still carry a blocker: the stage says it serves, the blocker says what is unsettled about it. Echo marks an input asked back as an output (such as age): served, but no rule computes it. Hover a blocker count for the reasons.
| PolicyEngine variable | Program | Door 1: PolicyEngine | Door 2: axiom-api | Blockers |
|---|
Overclaimed
Where a Door 1 status says more than the evidence holds
A binding whose status says on runs as shadow until policyengine-axiom's ledger certifies it, and answers nothing outside its program's time window. Each row here is listed at the stage the evidence supports.
| PolicyEngine variable | Status says | Evidence holds | Why |
|---|
No Door 1 status claims more than its evidence.
Demand
Where the variables partners ask for actually stand
| Variable | Demand weight | Door 1 | Door 2 | First blocker |
|---|
No demanded variable carries a blocker.
Blockers
What the remaining work is
| Variable | Door 1 | Door 2 | Blocked by |
|---|
Cases
Every partner call
Each card is one real partner payload replayed against production: end-to-end latency with the engine's share, then every covered variable — Axiom against the PolicyEngine golden and live PolicyEngine, with the difference. Variables Axiom cannot compute yet are folded below each card with the exact reason.
Evidence
State of the record
The latest run in one verdict: exact means equal within one cent; expected diffs are understood and documented (e.g. PE projects unpublished FY-2027 COLA values that Axiom deliberately omits); awaiting-encoding variables have no executable Axiom package yet.
Recorder
The tape
Every published run leaves a mark: exact agreement rides the upper trace, disagreements track beneath. Hover a point for that run's counts.
No runs recorded yet — the first daily comparison starts the tape.
pens:exact matchesdisagreements
Runs
The docket
| Recorded (UTC) | Verdict | Exact / covered | Avg case |
|---|
Comparison
Between two runs
Every variable whose value or coverage changed between the selected runs.
vs CONTRACT CHANGED
No value or coverage changes between these runs.
| Case | Variable | Before | After | Parity |
|---|
Service
Right now
| Dependency | Status | Detail |
|---|
Instrumentation
Where computation time goes
Measured inside the runtime for every real calculation, accumulated across instances and deploys.
planenginenormalize
No calculations recorded yet — run one and refresh.
| Package | Runs | Avg total | Phase split |
|---|
Instrumentation
Latency by route
Busiest routes across live instances (in-memory, resets on deploy). Distribution buckets: ≤25, ≤100, ≤500, ≤2000, >2000 ms.
| Route | Requests | Avg | Distribution |
|---|