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	14862
title	feat(fleet): fleetActivity read-observe bridge capability + activitySource honest-degrade seam
state	Closed
labels	[]
assignees	neo-opus-vega
createdAt	Jul 5, 2026, 8:10 PM
updatedAt	Jul 5, 2026, 9:53 PM
githubUrl	https://github.com/neomjs/neo/issues/14862
author	neo-opus-vega
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jul 5, 2026, 9:53 PM

feat(fleet): fleetActivity read-observe bridge capability + activitySource honest-degrade seam

Closed Backlog/active-chunk-4 []

neo-opus-vega commented on Jul 5, 2026, 8:10 PM

Sub of #14606 (FM cockpit ActivityStream live-binding) — the Brain-side prerequisite.

The ActivityStream component + bounded buffer + kind-delegation are done (#14831), and the A2A (#14572) + PR/lane (#14573) activity adapters are closed — but no activity feed is exposed to the app: createFleetCockpitStatus and the adapters have no consumable bridge/NL method. This slice adds the exposure capability so the ActivityStream can bind a live feed instead of a fixture.

Scope

fleetActivity read-observe verb on the app↔fleet wire allowlist (FLEET_WIRE_METHODS) + FleetControlBridge (auto-exposed by createFleetRegistryBridge, routed by dispatchFleetRequest).
Delegates to an injectable activitySource collaborator — the composed A2A + PR/lane adapters, orchestrator-wired with the mailbox / PR read paths whose identity binding it owns (the adapters' DI contract: they consume an injected listMessages, never import the singleton).
Mirrors the bootIdentitySource seam: unwired → an honest source-not-wired snapshot ({capability: not-wired, events: []}), never fabricated activity. No lifecycle-write authority (the R3 read-observe seam).

Acceptance Criteria

fleetActivity on FLEET_WIRE_METHODS + implemented on FleetControlBridge.
Wired activitySource → passes the snapshot through (bounds forwarded); unwired → honest degrade.
Unit-tested (injected source + honest degrade + the wire-allowlist exact-set guard).

Out of scope (follow-up slices of #14606)

App-side binding (FleetCockpit polls fleetActivity → ActivityStream.events, honest-degrade).
Orchestrator-side real activitySource wiring (mailbox + PR adapters).
The NL-verifiable live e2e mount (builds on the #14859 hardened fixture).

Filed by Vega (@neo-opus-vega).

tobiu closed this issue on Jul 5, 2026, 9:53 PM