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.

Neo.mjs - Self-Evolving Software Organism

Frontmatter

title	Docs: Modernize Historical Context and Sandbox topology in CodebaseOverview
author	tobiu
state	Merged
createdAt	Apr 11, 2026, 10:30 AM
updatedAt	Apr 11, 2026, 6:11 PM
closedAt	Apr 11, 2026, 10:31 AM
mergedAt	Apr 11, 2026, 10:31 AM
branches	`dev` ← `agent/9877-docs-sandbox-topology`
url	https://github.com/neomjs/neo/pull/9878

Merged

tobiu commented on Apr 11, 2026, 10:30 AM

Resolves #9877

Architectural Summary

This Pull Request modernizes the Historical Context routing within the Codebase Overview to properly guide external agents and humans to the synced local records utilized by the Agent OS.

Fat Ticket Details

Directory Migrations: Shifted all deprecated .github/RELEASE_NOTES/ and .github/ISSUE_ARCHIVE/ paths to the structurally correct resources/content/release-notes/ and resources/content/issue-archive/ namespaces.
Pull Requests and Discussions Pipeline: Documented the addition of PRs and Discussions/Ideation Sandbox as synced elements.
Search Paradigm Shift: Upgraded the "When Stuck" troubleshooting checklist to direct queries towards pull type queries for execution history and discussion type queries for underlying architectural rationale ("The Why").

These adjustments ensure that search directives accurately map to the true offline storage vectors used by the Retrospective Daemon and the Knowledge Base servers.

tobiu commented on Apr 11, 2026, 10:30 AM

Input from Gemini 3.1 Pro (Antigravity):

✦ # PR Review Summary

Status: Approved

Excellent rapid follow-up. Correcting these deprecated directory paths and actively incorporating the Ideation Sandbox (Discussions) and active Pull Requests into our "When Stuck" troubleshooting guide is essential for keeping the swarm's vector search aligned with our true data structures.

📊 Evaluation Metrics

[ARCH_ALIGNMENT]: 100 - Effectively maps internal Knowledge Base search directives to the actual physical sync topology utilized by the Memory Core.

[CONTENT_COMPLETENESS]: 100 - Fat Ticket PR body highlights the exact migration of deprecated locations and the addition of PR/Discussions into the knowledge index.

[EXECUTION_QUALITY]: 100 - Clean markdown transition across 2 non-contiguous blocks, maintaining the aesthetic format of the original guide.

[PRODUCTIVITY]: 100 - Solved the outdated path goal definitively.

[IMPACT]: 20 - Informational update. Very low runtime risk, but incredibly high impact for the efficiency of future Agent OS search operations.

[COMPLEXITY]: 10 - Standard multi-block Markdown refactoring.

[EFFORT_PROFILE]: Quick Win - Straightforward update matching the precise architectural directives.

🕸️ Context & Graph Linking

Target Epic / Issue ID: Resolves #9877

Related Graph Nodes: learn/guides/fundamentals/CodebaseOverview.md, resources/content/*

🧠 Graph Ingestion Notes

[KB_GAP]: None. This PR directly resolves a KB GAP where Agents might have attempted to query non-existent .github archive directories instead of the active resources/content proxies.

[TOOLING_GAP]: None.

[RETROSPECTIVE]: Redirecting "When Stuck" troubleshooting advice to explicitly include Pull Requests (for execution history) and Discussions (for the architectural "Why") will significantly improve context extraction rates for future Swarm tasks facing unknown unknowns.

📋 Required Actions

To proceed with merging, please address the following:

None. Ready for Squash Merge.