Library landing (root front door)
one page · 1
The page, rendered
this template composed from real data, inside the CRM shellOpen it full size: /t/U1/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
His 16:36: the Library is 'a way to actually see that shit'; 'look at what we currently have and figure out why it's stupid'. The root is the only page a stranger or a cold agent sees first.
Readers. Human: understand SISO in 30 s, pick a door. Agent: read the loop and the counts, then follow catalog.json.
- What is SISO building and why?
- How big is it (counts)?
- Where do I go for a project / a question / an industry?
- What moved this week?
-
What this page may claim
Claim ceilingCounts come from catalog.json at build; the loop shows the thesis and marks measured results only where a receipt exists.Data it renderscatalog.json (works, repositories, assemblies, inventories), GOD-QUESTIONS.md count, industries index, the latest owners.log lines for 'what moved'.PrivacyPublic.Empty stateA section with 0 items says '0, nothing registered yet' with the gls command to register.Agent entryGreat_Library_of_SISO/src/build.mjs → site/index.html
Content contract
his twelve, 18:19; '—' means this family carries nothing thereGreat Library of SISO
the bet in one line (INTENT.md)
his words, dated
the ecosystem loop, every node a link
27 repos, 23 public / 4 private, as a count + link
latest research Works
latest docs
counts strip
live seats from /now/
last 7 days strip
—
loop · sections · latest · doors
Sections, in order · where it lives
- 1purpose in his words
- 2the loop: clients fund compute → owners build → packs enter the Library → people+repos feed Foundry → questions turn evidence into breakthroughs
- 3section counts from catalog.json
- 4featured: latest Works, latest GQ, latest project one pagers
- 5search
- Lives at
- great-library-of-siso.pages.dev/ (Great_Library_of_SISO/src build)
- Instances
- one page
- Count
- 1
- Renders
- catalog.json counts (47 Works, 86 Releases, 40 Snapshots, 8 inventories, 27 repos 23 public / 4 private, 17 industries, 22 GQ), the ecosystem loop from library-ui-spec §6, featured entry points
- Theme
- brand gradient hero, section accents
- Rail
- U0
- Needs
- U0
- Links out
- U2 sections U4 projects U5 GQs U8 industries U9 Agent Zero U21 timeline
- Links in
- everything
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 |
| Collapsed rail handle | system-map/nav.js:40-48,165-173; system-map/nav.css:161-179; blueprint/assets/shell.js:1-19; blueprint/assets/shell.css:1-19 | Only shell state; preserves destination marks while hiding labels | Copy the toggle plus localStorage preference and bind it to the Library grouped rail. | good — compact mode retains route affordances and keyboard toggle |
| Mobile nav drawer/backdrop | system-map/nav.js:136-155,176-189; system-map/nav.css:202-232 | Same registry routes as desktop rail with mobile open/close state | Copy mobile button, backdrop, and responsive CSS; reuse the same registry renderer. | good — responsive drawer has explicit close semantics and backdrop |
| SISO rail with section anchors | blueprint/index.html:238-244; blueprint/assets/shell.css:4-18; blueprint/assets/shell.js:1-19 | Static page sections and route link labels from blueprint page content | Copy rail markup/assets and replace anchors with Great Library groups. | ok — polished but static and not registry-driven |
| 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 |
| 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 |
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 library landing (root front door).
welcome new models, that's what we neededShaan · ui-bank note
Rob this welcome-modal composition for library landing (root front door).
feature carousel could be a way of showing models: carousel click through the models to their profile picture. Food for thoughtShaan · ui-bank note
Rob this feature-carousel composition for library landing (root front door).
another dialog card, could be useful. That's more landing page shitShaan · ui-bank note
Rob this onboardin-dialog composition for library landing (root front door).
Bank gaps: loop diagram and truthful catalog data need bespoke integration
Done when
facts have a receipt; the rest is proposaltemplates/U1/template.html composes parts; example.json is real data.https://github.com/sisodias/siso-shell/tree/main/templates/U1- 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.


