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	14639
title	FM module event-kind map: the data-driven kind→token registry
state	Closed
labels	enhancementdeveloper-experienceai
assignees	neo-opus-vega
createdAt	5:31 AM
updatedAt	11:31 AM
githubUrl	https://github.com/neomjs/neo/issues/14639
author	neo-opus-vega
commentsCount	0
parentIssue	14560
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	11:31 AM

FM module event-kind map: the data-driven kind→token registry

Closed Backlog/active-chunk-3 enhancementdeveloper-experienceai

neo-opus-vega commented on 5:31 AM

Context

B-split of #14594 (horizon map v2): the kind→token mapping as its own leaf — pure data + a tiny resolver, so kind-set growth (lane-claims, graduations, lifecycle transitions beyond the SSOT's four) is one map entry, zero component edits.

The Fix

(1) The kind registry (module-scoped data: pr/a2a/review/alert + the FLEET_COCKPIT_EVENT_TYPES lifecycle kinds from the merged DTO, each → token + label casing) + a resolver with the neutral fallback; (2) unit specs — known kinds resolve, unknown → neutral (never throw/invisible), DTO event-types covered 1:1; (3) doc row in TOKENS.md's consumer table.

Acceptance Criteria

Registry covers the SSOT four + all FLEET_COCKPIT_EVENT_TYPES; adding a kind = one entry (fixture proves no component edit).
Unknown-kind → neutral resolution (fixture).
Consumed by the EventChip leaf (#14594, narrowed) — the resolver is its only kind source.

Out of Scope

The chip COMPONENT (#14594, narrowed) · adapter classification (Lane C).

Epic #14560 (parent) · split-of #14594 · src/ai/fleet/fleetCockpitStatus.mjs (the kind source) · merged tokens.

Sweeps: current window; no equivalent; A2A clean. Structure-map: N/A.

Origin Session ID: a28f1415-37a4-4a5a-a3e4-b56adf6274ec Retrieval Hint: "event kind map registry resolver neutral fallback"

tobiu referenced in commit 38cadfb - "feat(agentos): event-kind chip + kind registry (#14594, #14639) (#14701) on 11:31 AM

tobiu closed this issue on 11:31 AM