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	12447
title	Reshape pr-review §0 into the patch-blind premise snapshot + net-byte reduction
state	Closed
labels	enhancementaimodel-experience
assignees	neo-opus-ada
createdAt	Jun 3, 2026, 8:47 PM
updatedAt	Jun 7, 2026, 7:18 PM
githubUrl	https://github.com/neomjs/neo/issues/12447
author	neo-opus-grace
commentsCount	2
parentIssue	12442
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[x] 12486 refactor(agentos): codify "skills cite tool behavior, not mechanics" + slim the A2A commentId-handoff exemplar
closedAt	Jun 4, 2026, 11:41 AM

Reshape pr-review §0 into the patch-blind premise snapshot + net-byte reduction

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.2/.3/.6). Design by @neo-opus-ada.

Scope

The pr-review skill-body change — reshape §0 into the patch-blind premise snapshot, add the night-shift marker, and net-reduce the substrate.

Affected substrate

.agents/skills/pr-review/references/pr-review-guide.md §0/§7/§9 + the review template.

Acceptance Criteria

§0 reshaped to the patch-blind premise snapshot (3 fields):
- (a) inputs-read-before-patch — ticket/issue, changed-file list, current dev source, sibling precedent, source-of-authority substrate — NOT the PR's self-description as primary premise;
- (b) expected-solution-shape — 1–3 sentences incl. "what boundary should this NOT hardcode?" + "what test-isolation should exist?" (so it reaches the portability + test-isolation dimensions);
- (c) patch-verdict — matches / improves / contradicts + the evidence that changed the reviewer's mind.
- Framed patch-blind, NOT a temporally-guaranteed pre-commitment (overclaiming temporality = theater).
Night-shift provisional marker (single-family — calibration-deferred-to-merge-gate) for single-family / human-asleep approvals.
Net-byte: net-reduce the ≈696-line pr-review substrate via conditional Atlas payloads (§0 absorbs mass; no 9th always-loaded section). Declare the delta.
Floor/ceiling residual archived (diversity-ceiling = #12429 → Epic #12440).

Coordination

The template/anchor changes here must align with the validation-contract sequencing sub (the add-as-optional → migrate → enforce leg) so the lint doesn't break in-flight reviews.

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

tobiu closed this issue on Jun 4, 2026, 11:41 AM