Compute run page
one per measured run · runs: 2026-09-05-gq-compute, 2026-09-06-j2 (medium vs xhigh), e1 windows ×3; receipts in domains/compute/runs/
The page, rendered
this template composed from real data, inside the CRM shellOpen it full size: /t/U19/example/ · data: example.json · schema.json
Why this template exists
his words · the reading · the ceilings-
His words 0
verbatim, from
00_AGENT_ZERO/source/— never paraphrasedNo verbatim source on this page. -
Reading authored by the seat
A God Question without runs is opinion; the J2 '4×' claim survived a night because no page showed ratio 1.00× with effort null. Receipts must be visible.
Readers. Human: did it work, what did it cost. Agent: the preregistration to repeat and the receipt shape to emit.
- What was tested?
- What was applied vs requested?
- What are the numbers, with n?
- What decision does it change?
-
What this page may claim
Claim ceilingNumbers only from receipt files; requested vs applied shown separately.Data it rendersdomains/compute/runs/.PrivacyPublic.Empty stateNo acceptance.json → 'unfinished run'.Agent entrydomains/compute/runs/<run>/README or preregistration.json
Content contract
his twelve, 18:19; '—' means this family carries nothing thererun id
GQ · date · host
what we expected
—
—
—
—
verdict
seat
arms
—
prereg · arms · numbers · verdict
Sections, in order · where it lives
- 1preregistration (what we expected)
- 2arms + effort applied
- 3tokens in/out per arm, ratio with n
- 4acceptance verdict
- 5runtime audit
- 6what it changes (decision)
- Lives at
- /runs/
/ under its God Question - Instances
- one per measured run
- Count
- runs: 2026-09-05-gq-compute, 2026-09-06-j2 (medium vs xhigh), e1 windows ×3; receipts in domains/compute/runs/
- Renders
- domains/compute/runs/
/{preregistration,run,acceptance,runtime-audit}.json, events.jsonl, metadata.json (effort applied), receipts - Theme
- research = focus blue
- Rail
- U0
- Needs
- —
- Links out
- U5 U16 U17
- Links in
- U5 U9
What to rob
presentation only; licences keptFrom the Action Model sites (built from real data)
Components, exact locations (Luna inventory)
| Component | Where | Renders | How | Quality |
|---|---|---|---|---|
| Actionist grouped registry rail | system-map/nav.js:74-123,125-174; system-map/nav.css:27-177 | page-registry.json sections/pages, status, descriptions and route IDs | Copy nav.js/nav.css and feed a registry JSON with sections and pages. | good — complete persistent grouped navigation and active-route state |
| Hero plus status panel | system-map/index.html:67-80; system-map/part-page.css:8-15; registry.css:3-12; industry.css:1-30; state.css:15-72; blueprint/index.html:246-258 | Title, thesis/lede, current posture, status, date, and source/generator metadata | Copy the two-column hero/status structure and feed title, summary, posture, and provenance fields. | good — consistently separates narrative from current state |
| Metric strip | system-map/index.html:81-84; system-map/part-page.css:40-43,72-75; blueprint/index.html:328-335; industries/law_firms/index.html:21; state/index.html:19-27 | Counts such as mapped parts, sources, observed slots, repos, cells, and open gaps | Copy metric cards and bind each value to a named registry or record count. | good — compact quantitative orientation with semantic labels |
| Flow / process steps | system-map/index.html:93-104; blueprint/index.html:57-60,487-492; live block-runtime SVG/sections | Ordered stages from discovery through composition, runtime, and learning | Copy flow-step styling and feed ordered stage objects with labels and descriptions. | good — communicates sequence without requiring a chart library |
| Status badge/chip | site/index.html:101-102; system-map/part-page.css:37-39,58-59; nav.css:151-153; blueprint/index.html:39-42 | Research state, maturity, qualification, sparse/observed posture, and live/open state | Copy chip CSS and feed an explicit status vocabulary, never inferred prose. | good — status is visually prominent and remains text-readable |
| Evidence/source table | RESEARCH-PACK.html:166-176,233-264,358-395; part-page.css:32-39,50-59; industry.css:52-60; docs.css:54-59; state/index.html:220-240; blueprint/index.html:335,393,427 | Rows of sources, contributions, limits, repositories, evidence classes, observed slots, statuses, and provenance paths | Copy scrollable table wrappers and define a record-specific column schema. | good — explicit provenance columns prevent summary-only displays |
| Scrollable dataset search header | system-map/part-page.css:46-57; generated P01 dataset markup and inline search behavior | Dataset title/description plus client-side query against preserved research rows | Copy dataset-head/input and bind filtering to table rows by text content. | good — keeps large evidence packets inspectable without pagination |
| OSS admission funnel | site/index.html:431-441; generate-state-page.mjs:71-112; state.css:74-160 | Merged candidates, bounded reviews, held evidence, rejected, admitted, and stage counts | Copy funnel rows/bar CSS and feed ordered stage count objects. | good — communicates attrition and zero states without hiding them |
From the 21st.dev bank (his picks, his notes)
another performance benchmark card, might be usefulShaan · ui-bank note
Rob this performance-benchmark-card composition for compute run page (receipts, ratios).
could be a really cool animation if we use it well, donut chart card. Could be used somewhere on the operator dashboardShaan · ui-bank note
Rob this donut-chart composition for compute run page (receipts, ratios).
does this activity mini chart actually work? It does. Banging. We needed some graphs. This is going to be used in the operator thingShaan · ui-bank note
Rob this mini-chart composition for compute run page (receipts, ratios).
nice different stat widgetShaan · ui-bank note
Rob this stats-widget composition for compute run page (receipts, ratios).
Bank gaps: receipt schema and reproducibility links need bespoke data
Done when
facts have a receipt; the rest is proposaltemplates/U19/template.html composes parts; example.json is real data.https://github.com/sisodias/siso-shell/tree/main/templates/U19- Counts on this page come from plan/templates.json (6 Sep 18:36), not from a live registry query.
- 'Built' means the template folder exists and renders; the done-when line is the acceptance.

