Source page (his words)
one per capture · 44 files, 111,930 words in 00_AGENT_ZERO/source/ + siso-source partitions (August 10,503, September 4,144 occurrences)
The page, rendered
this template composed from real data, inside the CRM shellOpen it full size: /t/U18/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 of my prompts and absolutely everythingShaan · 6 Sep 16:36
-
Reading authored by the seat
His 16:36: 'all of my prompts and absolutely everything'; 16:50: 'those 50,000 words and the last 20,000 words … a really important source'. The words are the root of every decision; they need a front end of their own.
Readers. Human: what did I say, when, and what happened because of it. Agent: the verbatim to quote instead of paraphrasing.
- What did he say on X?
- What did it cause?
- When exactly (label vs transcript)?
-
What this page may claim
Claim ceilingVerbatim only; 'Reads' labelled as the seat's reading.Data it renderssource/*.md, siso-source manifest.PrivacyPrivate repo; public pages quote fragments.Empty state—Agent entrysource/
Content contract
his twelve, 18:19; '—' means this family carries nothing theredate-time · slug
to whom
the words
→ decisions, briefs, pages
—
—
—
caused
—
the day
—
words · reads · caused
Sections, in order · where it lives
- 1the words, verbatim, dated
- 2who it was said to
- 3what it caused (decisions, briefs, pages)
- 4the offset note (label vs transcript, GAPS F-8)
- Lives at
- /source/ index by date + /source/
/ (private repo siso-agent-zero-source if he rules so) - Instances
- one per capture
- Count
- 44 files, 111,930 words in 00_AGENT_ZERO/source/ + siso-source partitions (August 10,503, September 4,144 occurrences)
- Renders
- source/
- .md: verbatim block + Reads; transcript timestamp; the decisions/projects it caused - Theme
- agents = reflect violet
- Rail
- U0
- Needs
- —
- Links out
- U16 U4 U5 U17
- Links in
- U9 U16 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 |
| 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 |
| Searchable track/card filter | site/index.html:487-499; blueprint/index.html:357-400 and filter script around 487-499 | Track cards matched against data-search keywords and visible count | Copy the input/filter function and give each card a normalized search string. | good — simple no-framework filtering with visible result count |
| Resource room card grid | site/index.html:403-416; blueprint/index.html:300-303,424-427 | Research room title, status/tag, short description, and route | Copy card markup and map each Library work or source to tag, summary, and link. | good — clear scan-to-open pattern with color-coded category strips |
| 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 |
| Freshness lane card | generate-state-page.mjs:122-190; state/index.html:83-176; state.css:306-469 | Lane owner, state, last change, age/budget, note, source locator, and reachability | Copy lane-card structure and feed owner, freshness state, budget, source, and note. | good — combines operational status and evidence locator in one unit |
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 source page (his verbatim words, dated).
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 source page (his verbatim words, dated).
frequently asked questions scrolly thing, could be usefulShaan · ui-bank note
Rob this scrollable-sticky-footer composition for source page (his verbatim words, dated).
Bank gaps: verbatim provenance and quote search require bespoke content
Done when
facts have a receipt; the rest is proposaltemplates/U18/template.html composes parts; example.json is real data.https://github.com/sisodias/siso-shell/tree/main/templates/U18- 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.
