Skip to content

I3356 — The site's economics page publishes the scorecard from the generated summary, failed and inconclusive tests and every loss in the same rows as passed ones, each linking its records

Carry the scorecard into the summary majordomus generate economics writes: a proof field in docs/generated/economics.{json,yaml}, a section in economics.md written by economics::report, the field in share/schemas/generated/economics-summary.schema.json, and rows in site/templates/economics.html from the data scripts/generate-site-data already copies. Each row carries its protocol, status, reason, counted sample against minimum, effect with interval and method, losses, the claim it settles, and links to its counted and uncounted records (trial records, runs, the T3 window record). Add a sentence to site/content-src/economics.md saying where the rows come from.

BLOCKED wave 4 · p1 · implementation profile · parallel safe

Part of the-proof-scorecard-is-published — One derived scorecard publishes every proof test's computed status, losses included, on every surface, and no value claim stands without a passed test.

Blocked. This issue cannot start until I3355 is done. The status is derived from that, not declared.

Objective

Carry the scorecard into the summary majordomus generate economics writes: a proof field in docs/generated/economics.{json,yaml}, a section in economics.md written by economics::report, the field in share/schemas/generated/economics-summary.schema.json, and rows in site/templates/economics.html from the data scripts/generate-site-data already copies. Each row carries its protocol, status, reason, counted sample against minimum, effect with interval and method, losses, the claim it settles, and links to its counted and uncounted records (trial records, runs, the T3 window record). Add a sentence to site/content-src/economics.md saying where the rows come from.

Why

The owner's report of 2026-10-19 asks that every verdict be public, losses included. The economics page already renders only the generated summary through a path whose provenance is checked. The critique found that adoption and delivery readings had no surface but raw JSON, so each row links its records.

Current state

scripts/generate-site-data:1517-1529 copies docs/generated/economics.json into the site data. site/templates/economics.html renders verdict, metrics, pairs and hypotheses. The schema's required list (economics-summary.schema.json:7) has no proof field. Case 430 drives the economics pipeline end to end.

Desired state

The built /economics/ page shows six rows; failed, inconclusive and loss rows use the same markup as passed ones; with no plan the page says so.

Scope

  • apps/majordomus-cli/src/economics/model.rs
  • apps/majordomus-cli/src/economics/report.rs
  • share/schemas/generated/economics-summary.schema.json
  • docs/generated/economics.json
  • docs/generated/economics.md
  • docs/generated/economics.yaml
  • site/data/generated/economics.json
  • site/templates/economics.html
  • site/content-src/economics.md
  • site/content/economics.md
  • test/cases/430_economics.sh

Out of scope

  • A homepage section or link
  • Restyling the page
  • /ui (I3357)

Dependencies

What waits on this

Acceptance criteria

  • docs/generated/economics.json carries proof with six rows and totals summing to six, and the schema validates it
  • Case 430 asserts one row per test with a data attribute naming its status, and a fixture with a failed test renders that row, its losses and its record links
  • With no plan the page states it and renders no empty table
  • scripts/site-check and majordomus economics check pass on the built site

Validation

  • majordomus generate --check
  • bash test/run.sh 430_economics
  • scripts/site-build
  • scripts/site-check

Evidence required

  • case_scorecard_rendered_with_losses

Evidence

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

Timeline

started
—
verified
—
completed
—

Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.

Canonical record: .ai/repo/project/issues/I3356.yaml. Read it back with majordomus plan show I3356.

Searches the titles and descriptions of every page this site publishes.