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	14203
title	composeTurnDocumentText pure helper — single-source the turn-document derivation (slice 1 of the #14193 de-dup)
state	Closed
labels	enhancementaiarchitecture
assignees	neo-opus-ada
createdAt	Jun 27, 2026, 6:41 AM
updatedAt	Jun 27, 2026, 11:08 AM
githubUrl	https://github.com/neomjs/neo/issues/14203
author	neo-opus-ada
commentsCount	0
parentIssue	14193
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jun 27, 2026, 11:08 AM

composeTurnDocumentText pure helper — single-source the turn-document derivation (slice 1 of the #14193 de-dup)

Closed v13.1.0/archive-v13-1-0-chunk-7 enhancementaiarchitecture

neo-opus-ada commented on Jun 27, 2026, 6:41 AM

Slice 1 of the #14193 field↔document de-dup.

Scope (this ticket)

A pure, single-source helper composeTurnDocumentText({prompt, thought, response}) (ai/services/memory-core/helpers/turnDocumentText.mjs) that derives the canonical User Prompt: … / Agent Thought: … / Agent Response: … text currently built inline at the MemoryService write path — plus its unit test. Primitive-first, zero data touch, no MemoryService edit.

Why

The de-dup (#14193) drops the redundant stored document and reconstructs it on read from the canonical split fields (metadata.prompt/thought/response). That reconstruct must be byte-identical to the original construction, which first requires the format to live in ONE place. This helper is that single source.

Out of scope (later slices)

Slice 2: wire the write path to use the helper + reconstruct on read — gated on #14192 (the Chroma FTS5 reclaim establishing no document-FTS consumer).
Slice 4: the one-time data migration reclaiming existing records.
Summaries (distinct document shape) are excluded throughout.

Refs #14193 (parent), #14192 (Chroma FTS5 reclaim — the no-document-FTS-consumer premise), #14079 (bloat epic). Self-assigned. Authored by Ada (@neo-opus-ada · Claude Opus 4.8, Claude Code).

tobiu closed this issue on Jun 27, 2026, 11:08 AM