LearnNewsExamplesServices
Frontmatter
id12227
titleRe-categorize discovery surfaces to the canonical apex
stateClosed
labels
documentationenhancementai
assigneesneo-gpt
createdAtMay 30, 2026, 11:25 PM
updatedAtJun 7, 2026, 7:17 PM
githubUrlhttps://github.com/neomjs/neo/issues/12227
authorneo-opus-ada
commentsCount0
parentIssue12225
subIssues[]
subIssuesCompleted0
subIssuesTotal0
blockedBy[]
blocking[]
closedAtMay 31, 2026, 6:15 AM

Re-categorize discovery surfaces to the canonical apex

Closed Backlog/active-chunk-16 documentationenhancementai
neo-opus-ada
neo-opus-ada commented on May 30, 2026, 11:25 PM

Parent epic: #12225

Context

Neo is filed under "framework" on its discovery surfaces, which points the worst-fit audience (React/Angular shoppers) at it while the audience that would value an autonomous engineering Agent OS never sees it. The discovery metadata leads with the Body and omits the Brain.

This sub now runs under the canonical apex from ADR 0018 §2.7 OD-1 and Epic #12225:

Neo.mjs is a self-evolving software organism — a professional, end-to-end AI engineering team that lives in its own open-source repository.

The Body (/src/) runtime and Brain (/ai/) Agent OS are the two hemispheres beneath that apex. This ticket is the discovery-surface recategorization slice; it should not revert to the older institution-only lead noun.

The Fix

Bring the discovery surfaces into line with the canonical organism apex, per the neo-identity-update skill's facts-vs-framing model:

  • package.json — description leads with the self-evolving software organism / professional AI engineering team framing while keeping the Body as the adoption substrate; keywords add ai-agents, agent-os, multi-agent, mcp, agentic; remove framework-axis tags that re-enter the trap (e.g. react-alternative).
  • GitHub repo description + topics — mirror the package.json description; add the agent/AI-OS topics. (External-platform: the sub specifies the exact strings; an operator with repo admin applies them — they are out-of-git.)

Facts (version, counts) stay at their SSOT and are not hand-edited here.

Contract Ledger Matrix

Target Surface Source of Authority Proposed Behavior Fallback Docs Evidence
package.json description ADR 0018 §2.7 OD-1; neo-identity-update framing governance concise machine-surface form Replace the runtime-only description with concise organism-apex package/GitHub register: Neo.mjs is a self-evolving software organism: a professional end-to-end AI engineering team whose cross-model swarm inhabits live apps via Neural Link, Active Hybrid GraphRAG, DreamService, and self-healing loops. If npm length/readability proves too long, keep the same noun stack but shorten without dropping self-evolving software organism, professional AI engineering team, and Neural Link PR body node -e package inspection + PR diff
package.json keywords[] ADR 0018 keyword cluster; #12225 affected-areas taxonomy Add AI/Agent-OS discovery terms (self-evolving, software-organism, autonomous-agent-os, professional-ai-engineering-team, ai-agents, agent-os, multi-agent, mcp, agentic, active-hybrid-graphrag, dreamservice, neural-link, possession-interface, cross-family-pr-review) and remove framework-trap tags such as react-alternative If package keyword volume is already high, prefer replacing stale/trap terms over unbounded growth PR body JSON parse + keyword membership check
GitHub repo description Same as package description Document the exact proposed description for operator/admin application; do not silently skip because it is out-of-git If the agent has repo-admin authority and operator intent is explicit, apply with gh repo edit; otherwise leave as PR-body/operator checklist PR body, out-of-git section gh repo view neomjs/neo --json description,repositoryTopics before/after or checklist
GitHub repo topics ADR 0018 keyword cluster; GitHub 20-topic practical cap Document exact proposed topics for operator/admin application, replacing framework-trap topics (react-alternative) with organism/Agent-OS topics If the 20-topic cap forces tradeoffs, retain mixed Brain+Body discovery: organism/Agent-OS terms plus application-engine, multi-threaded, off-main-thread, javascript PR body, out-of-git section gh repo view before/after or checklist
Facts (version, engines, counts) facts-ledger.md Do not edit facts in this framing/discovery sub If a stale fact is found while editing, route to #12231 #12231 Diff contains no fact changes

Proposed External-Platform Values

These are out-of-git unless an admin/operator applies them.

  • GitHub repo description: Neo.mjs is a self-evolving software organism: a professional end-to-end AI engineering team whose cross-model swarm inhabits live apps via Neural Link, Active Hybrid GraphRAG, DreamService, and self-healing loops.
  • GitHub repo topics (20): self-evolving, software-organism, autonomous-agent-os, professional-ai-engineering-team, ai-agents, agent-os, multi-agent, mcp, model-context-protocol, active-hybrid-graphrag, dreamservice, neural-link, possession-interface, self-healing, cross-family-pr-review, application-engine, multi-threaded, off-main-thread, javascript, pwa

Acceptance Criteria

  • package.json description + keywords updated to the canonical apex; framework-trap tags removed
  • Exact proposed GitHub description + topics documented for operator application (out-of-git)
  • No fact duplicated into these surfaces that is not derived from its SSOT
  • Cross-family review per ADR 0018 §2.6

Out of Scope

  • README opening rewrite (sibling sub)
  • npm page (derives from package.json on publish)

Related

  • Parent: #12225 · Model: ADR 0018 §2.7 OD-1

Origin Session ID: 94a91ebc-d325-4d32-a746-4ff8c26c0342 Retrieval Hint: "re-categorize package.json keywords github topics organism apex"

tobiu referenced in commit a040035 - "feat(identity): recategorize discovery metadata (#12227) (#12239) on May 31, 2026, 6:15 AM
tobiu closed this issue on May 31, 2026, 6:15 AM