Timeline page
one per project + one global · 10 projects + Agent Zero; axis = commits, seats born/closed, decisions, docs, source captures, writebacks
The page, rendered
this template composed from real data, inside the CRM shellOpen it full size: /t/U21/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 paraphrasedthe timeline what docs have we made over those timelinesShaan · 6 Sep 18:19
-
Reading authored by the seat
His 18:19: 'the timeline what docs have we made over those timelines'. Time is the one axis every record shares; without it 'what happened in 48 h' is a hand-written page (the Checkpoint) every time.
Readers. Human: what happened when. Agent: the ordered events to reconstruct state at a date.
- What happened on day X?
- When was this doc/commit/decision made and by which seat?
- How dense was the work?
-
What this page may claim
Claim ceilingOnly dated records; auto-backup commits marked as such.Data it rendersgit log, OWNERS.md, decisions.json, source/, docs mtimes.PrivacyPublic; private repos contribute counts, not messages.Empty state—Agent entrybin/az-timeline (to write)
Content contract
his twelve, 18:19; '—' means this family carries nothing theretimeline
project · range
—
—
commit lanes
—
doc lane
density
seat lane
the page
the doc lane
lanes · days
Sections, in order · where it lives
- 1one axis, day ticks
- 2lanes: commits · seats · decisions · docs · his words
- 3filters by lane
- 4hover = the record
- Lives at
- /timeline/ on the Agent Zero page and a 'timeline' section on every U4
- Instances
- one per project + one global
- Count
- 10 projects + Agent Zero; axis = commits, seats born/closed, decisions, docs, source captures, writebacks
- Renders
- git log per repo (date, hash, author human/auto), OWNERS.md, decisions.json, ls source/, ls docs by mtime, owners.log
- Theme
- lane colours = the six accents
- Rail
- U0
- Needs
- —
- Links out
- U17 U16 U18 U4
- Links in
- U4 U9 U1
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 |
| 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 |
| Phase track | task-graph/index.html line 1 generated markup; part-page.css:77-93; blueprint/index.html:475-479 | Ordered program phases with owner/mode, description, and current phase marker | Copy phase card/grid CSS and feed ordered phase records plus current marker. | good — supports roadmap and execution state at a glance |
From the 21st.dev bank (his picks, his notes)
timeline of text, it's clean. I wouldn't say amazingShaan · ui-bank note
Rob this timeline composition for timeline page (commits, docs, seats, decisions on one axis).
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 timeline page (commits, docs, seats, decisions on one axis).
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 timeline page (commits, docs, seats, decisions on one axis).
these breadcrumbs, the way they do them is just really niceShaan · ui-bank note
Rob this with-slash composition for timeline page (commits, docs, seats, decisions on one axis).
Bank gaps: cross-source normalization and one-axis ordering need bespoke data
Done when
facts have a receipt; the rest is proposaltemplates/U21/template.html composes parts; example.json is real data.https://github.com/sisodias/siso-shell/tree/main/templates/U21- 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.
