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	14329
title	docs(agentos): author the hooks & mechanical-enforcement guide (stop hooks · lane-state · no-hold)
state	Closed
labels	documentationaiarchitecture
assignees	neo-gpt
createdAt	Jun 29, 2026, 11:46 AM
updatedAt	Jun 30, 2026, 2:43 AM
githubUrl	https://github.com/neomjs/neo/issues/14329
author	neo-opus-grace
commentsCount	0
parentIssue	14310
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jun 30, 2026, 2:43 AM
milestone	v13.1

docs(agentos): author the hooks & mechanical-enforcement guide (stop hooks · lane-state · no-hold)

Closed v13.1.0/archive-v13-1-0-chunk-8 documentationaiarchitecture

neo-opus-grace commented on Jun 29, 2026, 11:46 AM

Part of #14310 · content rubric + §Mandatory V-B-A grounding in #14310. Refs #14310.

Problem: the mechanical-enforcement layer — stop hooks, lane-state enforcement, the no-hold gate — has no guide. In cloud, agents read messages at turn-start + hooks keep them on-task; this is how the swarm runs unattended without wakes. (Mechanical enforcement replacing prompt-machinery = #13652 territory.)

Acceptance Criteria

New guide: what hooks are; the stop-hook / lane-state enforcement; the no-hold mechanism; mechanical enforcement vs prompt-machinery.
How it fits local (wakes/heartbeats) vs cloud (turn-start reads + hooks keep agents driving).
problem → resolve → why-care → what's-in-it; honest.
Registered in tree.json.

⚠️ V-B-A grounding (mandatory before writing): .claude/hooks/ (laneStateStopHook.mjs + the hook wiring in settings.json), epic #13652 (mechanical enforcement replaces prompt-machinery), the actual stop-hook behavior + triggers. Write from VERIFIED reality; capture grounding evidence in the PR.

Files: new learn/agentos/Hooks.md (name TBD) + learn/tree.json.

tobiu referenced in commit f4329e4 - "docs(agentos): add hooks guide (#14329) (#14373)" on Jun 30, 2026, 2:43 AM

tobiu closed this issue on Jun 30, 2026, 2:43 AM