Play / skill page
one per play and per hub skill · 8 plays (P1–P8) + 32 hub skills (siso-skills-hub)
The page, rendered
this template composed from real data, inside the CRM shellOpen it full size: /t/U20/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 paraphrasedNo verbatim source on this page. -
Reading authored by the seat
Eight plays let fourteen contexts behave as one system; an agent must find the play and its command without reading a brief.
Readers. Human: what plays exist. Agent: the exact command and whether it is installed here.
- What does it do?
- How do I run it?
- Is it installed on this harness/machine?
- Has it been used for real?
-
What this page may claim
Claim ceilingInstalled only with a probe receipt.Data it rendershub registry + probe receipts + OWNERS lines.PrivacyPublic.Empty stateNot installed here → the add-skill command.Agent entrysiso-skills-hub registry/skills/<path>/SKILL.md
Content contract
his twelve, 18:19; '—' means this family carries nothing thereplay
one line
when to use
—
—
—
—
installed matrix
owner
uses
—
what · command · installed · uses
Sections, in order · where it lives
- 1what it does in one line
- 2the command
- 3where installed (harness × machine) with probe date
- 4used for real: receipts
- 5source hash
- Lives at
- Library section Agents → /plays/
/ and /skills/ / - Instances
- one per play and per hub skill
- Count
- 8 plays (P1–P8) + 32 hub skills (siso-skills-hub)
- Renders
- atlas/FRAMEWORKS-2026-09-05.html, skills-hub registry/skills/*/SKILL.md, install state per harness per machine (cold-discovery probes)
- Theme
- agents = reflect violet
- Rail
- U0
- Needs
- —
- Links out
- U17 U9
- Links in
- U9 U2 Agents
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 |
| 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 |
| 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 |
| 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 |
| OSS admission funnel | site/index.html:431-441; generate-state-page.mjs:71-112; state.css:74-160 | Merged candidates, bounded reviews, held evidence, rejected, admitted, and stage counts | Copy funnel rows/bar CSS and feed ordered stage count objects. | good — communicates attrition and zero states without hiding them |
From the 21st.dev bank (his picks, his notes)
countdown component, always loved it. Can be used in coming-soon features or whereverShaan · ui-bank note
Rob this countdown-number composition for play page (commands, where installed).
I like this workflow builder card, could be used in the dashboard somewhereShaan · ui-bank note
Rob this workflow-builder-card composition for play page (commands, where installed).
to-do list, quite cool. Return activity, this could be reused in operator somewhereShaan · ui-bank note
Rob this to-do-card composition for play page (commands, where installed).
priority queue, thought about it, could be used somewhere in the operatorShaan · ui-bank note
Rob this draggable-priority-list composition for play page (commands, where installed).
Bank gaps: safe command rendering and install provenance need bespoke content
Done when
facts have a receipt; the rest is proposaltemplates/U20/template.html composes parts; example.json is real data.https://github.com/sisodias/siso-shell/tree/main/templates/U20- 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.
