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	12448
title	Sequence the premise-snapshot validation-contract change (lint + PullRequestService + openapi)
state	Closed
labels	enhancementaimodel-experience
assignees	neo-gpt
createdAt	Jun 3, 2026, 8:47 PM
updatedAt	Jun 7, 2026, 7:18 PM
githubUrl	https://github.com/neomjs/neo/issues/12448
author	neo-opus-grace
commentsCount	1
parentIssue	12442
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jun 4, 2026, 1:03 PM

Sequence the premise-snapshot validation-contract change (lint + PullRequestService + openapi)

Closed v13.0.0/archive-v13-0-0-chunk-15 enhancementaimodel-experience

neo-opus-grace commented on Jun 3, 2026, 8:47 PM

Sub-ticket of Epic #12442 (Pr-review premise gate). Graduated from Discussion #12432 (B-prime.7 + @neo-claude-opus's §5.2 Step-Back highest-care item).

Scope

The validation/graph-contract change for the new premise-snapshot anchors — sequenced so in-flight reviews don't break. This is the highest-care leg (a CI-coupled contract change, not prose).

Affected substrate

.github/workflows/agent-pr-review-body-lint.yml (the 7-anchor lint).
ai/services/github-workflow/PullRequestService.mjs.
openapi.yaml.
ConceptDiscoveryService (graph-ingestion of review anchors).

Acceptance Criteria

New premise-snapshot anchors added to the contract as optional first (add-as-optional).
Existing review templates / consumers migrated to the new anchors (migrate).
Contract flipped to enforce only after migration (enforce).
Sequence verified to NOT break in-flight reviews at any step.

Rationale

B-prime's premise-snapshot is a validation/graph contract change. The add-as-optional → migrate → enforce sequence is the §5.2-flagged highest-care item — flipping the lint to require new anchors before consumers emit them would fail every open review.

Origin: Discussion #12432 → Epic #12442 (design @neo-opus-ada). Session e886ae3e-13c0-4a94-9713-f8316e2342d0.