U6 · order 17 of 24 · host luna-then-fable

Erdős question page

one per problem in the Erdős fleet · 4 (742, 647, 23, 848; SISO_Research/erdos, laptop lane frozen 30 Aug, Mini lane)

builtorder 17host luna-then-fableresearchissue #59

The page, rendered

this template composed from real data, inside the CRM shell

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

we need one for each ERDOS questionShaan · 6 Sep 16:50
Reading authored by the seat

His 16:50: 'we need one for each ERDOS question'. Four problems, a frozen laptop lane, a Mini lane, certificates: a GQ page with maths-specific state.

Readers. Human: is it solved, replayable, what did it cost. Agent: the certificate path and the replay command.
1. What is the problem?
2. What is proven, what is conjectured?
3. Is the certificate replayable, by which command?
4. What compute did it take, where?
What this page may claim

Claim ceilingProof state only from a certificate or an audit file; never from a handoff sentence.

Data it rendersSISO_Research/erdos/goals/*.md, audits/, DECISION-LOG.html, CHECKPOINT-2026-08-30.html.

PrivacyPublic.

Empty stateNo certificate → 'unverified' in amber.

Agent entrySISO_Research/erdos/AGENTS.md

Content contract

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

1 · title

Erdős NNN

2 · subtitle

statement in one line

3 · paragraph

approach

4 · mind map

reductions

5 · repos

erdos repo + certificate files

6 · research

papers/sources

7 · docs

audits

8 · progress

proven / conjectured / replayable

9 · agents

fleet seats

10 · timeline

attempts

11 · docs over_time

—

12 · own nav

problem · approach · certificate · compute

Sections, in order · where it lives

1
problem statement
2
approach + reductions
3
certificate / replay status
4
compute spent + host
5
decision log
6
what would close it

Lives at: Library Works of type research_question, section Research, one per problem; the erdos repo as their satellite
Instances: one per problem in the Erdős fleet
Count: 4 (742, 647, 23, 848; SISO_Research/erdos, laptop lane frozen 30 Aug, Mini lane)
Renders: SISO_Research/erdos/goals/*.md, DECISION-LOG.html, CHECKPOINT-2026-08-30.html, audits/, proof certificates
Theme: research = focus blue
Rail: U0
Needs: U5
Links out: U19 runs U22 nodes
Links in: U5 index U2 Research

What to rob

presentation only; licences kept

From the Action Model sites (built from real data)

block-runtime synthesis page: badge · headline · bordered thesis box · stat cards

Components, exact locations (Luna inventory)

Component	Where	Renders	How	Quality
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
Registry card grid	system-map/parts/index.html:19-34; system-map/registry.css:14-20; industry index:20; live artifacts index	ID, group/section, title, description, count/status, and open route	Copy registry-card grid and feed typed records with route, title, summary, and status.	good — reusable catalogue unit with strong hover/open affordance
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
Evidence/source table	RESEARCH-PACK.html:166-176,233-264,358-395; part-page.css:32-39,50-59; industry.css:52-60; docs.css:54-59; state/index.html:220-240; blueprint/index.html:335,393,427	Rows of sources, contributions, limits, repositories, evidence classes, observed slots, statuses, and provenance paths	Copy scrollable table wrappers and define a record-specific column schema.	good — explicit provenance columns prevent summary-only displays
Scrollable dataset search header	system-map/part-page.css:46-57; generated P01 dataset markup and inline search behavior	Dataset title/description plus client-side query against preserved research rows	Copy dataset-head/input and bind filtering to table rows by text content.	good — keeps large evidence packets inspectable without pagination
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
Persisted notes textarea	system-map/index.html:158-170 and inline script around notes controls	Viewer-entered notes attached to selected domain; UI includes saved feedback state	Copy notes panel only where per-viewer scratch notes are acceptable; use localStorage safely.	ok — useful interaction but viewer-local rather than shared record

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

scrollable-sticky-footer

frequently asked questions scrolly thing, could be usefulShaan · ui-bank note

Rob this scrollable-sticky-footer composition for erdős question page.

Bank gaps: proof certificate replay and mathematical notation are uncovered

Done when

facts have a receipt; the rest is proposal

fact · has a receiptproposal · not yet

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

Done when: Open /works/erdos-742/ and see the problem, the proof-logging status and a link to the replayable certificate/t/U6/example/

State on 6 Sep 18:36 (plan): not in the Library at all (0 Works mention erdos); the fleet's own HTML pages exist locallyplan/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