U17 · order 11 of 24 · host luna

Agent seat page

one per seat that ever ran · ~30 seats 5–6 Sep (12 closed Astra seats + Fable heads + Oracle lane + Mini seats); ledger/OWNERS.md lines

builtorder 11host lunaagentsissue #52

The page, rendered

this template composed from real data, inside the CRM shell

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

agents should be ephemeral … the projects are foreverShaan · 6 Sep 16:50
Reading authored by the seat

His 16:50: 'agents should be ephemeral … the projects are forever'. Ephemeral means a record, not a memory: every seat gets one page so the project keeps what the agent learned.

Readers. Human: what did this agent do and cost. Agent: the handoff to resume from and the brief pattern that worked.
1. What was it born from?
2. What did it land, verified?
3. What did it cost?
4. Where is its reasoning (rollout)?
5. How did it close?
What this page may claim

Claim ceilingLanded only with a commit/URL; cost from token_count events labelled cumulative vs uncached.

Data it rendersbriefs/, handoffs/, OWNERS.md, owners.log, ~/.codex/sessions rollouts (private satellite).

PrivacyPublic page; rollout private.

Empty stateNo handoff → 'closed without handoff' in red.

Agent entryhandoffs/<SEAT>.md

Content contract

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

1 · title

SEAT

2 · subtitle

model · node · born → closed

3 · paragraph

what it was for (brief)

4 · mind map

project → modules → commits

5 · repos

repos it wrote to

6 · research

—

7 · docs

—

8 · progress

landed / left

9 · agents

itself + successors

10 · timeline

born · writebacks · closed

11 · docs over_time

handoff sections by time

12 · own nav

born · landed · cost · rollout · closed

Sections, in order · where it lives

1
born: date, brief, node, model, harness
2
what it landed (verified)
3
what it cost (uncached in / out / reasoning)
4
its writebacks
5
its rollout (path, size, private)
6
closed: how, handoff

Lives at: /seats// under the project it served; the rollout stays in -sessions
Instances: one per seat that ever ran
Count: ~30 seats 5–6 Sep (12 closed Astra seats + Fable heads + Oracle lane + Mini seats); ledger/OWNERS.md lines
Renders: briefs/.md (born from), handoffs/.md, OWNERS.md lines, owners.log, rollout path + token maxima (GAPS M-4), verification line
Theme: agents = reflect violet
Rail: U0
Needs: —
Links out: U4 U19 U21 U18
Links in: U4 U9 U10

What to rob

presentation only; licences kept

From the Action Model sites (built from real data)

research-os track card: kicker · status · 'ORIGINAL TASK'

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
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
Status badge/chip	site/index.html:101-102; system-map/part-page.css:37-39,58-59; nav.css:151-153; blueprint/index.html:39-42	Research state, maturity, qualification, sparse/observed posture, and live/open state	Copy chip CSS and feed an explicit status vocabulary, never inferred prose.	good — status is visually prominent and remains text-readable
Node detail card grid	system-map/part-page.css:19-26; generate-part-pages.mjs:144-158; industry.css:38-49; generate-industry-pages.mjs:137-144	Owned scope, known findings, inputs, outputs, risks, and open questions	Copy node-card variants and feed arrays into labeled cards with wide/risk/lilac/mint classes.	good — flexible two-column/wide layout for heterogeneous records
Dependency link chips	system-map/index.html:152-157; system-map/part-page.css:94-96; generate-part-pages.mjs:100-109	Related part IDs, titles, and dependency direction	Copy dependency chip styles and feed linked work/decision IDs.	good — compact relationship map that remains clickable
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
Computed defect panel	generate-state-page.mjs:349-370; state/index.html:213-229	Derived estate defects with owner, observed rows, and detection method	Copy defect section and feed computed findings only, with detection explanation.	good — distinguishes live derived defects from hand-maintained warnings
Sprint lane grid	part-page.css:78-96; task-graph/index.html generated markup	Sprint number, title, gate, lane owner, linked parts, and lane outputs	Copy sprint/lane grid and feed owner, gate, linked IDs, and output bullets.	good — dense multi-owner work stays scannable

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

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 seat page.

ai-planning

AI planning, I like how it dropped down and can show a bunch of information. Not sure where we'd use itShaan · ui-bank note

Rob this ai-planning composition for agent seat page.

stats-card

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

Rob this stats-card composition for agent seat page.

estimated-arrival

estimated time arrival, really interesting, don't know where we'd use it, love to have it. Progress bar could be useful in the operator app somewhereShaan · ui-bank note

Rob this estimated-arrival composition for agent seat page.

Bank gaps: seat lifecycle and cost receipts need bespoke data

Done when

facts have a receipt; the rest is proposal

fact · has a receiptproposal · not yet

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

Done when: Open /seats/HALO-ZERO/ and see born 5 Sep 12:01, 37 commits landed on the mirror, 184.6M cumulative tokens, the rollout path, and its handoff/t/U17/example/

State on 6 Sep 18:36 (plan): exists as handoff markdown + OWNERS lines; no page; cost only in GAPS M-4plan/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