U4 · order 3 of 24 · host fable

Project one pager (bigger; the hub that links to the rest)

one per project, agency and client · 10 projects: Library, Foundry, Internal+Agent Base, Knowledge/siso-source, Plays/hub, GQ+compute, Agent Zero (agency) · Oracle, HALO, BykonzYard, Action Model (client)

builtorder 3host fableprojectsissue #43

The page, rendered

this template composed from real data, inside the CRM shell

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

templates for like our project one pager which leads to all of the other project Cloudflare … loads of different repos, but we want like a set kind of UI templateShaan · 6 Sep 16:36
Reading authored by the seat

His 16:36: 'templates for like our project one pager which leads to all of the other project Cloudflare … loads of different repos, but we want like a set kind of UI template'; 18:19: 'title subtitle paragraph … mind map … link to all of the repos … all of the research what the research means … all of the docs the progress what agents we've had running on here the timeline'. This is the hub: every other page is one hop from it.

Readers. Human: the whole project in one screen, then click out. Agent: the entry to resume a project: front door, repos, verification lines, open modules.
1. What is this project and for whom?
2. Which repos, which are private, what is the head commit?
3. What is live (URLs) and does it return 200?
4. What landed, what is left, who is on it?
5. What did he say about it, when?
6. Which questions, industries and Works does it touch?
What this page may claim

Claim ceilingRepo heads and HTTP codes from live lookups with their timestamp; 'landed' only when verified against a remote or URL; his words verbatim from source/.

Data it rendersplan/projects.json (this repo) + /.agents/{PAGE.md,HANDOFF.md,owners.log,page.url,repos.json} + bin/az-projects-table live cache; the same JSON feeds the project's own pages.dev front door and its Library Work.

PrivacyPublic front door for agency projects; client projects show repo names, visibility and dated activity, never payload.

Empty stateNo URL → 'no live page yet' + the publish play; no owner → 'unowned' in red.

Agent entry<repo>/.agents/PAGE.md (read first) · bin/az-projects-table

Content contract

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

1 · title

project name

2 · subtitle

client or agency · one-line what · for whom

3 · paragraph

in his words, dated

4 · mind map

repos · Works · questions · industries · people · nodes as a graph

5 · repos

every repo incl. private: head, time, branch, visibility

6 · research

research Works + one line each: what it means for this project

7 · docs

the docs in the repos, dated

8 · progress

modules with verification lines: landed / left

9 · agents

every seat that ran: born, closed, what it landed, cost

10 · timeline

commits + seats + decisions + docs on one axis

11 · docs over_time

docs plotted on that axis

12 · own nav

the ten sections

Sections, in order · where it lives

1
what it is, in his words
2
repos incl. private (head, time, visibility)
3
live URLs with codes
4
owner seats + latest writeback
5
what landed (verified)
6
what is left → the module rows with verification lines
7
links: the Works, GQs and industries this project touches
8
the Cloudflare pages it leads to

Lives at: each project's *.pages.dev front door (Tier 1) AND mirrored as a Library Work of type project; atlas/p/.html is the prototype today
Instances: one per project, agency and client
Count: 10 projects: Library, Foundry, Internal+Agent Base, Knowledge/siso-source, Plays/hub, GQ+compute, Agent Zero (agency) · Oracle, HALO, BykonzYard, Action Model (client)
Renders: plan/projects.json (repos with branch/head/private, urls with HTTP code, seats with last writeback, landed, said verbatim, left, modules with verification lines) + /.agents/{PAGE.md,HANDOFF.md,owners.log,page.url,repos.json}
Theme: project = today orange; client projects carry the client's own brand strip below the SISO shell
Rail: U0
Needs: U0 U3
Links out: U3 Works U5 GQs U8 industries U14 people U15 client account U16 decisions U17 seats U18 source U21 timeline U22 nodes
Links in: U1 U9 U15

What to rob

presentation only; licences kept

From the Action Model sites (built from real data)

system-map root: 'Programme brief · date' kicker · 'Evidence ladder' counts with gate labels · 'OBSERVED' strip with commit hash

blueprint: chip row of entry points with live dots (system map, component catalogue, demo)

research-os: 'central thesis' + 'decision posture' twin panels; track cards

Components, exact locations (Luna inventory)

Component	Where	Renders	How	Quality
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
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
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
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
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

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

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 project one pager (bigger; the hub that links to the rest).

stats-card

I like this stats card, the earning one, really niceShaan · ui-bank note

Rob this stats-card composition for project one pager (bigger; the hub that links to the rest).

mini-chart

does this activity mini chart actually work? It does. Banging. We needed some graphs. This is going to be used in the operator thingShaan · ui-bank note

Rob this mini-chart composition for project one pager (bigger; the hub that links to the rest).

great-ui-revision-timeline

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 project one pager (bigger; the hub that links to the rest).

team-invitation

team invitation comp, don't know where it could be used but kind of cool. This team invitation is just good. If I mention they're good they're always good for a component bankShaan · ui-bank note

Rob this team-invitation composition for project one pager (bigger; the hub that links to the rest).

to-do-card

to-do list, quite cool. Return activity, this could be reused in operator somewhereShaan · ui-bank note

Rob this to-do-card composition for project one pager (bigger; the hub that links to the rest).

Bank gaps: repo truth, seat writebacks, and link graph need project data integration

Done when

facts have a receipt; the rest is proposal

fact · has a receiptproposal · not yet

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

Done when: Open .pages.dev and https://great-library-of-siso.pages.dev/works// and see the same one pager; every repo listed with its head commit from gh api, private ones marked private/t/U4/example/

State on 6 Sep 18:36 (plan): data exists (PROJECTS.html 11 rows, atlas/p 17 pages); front door on 4 of 10 repos; no shared templateplan/templates.json status field

Gap T-4 (atlas/GAPS-2026-09-06.html)open gap

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