U14 · order 13 of 24 · host fable

Person page

one per client, collaborator, person in the graph · 3 clients (Camron · ofm, Fahmy · bykonz, Cena · actionmodel) + the People Graph programme

builtorder 13host fableclientsissue #55

The page, rendered

this template composed from real data, inside the CRM shell

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

Every client project points at a person and nothing renders one; the 5 Sep 22:20 ruling 'account repo over project repos' has no page.

Readers. Human: who is this, what do we do for them, where are we. Agent: the account repo + the projects.
1. Who?
2. Which projects and repos?
3. When did we last deliver?
4. What is owed?
What this page may claim

Claim ceilingPublic-safe identity and relationship only; words and money private.

Data it rendersaccount repo .agents/, projects.json, owners.log.

PrivacyPublic stub; private detail behind the account repo.

Empty state—

Agent entry<account-repo>/.agents/PAGE.md

Content contract

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

1 · title

name

2 · subtitle

role · since

3 · paragraph

relationship

4 · mind map

projects → repos

5 · repos

account + project repos

6 · research

—

7 · docs

—

8 · progress

deliverables

9 · agents

seats on their projects

10 · timeline

deliveries

11 · docs over_time

—

12 · own nav

who · projects · activity

Sections, in order · where it lives

1
who, in one line
2
relationship + since
3
projects + repos
4
what they said (private, dated)
5
what we owe / they owe
6
activity

Lives at: Library Work of type person (public-safe) + private account repo
Instances: one per client, collaborator, person in the graph
Count: 3 clients (Camron · ofm, Fahmy · bykonz, Cena · actionmodel) + the People Graph programme
Renders: PEOPLE-GRAPH-PROGRAM.md, client account repos, projects.json 'for whom', WhatsApp intake words (private)
Theme: clients = tasks amber
Rail: U0
Needs: —
Links out: U15 U4 U11
Links in: U4 U1

What to rob

presentation only; licences kept

From the Action Model sites (built from real data)

research-os track cards as 'project cards per person'

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
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
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
Research/industry colored cards	part-page.css:20-26,44-45; industry.css:39-49; blueprint/index.html:50-56,449-454	Typed narrative blocks such as conclusion, rationale, risk, falsifier, or directional score	Copy lilac/mint/risk/dark variants and feed an explicit semantic role.	good — color communicates evidence role without replacing text

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

social-card

always been a cool socials card, it's always been goodShaan · ui-bank note

Rob this social-card composition for person page.

social-post-card

really cool. Don't know where it can be used but save this. I always like the UI of the design and the card and where the profile showsShaan · ui-bank note

Rob this social-post-card composition for person page.

popover

profile selector popover, pop it in a profile thing / settings. We need one of that for the operatorShaan · ui-bank note

Rob this popover composition for person page.

card-5

this card if you rob it out the box is really good. New opportunity card. Could be used somewhere, just the design of the way the card is laid out, maybe for models. Good UI designShaan · ui-bank note

Rob this card-5 composition for person page.

social-card

always been a cool socials card, it's always been goodShaan · ui-bank note

Rob this social-card composition for person page.

Bank gaps: verbatim source and all-repo relationship graph need bespoke data

Done when

facts have a receipt; the rest is proposal

fact · has a receiptproposal · not yet

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

Done when: Open /people/camron/ and see two projects (Oracle, HALO), their repos and the last dated activity; no message content/t/U14/example/

State on 6 Sep 18:36 (plan): nothing renders a person; clients exist only as words inside project rowsplan/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