God Question page
one per GQ · 22 (GOD-QUESTIONS.md; 18 registered as Works; 14 GQ URLs fall through to root)
The page, rendered
this template composed from real data, inside the CRM shellOpen it full size: /t/U5/example/ · data: example.json · schema.json
Why this template exists
his words · the reading · the ceilings-
His words 1
verbatim, from
00_AGENT_ZERO/source/— never paraphrasedall the different God questions, which are different allocations of compute, like we need a template for each and every God question project, right? Because it will show a bunch of stuff.Shaan · 6 Sep 16:36
-
Reading authored by the seat
His 16:36: 'all the different God questions, which are different allocations of compute, like we need a template for each and every God question project, right? Because it will show a bunch of stuff.' A GQ page is where a decision target meets its evidence and its compute.
Readers. Human: what are we trying to learn, what do we know, what is it costing. Agent: the decision target + counterexample rule + which modules to run next.
- What is the exact question and the decision it changes?
- What is the current answer and its counterexample?
- What evidence exists, dated, with receipts?
- Which compute modules are allocated / done / unallocated?
- What would close it?
-
What this page may claim
Claim ceilingEvidence lines cite a receipt path; 'answer' is labelled proposed until a receipt supports it; ratios carry n.Data it rendersGOD-QUESTIONS.md card, plan/modules.json rows with domain god-questions, domains/compute/runs// receipts (U19), source/ words that raised it. PrivacyPublic.Empty stateNo run yet → 'no receipt; allocated to' or 'unallocated'. Agent entryGOD-QUESTIONS.md#GQ-NNN · domains/compute/runs/
Content contract
his twelve, 18:19; '—' means this family carries nothing thereGQ-NNN · the question
decision target
why it matters, in his words
question → subquestions → modules → runs → Works
repos the runs live in
evidence lines with receipts + what each means
docs it produced
modules: allocated / done / unallocated by host
seats that ran on it + cost
runs + decisions by date
—
question · state · evidence · compute · next
Sections, in order · where it lives
- 1the question + decision target
- 2research state + counterexample
- 3evidence map with dated receipts (J2 ratio, E1 windows…)
- 4subquestions → compute modules allocated / not
- 5expected answer package
- 6who is on it + host (webui/luna/codex/shaan/hold)
- Lives at
- /works/frontier-question-gq-NNN/ + /god-questions/ index
- Instances
- one per GQ
- Count
- 22 (GOD-QUESTIONS.md; 18 registered as Works; 14 GQ URLs fall through to root)
- Renders
- GOD-QUESTIONS.md cards (question, decision target, counterexample, evidence lines), docs/frontier-question-template.html (exact question, why it matters, assumptions, evidence map, subquestions, expected answer package), domains/compute/runs/
/ receipts - Theme
- research = focus blue
- Rail
- U0
- Needs
- U0 U3
- Links out
- U19 runs U16 decisions U18 source U3 Works it produced U4 projects it serves
- Links in
- U1 U9 U4
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 |
| Registry card grid | system-map/parts/index.html:19-34; system-map/registry.css:14-20; industry index:20; live artifacts index | ID, group/section, title, description, count/status, and open route | Copy registry-card grid and feed typed records with route, title, summary, and status. | good — reusable catalogue unit with strong hover/open affordance |
| 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 |
From the 21st.dev bank (his picks, his notes)
some sort of heat map, that'll be usefulShaan · ui-bank note
Rob this anomaly-heatmap composition for god question page.
frequently asked questions scrolly thing, could be usefulShaan · ui-bank note
Rob this scrollable-sticky-footer composition for god question page.
another performance benchmark card, might be usefulShaan · ui-bank note
Rob this performance-benchmark-card composition for god question page.
timeline of text, it's clean. I wouldn't say amazingShaan · ui-bank note
Rob this timeline composition for god question page.
Bank gaps: mind map and evidence receipts need domain-specific rendering
Done when
facts have a receipt; the rest is proposaltemplates/U5/template.html composes parts; example.json is real data.https://github.com/sisodias/siso-shell/tree/main/templates/U5- 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.


