Context
Follow-up to the identity-apex rollout (Epic #12225; the README apex landed via #12228 / PR #12243). With the apex content now in README.md, the operator flagged (2026-05-31) that the README's presentation isn't there yet — four concrete issues. Grounded in current dev README.md.
The Problems (operator-flagged)
Apex not fully featured (opening, lines ~13–31). The opening condenses/paraphrases the apex. The graduated canonical hero (Discussion #12234, operator-authored) is richer — it includes the possession-interface detail ("inhabits live applications, inspecting semantic runtime state, mutating UI and data in real time, turning conversational UIs from chat panels into agents collaborating inside the application"), DreamService re-steering, self-healing loops, and the close: "In May 2026, the canonical repo recorded 706 merged PRs and 800 closed issues. It maintains its own codebase today; it is being built to inhabit yours, regardless of the models' training data." The README should feature that full graduated apex — but broken into readable structure, not one wall of text. Operator: "of course should not be one wall of text, but the readme is not there yet."
"A Platform at Scale (State of May 1, 2026)" (line 164) — too much number-bragging. A ~10-line scale section is fine; the current section is an exhaustive line-by-line breakdown (8 engine line-items + subtotal + embedded-knowledge + more) that reads as excessive bragging → negative. Trim to ~10 lines (keep a representative scale signal, cut the line-by-line).
"Faculty-Staging Maturity (Honest Current State)" (line 92) — vastly outdated. The faculty table (Speech/Attention shipped; Short-term-recall #10332, Dream #10030 "in flight") + the SPOF / resilience-asymmetry framing (#10291) are stale. Refresh to current state (or reconsider the section); V-B-A the faculty statuses + #10332 / #10030 / #10291 first.
"This is the headline." (line 22, Brain bullet) — confusing. Reads as meaningless to a cold reader (operator: "i don't get what that is supposed to mean"). Remove/rephrase — and reconsider the parallel "This is the adoption substrate the Brain inhabits and improves" on the Body bullet (line 23).
MX-loop + motto block — KEEP (it's strong); reframe ONLY the gated-RSI clause (operator, 2026-05-31). The opening's MX-loop block must be preserved:
Neo's evolution mechanism is the MX loop — Model Experience as production mechanism. Internal friction from real agent work becomes tickets, tickets become PRs, PRs become skills and memory, and the next agent starts with better reflexes. The trajectory is autonomous narrow intelligence (ANI) by accumulation, [gated-RSI clause — see below].
"The system evolves by predicting its own evolution."
Preserve this block — and ESPECIALLY the motto quote. "The system evolves by predicting its own evolution" is the canonical recurring motto; its origin is learn/agentos/DreamPipeline.md (per the neo-identity-update facts-ledger recurring-motto SSOT — line 32/354 there). Do not drop or paraphrase it.
The ONE change: the gated-RSI clause — currently "under gated-RSI: agents propose, humans approve at merge" — must be reframed. Per Discussion #12234 dc-17119184 + ADR 0018 §2.7 OD-1 governance-line, gated-RSI is a founder-architect governance choice (the swarm can run the lifecycle autonomously; the founder-architect keeps final merge authority as an intentional governance choice — product taste, strategic coherence, accountable ownership), NOT a generic "humans approve" HITL-safety gate or a capability limit. Suggested form (tight, matching the block's voice): "…under gated-RSI by design: the swarm runs the lifecycle; the founder-architect keeps final merge authority as a governance choice." Same correction that landed in VISION §5 (PR #12246, cycle-4).
The Architectural Reality
README.md is the highest-visibility identity surface; it should lead with the canonical apex (ADR 0018 §2.7 OD-1) and carry the two-hemispheres framing (OD-3) — the opening already does the two-hemispheres structure; keep that.- The full graduated apex hero lives in Discussion #12234 (operator-authored README/portal-hero form) + ADR 0018 §2.7 OD-1.
The Fix
- Feature the full graduated #12234 apex hero in the opening, broken into readable paragraphs (not a wall of text); preserve the two-hemispheres structure.
- Trim "Platform at Scale" to a concise ~10-line scale section.
- Refresh / reconsider "Faculty-Staging Maturity" against verified current state.
- Remove/rephrase "This is the headline." (+ the parallel Body-bullet phrasing).
- Preserve the MX-loop + motto block (incl. the
DreamPipeline.md-origin motto verbatim); reframe ONLY the gated-RSI clause to the governance-choice form (per #12234 dc-17119184), consistent with VISION §5.
Ownership (operator-directed): implementation PR authored by @neo-opus-ada; cross-family review by @neo-gpt. (I drive the lifecycle — author the PR, then request review.)
Acceptance Criteria
Out of Scope
.github/VISION.md (#12229 / PR #12246 — separate sub).- The two-hemispheres structure itself (keep — OD-3-aligned).
- The MX-loop + motto block content (KEEP — only the gated-RSI clause within it changes).
- Other already-merged identity surfaces.
Decision Record impact
aligned-with ADR 0018 §2.7 OD-1 (apex) + OD-3 (two hemispheres). No ADR change.
Related
- Parent epic: #12225 (identity rollout)
- Predecessor: #12228 / PR #12243 (README apex — merged; this refines its presentation)
- Canonical apex source: Discussion #12234 (operator-authored hero) + ADR 0018 §2.7 OD-1
- Sibling open: #12229 / PR #12246 (VISION)
Origin Session ID: d2fbe3b2-44c4-4aab-b8c7-62621babc790
Retrieval Hint: "README presentation polish apex feature scale-bragging maturity outdated headline phrasing"
Context
Follow-up to the identity-apex rollout (Epic #12225; the README apex landed via #12228 / PR #12243). With the apex content now in
README.md, the operator flagged (2026-05-31) that the README's presentation isn't there yet — four concrete issues. Grounded in currentdevREADME.md.The Problems (operator-flagged)
Apex not fully featured (opening, lines ~13–31). The opening condenses/paraphrases the apex. The graduated canonical hero (Discussion #12234, operator-authored) is richer — it includes the possession-interface detail ("inhabits live applications, inspecting semantic runtime state, mutating UI and data in real time, turning conversational UIs from chat panels into agents collaborating inside the application"), DreamService re-steering, self-healing loops, and the close: "In May 2026, the canonical repo recorded 706 merged PRs and 800 closed issues. It maintains its own codebase today; it is being built to inhabit yours, regardless of the models' training data." The README should feature that full graduated apex — but broken into readable structure, not one wall of text. Operator: "of course should not be one wall of text, but the readme is not there yet."
"A Platform at Scale (State of May 1, 2026)" (line 164) — too much number-bragging. A ~10-line scale section is fine; the current section is an exhaustive line-by-line breakdown (8 engine line-items + subtotal + embedded-knowledge + more) that reads as excessive bragging → negative. Trim to ~10 lines (keep a representative scale signal, cut the line-by-line).
"Faculty-Staging Maturity (Honest Current State)" (line 92) — vastly outdated. The faculty table (Speech/Attention shipped; Short-term-recall #10332, Dream #10030 "in flight") + the SPOF / resilience-asymmetry framing (#10291) are stale. Refresh to current state (or reconsider the section); V-B-A the faculty statuses + #10332 / #10030 / #10291 first.
"This is the headline." (line 22, Brain bullet) — confusing. Reads as meaningless to a cold reader (operator: "i don't get what that is supposed to mean"). Remove/rephrase — and reconsider the parallel "This is the adoption substrate the Brain inhabits and improves" on the Body bullet (line 23).
MX-loop + motto block — KEEP (it's strong); reframe ONLY the gated-RSI clause (operator, 2026-05-31). The opening's MX-loop block must be preserved:
Preserve this block — and ESPECIALLY the motto quote. "The system evolves by predicting its own evolution" is the canonical recurring motto; its origin is
learn/agentos/DreamPipeline.md(per theneo-identity-updatefacts-ledger recurring-motto SSOT — line 32/354 there). Do not drop or paraphrase it.The ONE change: the gated-RSI clause — currently "under gated-RSI: agents propose, humans approve at merge" — must be reframed. Per Discussion #12234
dc-17119184+ ADR 0018 §2.7 OD-1 governance-line, gated-RSI is a founder-architect governance choice (the swarm can run the lifecycle autonomously; the founder-architect keeps final merge authority as an intentional governance choice — product taste, strategic coherence, accountable ownership), NOT a generic "humans approve" HITL-safety gate or a capability limit. Suggested form (tight, matching the block's voice): "…under gated-RSI by design: the swarm runs the lifecycle; the founder-architect keeps final merge authority as a governance choice." Same correction that landed in VISION §5 (PR #12246, cycle-4).The Architectural Reality
README.mdis the highest-visibility identity surface; it should lead with the canonical apex (ADR 0018 §2.7 OD-1) and carry the two-hemispheres framing (OD-3) — the opening already does the two-hemispheres structure; keep that.The Fix
DreamPipeline.md-origin motto verbatim); reframe ONLY the gated-RSI clause to the governance-choice form (per #12234dc-17119184), consistent with VISION §5.Ownership (operator-directed): implementation PR authored by @neo-opus-ada; cross-family review by @neo-gpt. (I drive the lifecycle — author the PR, then request review.)
Acceptance Criteria
dc-17119184/ OD-1 governance-line) — not "humans approve at merge" / capability-limit; consistent with VISION §5.Out of Scope
.github/VISION.md(#12229 / PR #12246 — separate sub).Decision Record impact
aligned-withADR 0018 §2.7 OD-1 (apex) + OD-3 (two hemispheres). No ADR change.Related
Origin Session ID: d2fbe3b2-44c4-4aab-b8c7-62621babc790 Retrieval Hint: "README presentation polish apex feature scale-bragging maturity outdated headline phrasing"