U9 · order 7 of 24 · host fable

Agent Zero page (his concepts + the fleet, on the Library)

one · 1 (+ the 24 atlas pages it fronts)

builtorder 7host fableagentsissue #47

The page, rendered

this template composed from real data, inside the CRM shell

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

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

His 16:36: 'the template for Agent Zero and like a repo of all of my main concepts and information for Agent Zero. So if I want to see that front end and see what's going on with Agent Zero, see all of the main projects and all of that stuff linked to it, it's all there.'

Readers. Human: the whole thing from the top. Agent: the read order + the register + the decisions, then the project it touches.
1. What is the bet and the two axes?
2. What are his concepts, in his words, by date?
3. Which projects exist and what state are they in?
4. What is allocated, done, unallocated, by host?
5. What was decided and what reverses it?
6. Who is running now and where?
What this page may claim

Claim ceilingEvery number from a JSON in this repo; his words only from source/.

Data it rendersINTENT.md, BASELINE.md, plan/*.json, GOD-QUESTIONS.md, source/, ledger/OWNERS.md, atlas/now.json.

PrivacyPublic page; the repo may stay private (D on source/ → private siso-agent-zero-source).

Empty state—

Agent entryINTENT.md → BASELINE.md → this page

Content contract

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

1 · title

Agent Zero

2 · subtitle

the bet

3 · paragraph

INTENT in his words

4 · mind map

projects · questions · plays · nodes

5 · repos

this repo + harness-lab

6 · research

the GQs

7 · docs

atlas readings by date

8 · progress

9 · agents

every seat, live and closed

10 · timeline

decisions + seats + readings

11 · docs over_time

atlas pages by date

12 · own nav

bet · concepts · projects · register · decisions · fleet · gaps

Sections, in order · where it lives

1
the bet + the two axes
2
his concepts (source/ index, dated, verbatim)
3
projects → U4 pages
4
register: allocated / not allocated / done, by host, with verification lines
5
decisions D-1…D-29
6
fleet now (owners, nodes)
7
gaps

Lives at: Library Work 'Agent Zero' (type agent_system) + agent-zero.pages.dev front door; atlas/ stays the laptop-local live view
Instances: one
Count: 1 (+ the 24 atlas pages it fronts)
Renders: INTENT.md, BASELINE.md, plan/{modules,projects,decisions}.json, GOD-QUESTIONS.md, source/ (44 verbatim files, 111,930 words), ledger/OWNERS.md, the atlas
Theme: agents = reflect violet
Rail: U0
Needs: U0 U4
Links out: U4 all projects U5 GQs U16 decisions U17 seats U18 source U21 timeline U22 nodes U20 plays
Links in: U1

What to rob

presentation only; licences kept

From the Action Model sites (built from real data)

system-map registry rail with counts + status chips

research-os pack index + hero posture card

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

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

ai-input

ask AI input. Really cool the way it pops up, then we're not always wasting space. Having an AI chat always showing is the bad way to go on Oracle. This is definitely the best way, definitely best UI principles. Hand over to an agent to look intoShaan · ui-bank note

Rob this ai-input composition for agent zero page (his concepts + the fleet, on the library).

agent-plan

drop-down agent plan, might be useful. We've done a really nice onboarding dropdown and our UI is better, but the way this component works is maybe slightly betterShaan · ui-bank note

Rob this agent-plan composition for agent zero page (his concepts + the fleet, on the library).

agent-avatar

(agent avatar; part of the AI/agent set, no separate comment)Shaan · ui-bank note

Rob this agent-avatar composition for agent zero page (his concepts + the fleet, on the library).

animated-state-icons

animated state icons, always useful to make the app feel nicerShaan · ui-bank note

Rob this animated-state-icons composition for agent zero page (his concepts + the fleet, on the library).

Bank gaps: fleet register and verbatim source index need bespoke data

Done when

facts have a receipt; the rest is proposal

fact · has a receiptproposal · not yet

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

Done when: Open https://great-library-of-siso.pages.dev/works/agent-zero/ from a cold browser and see the register with 51 rows, each with its host and verification line, and the 44 source files listed by date/t/U9/example/

State on 6 Sep 18:36 (plan): atlas/AGENT-ZERO.html + index.html exist on the laptop only; not on the Library; the atlas rail is not the CRM one (fixing now)plan/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

The page, rendered

Why this template exists

His words 0

Reading authored by the seat

What this page may claim