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	15506
title	TOKENS.md post-ruling truth-fold: the resolved-failures note + --fm-ink-faint''s threshold class
state	Closed
labels	designai
assignees	neo-opus-grace
createdAt	Jul 18, 2026, 8:21 PM
updatedAt	Jul 18, 2026, 8:43 PM
githubUrl	https://github.com/neomjs/neo/issues/15506
author	neo-opus-grace
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jul 18, 2026, 8:43 PM

TOKENS.md post-ruling truth-fold: the resolved-failures note + --fm-ink-faint's threshold class

Closed Backlog/active-chunk-7 designai

neo-opus-grace commented on Jul 18, 2026, 8:21 PM

Context

Residual of my own two design leaves landing back-to-back: #15500 → PR #15502 (D3, --fm-state-off retune) and #15493 → PR #15496 (D4, --fm-ink-faint non-text reclassification). Both merged within minutes of each other; neither folded the shared prose that the other one invalidated. Filing it rather than leaving known-stale doc on dev.

The Problem

Two statements in apps/agentos/TOKENS.md are now false on dev:

The open-failures note still says "One open failure, ruled and awaiting its implementing leaf … Implementing leaf: #15493." That leaf merged (PR #15496, 2026-07-18T18:20:38Z). The note advertises pending work that is done.
The contrast row still grades --fm-ink-faint against the 4.5 TEXT threshold with ❌ failure marks. PR #15496 reclassified the token as non-text only — and the table's own stated rule is that "threshold is set by usage class … argued from this table's Role column, never from the token's name." Grading a now-decorative token against the text threshold contradicts the table's own method, and the ❌ marks read as live defects when the defect was resolved by reclassification.

This is the exact failure mode the D4 ruling was about — documentation asserting something the code no longer does — so leaving it would be ironic as well as wrong.

The Fix

Fold the note to "No open contrast failures", keeping both rulings' reasoning recorded (the delta rule wants the decision visible, not just the outcome).
Reclassify the --fm-ink-faint row's AA column to n/a — decorative, keeping the measured ratios for reference rather than as a gate it is no longer measured against.
Record the sharper fact the reclassification implies: at 2.64–3.27 the token clears the 3.0 non-text floor on only two of eight surface/skin combinations, so it cannot be relied on for information-bearing non-text either — decorative is the honest class, not merely "non-text".

Acceptance Criteria

No statement in TOKENS.md claims a pending implementing leaf that has merged.
--fm-ink-faint's row carries no AA threshold it is not measured against, and no ❌ marks for a resolved reclassification.
Both rulings' reasoning survives the fold (decision visible, per the delta rule).
check-agentos-theme green (docs-only change; no token values move).

Out of Scope

D2 (StateDot 1.4.1 third channel) — still open; the Motion section's audit text stays as-is.
Any token value change — D3's retune already landed.

#14805 (epic) · #15493 / PR #15496 (D4) · #15500 / PR #15502 (D3) · #14619 (the measured table) · #14578 (TOKENS.md authority).

Live latest-open sweep at 2026-07-18T18:22Z; no equivalent doc-fold ticket exists (the nearest, #15494/#15495, are the learn/ self-description purge — disjoint).

Authored by Grace (Claude Opus 4.8, Claude Code).