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	13816
title	fix(ai): archaeology-hook error message names only "tickets" but the gate also bans ADR/Epic/Discussion refs (quick-win of #13813)
state	Closed
labels	aimodel-experience
assignees	neo-opus-ada
createdAt	Jun 21, 2026, 10:36 PM
updatedAt	Jun 21, 2026, 11:00 PM
githubUrl	https://github.com/neomjs/neo/issues/13816
author	neo-opus-ada
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jun 21, 2026, 11:00 PM

Discussion refs (quick-win of #13813)

Closed v13.1.0/archive-v13-1-0-chunk-5 aimodel-experience

neo-opus-ada commented on Jun 21, 2026, 10:36 PM

Quick-win slice of #13813

buildScripts/util/check-ticket-archaeology.mjs bans ADR-NNNN refs in durable comments (regex L26 /\bADR[-\s]?\d{3,4}\b/i) and its CLI .description() (L150) correctly says "ticket/Epic/Discussion/ADR refs" — but the failure message (L207 "ticket ref(s)", L210 "must … not cite tracking tickets") names only tickets. An agent who removes the #NNNN refs then re-commits is surprised by the ADR-ban on the next round.

Empirical: this cost 3 of 4 commit-retry rounds on one refactor this session (@neo-opus-ada, #13794 discussions build) — I removed #11573, then hit ADR-0011 three separate times because the message never said ADRs were banned.

Fix

L207: ${n} ticket ref(s) → ${n} decay-prone ref(s) (ticket/Epic/Discussion/ADR).
L210: not cite tracking tickets → not cite tracking refs (tickets, Epics, Discussions, or ADRs).

Pure message-clarity; the detection regexes + the ticket-ref-ok escape are unchanged.

AC

The failure message names ADR/Epic/Discussion refs (not just "tickets"), matching the L26 regex set + the L150 description.
No detection/behavior change (regexes + escape marker unchanged).

Quick-win of #13813 (the broader commit/PR-preflight stays on #13813). Surfaced by @neo-opus-ada.

tobiu referenced in commit 3e98295 - "fix(ai): archaeology-hook failure message names ADR/Epic/Discussion refs, not just tickets (#13816) (#13817) on Jun 21, 2026, 11:00 PM

tobiu closed this issue on Jun 21, 2026, 11:00 PM