What is the Neural Link?

The Neural Link is a bi-directional bridge that connects AI agents directly to the Neo.mjs runtime. It lets agents inspect the Scene Graph, component state, event listeners, computed styles, and DOM rectangles, and mutate the running application in real time.

Why is Neo.mjs called an Application Engine instead of a framework?

Neo.mjs maintains persistent application objects in a worker-backed Scene Graph instead of compiling application state away into ephemeral DOM nodes. That architecture enables multi-window orchestration, runtime permutation, and deep AI introspection.

What is Context Engineering?

Context Engineering shapes the information and tool environment around AI agents. Neo.mjs implements it through Knowledge Base, Memory Core, GitHub Workflow, and Neural Link MCP servers for frontier harnesses, plus a File System MCP server for internal Neo.ai.Agent local loops.

What is the Neo.mjs Agent OS?

The Neo.mjs Agent OS is the repository Brain: source code and services for Memory Core, Knowledge Base, Active Hybrid GraphRAG, DreamService, Golden Path synthesis, A2A coordination, and Neural Link tooling.

Frontmatter

id	11564
title	Migrate ADR and docs refs to semantic anchors
state	Closed
labels	documentationenhancementaiarchitecture
assignees	neo-gemini-pro
createdAt	May 18, 2026, 2:51 AM
updatedAt	May 18, 2026, 7:29 PM
githubUrl	https://github.com/neomjs/neo/issues/11564
author	neo-gpt
commentsCount	1
parentIssue	11558
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	May 18, 2026, 7:29 PM

Migrate ADR and docs refs to semantic anchors

Closed v13.0.0/archive-v13-0-0-chunk-12 documentationenhancementaiarchitecture

neo-gpt commented on May 18, 2026, 2:51 AM

Context

Epic #11558 includes ADR and general documentation references after the policy, lint, AGENTS maps, and skill partitions are defined. This final partition handles non-skill documentation without collapsing active references and historical archaeology into the same treatment.

The Problem

ADR and documentation files can contain positional §N references with different meanings: some are live guidance references that should migrate, while others are historical references to the state at the time of a decision. Treating both classes identically risks either stale live guidance or damaged archaeology.

The Architectural Reality

Discussion #11557 v5 and Gemini cycle-4 StepBack require an active-vs-archive boundary. Historical/archaeology refs either preserve original numbering intentionally or get an explicit errata class. Live documentation refs should use semantic anchors once the policy and map anchors exist.

The Fix

Audit and migrate ADR / documentation references according to the semantic-anchor policy from #11559:

live guidance references migrate to semantic anchors
historical/archaeology references are preserved intentionally with classification or errata
no broad prose rewrites unrelated to reference identity

Discussion Criteria Mapping

OQ1 historical/archaeology refs -> preserve intentionally or classify as errata.
Active/archive boundary -> this ticket owns non-skill docs treatment.
Migration blast-radius partial -> bounded docs/ADR partition with explicit evidence.
OQ6 ADR vehicle -> depends on policy ADR from #11559.

Acceptance Criteria

ADR and docs refs to live AGENTS/ATLAS/skill sections use semantic anchors where appropriate.
Historical/archaeology refs are explicitly preserved, classified, or documented as errata.
No broad stylistic rewrites are included.
Lint evidence from #11560 is included if applicable.
PR body includes examples of at least one migrated live ref and one intentionally preserved historical ref, if both classes are present.

Out of Scope

Migrating skill files.
Changing ADR decisions beyond reference mechanics and explicit errata.
Reopening old architectural decisions.

Avoided Traps / Gold Standards Rejected

Blind global search-and-replace is rejected because historical references need archaeological context.
Leaving stale live refs because they appear in docs is rejected; live guidance still participates in Option C.

Parent Epic: #11558
Policy ADR ticket: #11559
Lint ticket: #11560
AGENTS map ticket: #11561
Skill migration ticket: #11562
Discussion: #11557

Origin Session ID: 6e5b995a-c68e-4179-840c-a4cc48d449da Retrieval Hint: "ADR docs semantic anchors historical archaeology active archive boundary #11558"

tobiu referenced in commit 5f4c575 - "feat(ci): PR-diff-scoped semantic-anchor lint for agent skills (#11560) (#11572) on May 18, 2026, 9:20 AM

tobiu May 18, 2026, 7:29 PM

absolutely not. superseded by https://github.com/orgs/neomjs/discussions/11577

tobiu closed this issue on May 18, 2026, 7:29 PM