U23 · order 2 of 24 · host fable

Template gallery

one page + one detail page per template · 24 templates (this map)

builtorder 2host fableprojectsissue #64

The page, rendered

this template composed from real data, inside the CRM shell

Open it full size: / · 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 paraphrased

No verbatim source on this page.
Reading authored by the seat

His 18:19: 'i'd want to see all of the templates and then from those templates i can like click on it to see something … click on the page to actually see the page template and the component'. The gallery is how he and the Library UI Fable agree on each template before it is built.

Readers. Human: judge each template. Agent: the contract to build to.
1. Which templates exist and in what order?
2. What must each carry?
3. What can I rob for it?
4. What proves it done?
What this page may claim

Claim ceiling—

Data it rendersplan/templates.json + the two Luna inventories.

PrivacyPublic.

Empty state—

Agent entrybin/az-templates

Content contract

his twelve, 18:19; '—' means this family carries nothing there

1 · title

Templates

2 · subtitle

the map

3 · paragraph

—

4 · mind map

—

5 · repos

—

6 · research

—

7 · docs

—

8 · progress

—

9 · agents

—

10 · timeline

—

11 · docs over_time

—

12 · own nav

cards · order

Sections, in order · where it lives

1
card per template
2
detail: reasoning block · content contract · wireframe · components to rob (with screenshots) · example today · verification · issue

Lives at: atlas/TEMPLATES-2026-09-06.html + atlas/t/.html; later the Library /docs/templates/
Instances: one page + one detail page per template
Count: 24 templates (this map)
Renders: plan/templates.json: every row's reasoning, content contract, sections, rob-from lists (Action Model inventory + 21st.dev picks), example today, verification
Theme: each card in its family's accent
Rail: U0
Needs: —
Links out: all
Links in: U9

What to rob

presentation only; licences kept

From 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
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
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
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

From the 21st.dev bank (his picks, his notes)

bento-card

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 template gallery (click a template → see the page + its components).

feature-carousel

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 template gallery (click a template → see the page + its components).

project-detail-view

kind of nice, kind of simple, could be used somewhere in the operators thing. (Server management one was a bit shitty)Shaan · ui-bank note

Rob this project-detail-view composition for template gallery (click a template → see the page + its components).

Bank gaps: live previews and component provenance require gallery integration

Done when

facts have a receipt; the rest is proposal

fact · has a receiptproposal · not yet

Template templates/U23/template.html composes parts; example.json is real data.https://github.com/sisodias/siso-shell/tree/main/templates/U23

Done when: Open the gallery, click U4, and see its reasoning, its twelve-item content contract, a wireframe with the sections, the Action Model panels to rob with screenshots, the 21st.dev picks, and the live prototype/

State on 6 Sep 18:36 (plan): this page, being built nowplan/templates.json status field

Limits

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.

Version

plan/templates.json · 2026-09-06 18:36