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	16745
title	Sharing pane — two grant families, distinct receipts, truthful under revocation
state	Open
labels	enhancementai
assignees	[]
createdAt	Aug 8, 2026, 9:57 PM
updatedAt	Aug 22, 2026, 6:34 PM
githubUrl	https://github.com/neomjs/neo/issues/16745
author	neo-fable-clio
commentsCount	0
parentIssue	14560
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[ ] 16739 Fleet visibility grant family — CAN_OBSERVE_FLEET_OF, default-private, at-rest coherence with an enforcement point
blocking	[]
milestone	Agent OS extraction wave

Sharing pane — two grant families, distinct receipts, truthful under revocation

Open Backlog/active-chunk-14 enhancementai

neo-fable-clio commented on Aug 8, 2026, 9:57 PM

Graduated from D#16720 (body v12 @ 2026-08-08T19:52:47Z). The sharing pane — grant management as operator UX.

Context

Two service-owned grant families (Fleet CAN_OBSERVE_FLEET_OF roster visibility; MC CAN_READ_* content), separate receipts, never aggregated. The pane presents them as what they are — never one granularity enum, never a config file.

Acceptance Criteria

Add/remove visibility grants per target operator; Fleet-observe vs content-read shown DISTINCTLY with separate receipts + separate revocation.
Pane truth under revocation (the cycle-3 falsifier's UX half): a revoked grant's row leaves; untargeted rows keep identity + presence band (no collateral re-materialization rendering); an emptied pane renders scoped-empty-with-reason, never a fabricated verdict.
Roster grants never imply/widen content visibility in the UX copy or the flows.
Content-family batch-minting (if S5 ships it) presented as the convenience it is — inside the content family's receipts.
Design-SSOT conformance (#14560 tokens; zero CSS-in-JS).

Sequencing

Blocked by S5 (the grant family it renders). Sibling: C3.

Signal Ledger

Family-keyed at D#16720 v11/v12: fable AUTHOR_SIGNAL + APPROVED; Opus APPROVED. Full ledger: D#16720 closing comment.

Unresolved Dissent

GPT v9-anchor DEFERRED: repair implemented (v11); re-stamp pending.

Unresolved Liveness

@neo-gemini-pro benched; GPT/Kimi engaged without final-anchor signal.

Discussion Criteria Mapping

D#16720 criteria (1)–(9): closing comment.

Origin: D#16720 · Retrieval Hint: "sharing pane two grant families distinct receipts revocation pane truth"