Decision page
one per decision · 29 (plan/decisions.json D-1…D-29) + harness-lab DECISIONS.md
The page, rendered
this template composed from real data, inside the CRM shellOpen it full size: /t/U16/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
'You just decide all of the answers for me' (D-1…D-29) means decisions are the constitution; a future Agent Zero must be able to read them one by one with the words that caused them.
Readers. Human: what did we decide and why. Agent: the rule to obey and what would reverse it.
- What was decided, when?
- In whose words?
- What did it change?
- Is it still in force?
-
What this page may claim
Claim ceilingOnly decisions in decisions.json; a proposal is labelled proposal.Data it rendersplan/decisions.json + source/.PrivacyPublic.Empty state—Agent entryplan/decisions.json
Content contract
his twelve, 18:19; '—' means this family carries nothing thereD-NN · one line
date · in force / superseded
his words
→ modules, projects, plays it gates
—
—
—
in force
—
decided · reaffirmed · reversed
—
decision · words · effects · reversal
Sections, in order · where it lives
- 1the decision in one line
- 2his words (verbatim)
- 3what it changed (files, modules)
- 4what reverses it
- 5superseded by
- Lives at
- /decisions/ index + /decisions/D-NN/ under the Agent Zero page
- Instances
- one per decision
- Count
- 29 (plan/decisions.json D-1…D-29) + harness-lab DECISIONS.md
- Renders
- plan/decisions.json: id, date, his words, what it changed, what reverses it; the source/ file it came from
- Theme
- agents = reflect violet
- Rail
- U0
- Needs
- —
- Links out
- U18 U4 U5 U9
- Links in
- U9 U4 U5
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 |
| Command palette | system-map/nav.js:157-171,192-257; system-map/nav.css:183-200 | Registry page title, description, section, ID and keywords filtered by query | Copy the palette DOM/event handlers and point REGISTRY_URL at the Great Library route registry. | good — keyboard navigation, mouse selection, escape close, and command shortcut |
| 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 |
| 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 |
| Node detail card grid | system-map/part-page.css:19-26; generate-part-pages.mjs:144-158; industry.css:38-49; generate-industry-pages.mjs:137-144 | Owned scope, known findings, inputs, outputs, risks, and open questions | Copy node-card variants and feed arrays into labeled cards with wide/risk/lilac/mint classes. | good — flexible two-column/wide layout for heterogeneous records |
| Dependency link chips | system-map/index.html:152-157; system-map/part-page.css:94-96; generate-part-pages.mjs:100-109 | Related part IDs, titles, and dependency direction | Copy dependency chip styles and feed linked work/decision IDs. | good — compact relationship map that remains clickable |
| 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 |
From the 21st.dev bank (his picks, his notes)
really nice bento card. If we ever make a landing page this is a really good comp to have. Must mean a lot considering I've actively not been mentioning landing page stuffShaan · ui-bank note
Rob this bento-card composition for decision page.
this would be so banging in the operators dashboard. I'd make a whole page for this. Models could have streaks, get assigned badges. We're going to gamify a bit for them, on the operators performance side of the admin boardShaan · ui-bank note
Rob this leaderboard-card composition for decision page.
great-ui revision timeline looks cool, the only comp I'm going to give you from themShaan · ui-bank note
Rob this great-ui-revision-timeline composition for decision page.
another performance benchmark card, might be usefulShaan · ui-bank note
Rob this performance-benchmark-card composition for decision page.
Bank gaps: decision schema and evidence provenance need bespoke data
Done when
facts have a receipt; the rest is proposaltemplates/U16/template.html composes parts; example.json is real data.https://github.com/sisodias/siso-shell/tree/main/templates/U16- 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.
