Context
The Engine README is the strongest current organization-level identity surface, but the repository split changed what “this repository” contains. The README needs an explicit organization map so readers can distinguish the parent Neo organism from the Engine package they are currently viewing.
The operator selected the five primary repositories and requires a visible “you are here” marker. This ticket changes the Engine README only.
Live latest-open sweep: checked the latest 20 open Engine issues immediately before creation; no equivalent organization-map README ticket exists. A2A in-flight sweep: latest 30 messages across read states contained no competing Engine README claim.
The Problem
The README explains Body and Brain in prose, but it does not provide a compact repository map covering the now-independent Engine, Brain, Institution, DevIndex and Skills products. Cold readers can therefore understand the organism and still miss where they are, which repository owns the next action, or which sibling contains the linked subsystem.
The Architectural Reality
README is the ADR 0018 apex framing surface. It should describe the parent organism first, then segment by the audience of this repository. The Engine README remains the baseline narrative; this ticket adds repository location and tightens Engine-specific doors without rewriting the identity thesis.
The Fix
Update README.md:
- Preserve the current organism-level opening and canonical Introduction relationship.
- Add a concise five-repository bulleted map near the front:
neomjs/neo — Body / Engine ← you are here;
neomjs/neo-agent-brain — Brain / Agent OS;
neomjs/neo-agent-institution — Institution application;
neomjs/devindex — developer/repository intelligence;
neomjs/neo-agent-skills — canonical Skills substrate.
- Ensure Engine quickstart, architecture and contribution doors remain primary for this repository.
- Replace stale filesystem-relative Brain doors with canonical sibling links where necessary.
Contract Ledger Matrix
| Target Surface |
Source of Authority |
Proposed Behavior |
Fallback |
Docs |
Evidence |
| README organization map |
live neomjs repositories + operator direction |
Five links, one-line ownership, exactly one “you are here” marker |
Omit a repository only if it is not a public product surface |
README |
Link/status check |
| README apex |
canonical learn/benefits/Introduction.md + ADR 0018 |
Preserved organization narrative, audience-segmented toward Engine |
Reuse current copy when already current |
README |
Cross-family framing review |
| Engine next-step doors |
Engine package/product authority |
Engine install/build/learn/contribute remain primary |
Sibling links remain secondary |
README |
Fresh-reader route audit |
Decision Record impact
Aligned-with ADR 0018. No ADR change.
Acceptance Criteria
Out of Scope
Engine package.json · Brain README · Portal/Pages/middleware · generated sitemap/llms.txt · product naming · repository extraction.
Avoided Traps
- Rewriting the entire README when the current organism narrative is the baseline.
- Turning the Engine README into an organization portal with no Engine-specific primary door.
- Duplicating detailed sibling documentation instead of linking its canonical owner.
Related
Identity authority: #12203 / ADR 0018
Repository split: #17500
Origin Session ID: 14f81b5f-435b-4f00-92fc-67503eb0602e
Retrieval Hint: Engine README five repository organization map you are here
Context
The Engine README is the strongest current organization-level identity surface, but the repository split changed what “this repository” contains. The README needs an explicit organization map so readers can distinguish the parent Neo organism from the Engine package they are currently viewing.
The operator selected the five primary repositories and requires a visible “you are here” marker. This ticket changes the Engine README only.
Live latest-open sweep: checked the latest 20 open Engine issues immediately before creation; no equivalent organization-map README ticket exists. A2A in-flight sweep: latest 30 messages across read states contained no competing Engine README claim.
The Problem
The README explains Body and Brain in prose, but it does not provide a compact repository map covering the now-independent Engine, Brain, Institution, DevIndex and Skills products. Cold readers can therefore understand the organism and still miss where they are, which repository owns the next action, or which sibling contains the linked subsystem.
The Architectural Reality
README is the ADR 0018 apex framing surface. It should describe the parent organism first, then segment by the audience of this repository. The Engine README remains the baseline narrative; this ticket adds repository location and tightens Engine-specific doors without rewriting the identity thesis.
The Fix
Update
README.md:neomjs/neo— Body / Engine ← you are here;neomjs/neo-agent-brain— Brain / Agent OS;neomjs/neo-agent-institution— Institution application;neomjs/devindex— developer/repository intelligence;neomjs/neo-agent-skills— canonical Skills substrate.Contract Ledger Matrix
learn/benefits/Introduction.md+ ADR 0018Decision Record impact
Aligned-with ADR 0018. No ADR change.
Acceptance Criteria
neomjs/neoalone carries the visible “you are here” marker.Out of Scope
Engine
package.json· Brain README · Portal/Pages/middleware · generated sitemap/llms.txt· product naming · repository extraction.Avoided Traps
Related
Identity authority:
#12203/ ADR 0018Repository split:
#17500Origin Session ID: 14f81b5f-435b-4f00-92fc-67503eb0602e
Retrieval Hint:
Engine README five repository organization map you are here