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	14101
title	Data-integrity detect: store-size bloat producer (#14026 leaf 4)
state	Closed
labels	enhancementaiarchitecture
assignees	neo-opus-grace
createdAt	Jun 26, 2026, 4:11 PM
updatedAt	Jun 26, 2026, 4:34 PM
githubUrl	https://github.com/neomjs/neo/issues/14101
author	neo-opus-grace
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jun 26, 2026, 4:34 PM

Data-integrity detect: store-size bloat producer (#14026 leaf 4)

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

neo-opus-grace commented on Jun 26, 2026, 4:11 PM

Context

#14026 leaf 4 (after coverage-drift #14075, monotonicity #14094, SQLite-integrity #14096). The Memory Core Chroma store grew to ~2.5GB (#14079) — uncontrolled store-size growth (un-pruned WAL / orphaned segments / churn) is a data-integrity signal, yet there is no detect signal for it. The #14026 body lists store-size/bloat (absolute + growth-rate) as a heuristic.

The Architectural Reality

dataIntegrityCoverageDiagnosis.mjs (#14075) + sqliteIntegrityDiagnosis.mjs (#14096) are the pure-producer pattern to mirror.
Store size is measured by the daemon (e.g. fs.stat on the store) + a previous sample for growth-rate — INJECTED into the pure producer (like monotonicity's count samples).
Thresholds (absolute bytes + growth-ratio) are ADR-0019 config leaves, read at the daemon use-site and passed as params (NOT in the pure fn).

The Fix

A pure buildStoreBloatDiagnosis({storeSizeBytes, previousSizeBytes, thresholds, observedAt, serviceId}):

Emits a data-integrity / escalate diagnosis when storeSizeBytes > thresholds.absoluteBytes (absolute bloat) OR (previousSizeBytes present and the growth ratio (storeSizeBytes - previousSizeBytes) / previousSizeBytes > thresholds.growthRatio).
evidenceFacts name which signal(s) crossed (absolute / growth) + the sizes + the crossed threshold; details.reasonCode: 'data-integrity-store-bloat'.
null when within budget (no false escalation); a sub-signal whose threshold is non-finite is skipped (graceful).
Detect-only — no prune/vacuum (operator-gated remediation; #14079).

Acceptance Criteria

Emits a contract-valid data-integrity / escalate diagnosis on absolute-bloat OR growth-bloat; null when within budget.
evidenceFacts name the crossed signal(s) + sizes + threshold; details.reasonCode: 'data-integrity-store-bloat'.
Detect-only; targetIdentity.kind: 'compose-service'; thresholds are params (ADR-0019 — read at the use-site, not in the pure fn).
Unit coverage: absolute-bloat → diagnosis; growth-bloat → diagnosis; within-budget → null; missing/zero previousSizeBytes → absolute-only; non-finite storeSizeBytes → null; enum/target validate; arg-guard throws.

Contract Ledger Matrix

Target Surface	Source of Authority	Proposed Behavior	Fallback	Docs	Evidence
`buildStoreBloatDiagnosis({storeSizeBytes, previousSizeBytes, thresholds, observedAt, serviceId})`	#14075 pure-producer pattern + #14079 bloat signal	absolute OR growth bloat → `data-integrity`/`escalate` diagnosis; `null` within budget	missing/zero previous → absolute-only; non-finite size → `null`; bad `serviceId`/`observedAt` → `TypeError`	module + fn JSDoc	unit spec
recovery-diagnosis payload	`createRecoveryDiagnosisEvent` (`recoveryRunStateStore`)	`recoveryClass: 'data-integrity'` · `details.actionClass: 'escalate'` · `targetIdentity.kind: 'compose-service'` · `evidenceFacts[].type: 'store-bloat'` (+ signal/sizes/threshold) · `details.reasonCode: 'data-integrity-store-bloat'`	n/a	JSDoc	spec asserts each field

(Contract Ledger included at creation — per @neo-gpt's #14095 catch, the detect-leaf pattern carries the ledger from the start.)

Out of Scope

Scheduling + the size measurement (the #14026 wiring slice).
Pruning/vacuuming the store (operator-gated; #14079).

#14026 (parent), #14075 / #14094 / #14096 (sibling producers), #14079 (the 2.5GB bloat this detects), #14089 (the ADR-0025 §2.4 dimension), #14039.

Live latest-open sweep: checked latest open + the #14026 leaf set at 2026-06-26T14:07Z; no store-bloat leaf exists (#14079 = broader bloat roadmap). A2A: broadcast [coordination] + claim before filing.

Origin Session ID: 5ab545e1-f09e-46c5-ae62-8cf5b2b96193

Handoff Retrieval Hints: query_raw_memories("store-size bloat data-integrity detect producer absolute growth-rate"); anchors: ai/daemons/orchestrator/services/sqliteIntegrityDiagnosis.mjs (sibling), #14079.