Skip to content

docs: preserve original memory records and add successor decision - #800

Draft
seathatflowsinourveins wants to merge 16 commits into
mainfrom
codex/ns2604-aimem-record-20261006
Draft

seathatflowsinourveins wants to merge 16 commits into
mainfrom
codex/ns2604-aimem-record-20261006

Conversation

@seathatflowsinourveins

@seathatflowsinourveins seathatflowsinourveins commented Oct 6, 2026 •

Copy link
Copy Markdown
Owner

Scope

Record the accepted ai-memory2.5.2/Nemotron8B integration and the later upstream KEEP ruling. Preserve the complete original historical decision and artifact blobs; put the later KEEP ruling and long-prompt failure/consolidation rerun in a new linked October7 successor record, and provide the portable explicit-scope example while keeping each host's capture marker untracked.

  • Base commit: 0d5e6506434fab598dee861c749a22e628beb75a.
  • Lane: lane:foundation; remains draft for the command center's cross-family read.
  • Owned paths: original October6 acceptance record and immutable sanitized receipt directory, new October7 successor decision/correction log, and supported examples/recipe. Pre-existing September decisions, maintenance guide and harness log are unchanged from the base; the October6/October7 decision prefixes remain unchanged with dated provenance/retirement amendments appended. Evidence registry is the final commit. docs: migrate indexed Qdrant stores to the native user service #783 is unchanged.

Landing path

The co-op performs the cross-family read of head af0fbfd32fd427567106780961c46be831a8f897, and the command center ACKs that head. The command center then assigns it to 5f's remaining foundation queue after the named critical-path order in CC item002346Z; it is not claimed queued or ACKed here. Only the landing cue permits the single rebase, with registry integration under the hot-file protocol, followed by 5f's landing. No lane merge or repeated DIRTY-triggered refresh.

SOTA sources

Evidence-class table

Claim Evidence class Command / receipt
Native embedder acceptance:331/331 re-embedded,335/335 current identity,29 usable known-answer targets native_proven Unchanged sanitized executor receipt, SHA256 8624a287a3df356e4ddabfdd0975ad4b93ca85d83ad57e9bbd36edc6df64339b; local29-target comparison is not upstream acceptance or a product-selection vote
Prefix/marker/consolidation/bound claims source_review Exact released source at7580b74d; upstream model preprocessing pin
Long prompt retained in observations but truncated in deterministic page; consolidation rerun passed local_integration, synthetic Private failed receipt beba568b..., private one-rerun receipt 772f222f0107cffcc48b3b328b527bcfb4a65101d027d11006c2dc87959d32ed:191characters/factoffset77; one completed source job before2native queries/1page read; recall/controltrue, strictfalse remains nongate
Model/cache retirement after CC ruling native_proven (recorded CC execution) CC manifest dated23:52:52Z, SHA256 0070add553649e97bd6a59b27ac00592773398ffaaa3559f48fe40dc75cad7e7; three model files, not a DB-row purge or backup deletion
Portable marker and docs integrity structural_validation Bounded documentation/citation tests and repository validator; root marker remains untracked, deployment placement belongs to operator

Local commands run

All host-heavy commands ran at nice19/idle I/O. No test is described as upstream acceptance.

python3 -m unittest tests.test_upstream_surface_watch.DispositionCitationTests tests.test_adoption_docs_consistency
exit0:45 tests, one skipped
python3 scripts/validate.py
exit0:69 components,10341 hashed files,4profiles,214receipts
git diff --check
exit0

Private canary facts, conversations, native transcripts, vectors, configurations and backups are not published. The only execution artifact added to this PR is the sanitized executor receipt. New native B3 smokes and the context-cap pair remain private records and are not fabricated organic counters.

Decision record

docs/decisions/2026-10-07-memory-keep-and-consolidated-recall.md is the new successor, linking the unchanged September decisions, original October6 acceptance decision and receipt. No historical decision or artifact is amended in place. The maintained re-drive trigger is the next clean Hindsight release after0.10.2 or new externally inspectable coding-agent/source-record-recovery evidence. Upstream evidence decides replacement; D3r4's stopped long campaign gates nothing.

Host evidence

No files under evidence/hosts are changed. CI's inherited sharp advisory is owned by #797; this PR changes no lock, exception, dependency or workflow. The command center/5f refreshes inherited main fixes at landing. The original September27 citation location is unchanged; remote CI remains a separate gate.

Checklist

  • One lane label, draft review and registry-last commit.
  • No credentials, raw conversations, vectors, active client configuration or new required secret published.
  • Complete original historical blobs and receipt values preserved; supersession and new observations use a separate linked record.
  • No upstream rebuild, memory-product install, hooks/client wiring or merge.
  • No new hosting/subscription surface; existing approved gateway route is recorded, not a client/provider change in this PR.
  • Peer-owned files and worktrees preserved.

J800 review fixes and CI boundary

P2a/P2b/P2c and nonblockingP3 are addressed in dated amendments: replacement comparison outcome distinct from Hindsight's re-drive trigger; all three CC-reported deletion manifests/digests and tier-1 rollback retired; intended model-card/plan revision distinct from unverified served weights; CC switch versus executing memory-h2h follow-up reports/hashes and inspection scope explicit. Release date/currentness remain unverified here with the older manifest and primary-source URL pending CC model-currency workflowwf_5053494c-265. No receipt/observation byte changed, new local campaign or model switch. Portable service/marker scope examples now both default/native-agent-stack.

Local checks at af0fbfd32fd427567106780961c46be831a8f897:45scoped documentation/citation tests passed(one skipped); validate.py passed69components/10341hashfiles/4profiles/214receipts; diffcheck passed. Both original decision prefixes and publicreceipt8624remain intact. Independent critic found no material documentation correction. Registry commit is last.

CI at the reviewed head af0fbfd32fd427567106780961c46be831a8f897: validate NOT RUN, as reported by the co-op's delta verdict (DIRTY against main). CI at the scope-fix head 8980fd5932f2f88ea44906a11c947832427f2147: UNKNOWN/not yet observed here. Local checks are structural_validation, not hosted CI acceptance or a CC ACK. The co-op reads the delta and hosted CI before CC ACK; 5f owns the queued branch and landing. No rebase just for DIRTY.

Dated consolidation limit — later CC ruling

From2026-10-07T01:47Z, CC review015759Z reports degraded ai-memory consolidation/auto-improve steady state through the correct cx/gpt-6.1-sol-max alias: roughly one in four to one in three calls succeeds pending the owner's free-connection pool decision. This is a dated NON-GATING operational limit, not this lane's new count. Model/alias/config remain unchanged. The23:47C2Xpass stands as a single successful run; no second smoke or canceled gateway count. The updated tracked record links the CC review/dispatch and qualified allowlisted-row observations; source-review data is not current independent health acceptance.

The earlier J783b/J800 review fix push was followed only to incorporate this subsequently discovered CC delivery. Both new exact heads pass the required local validator on their unchanged committed trees; hosted CI remains separately UNKNOWN here/mergeability handling stays co-op/5f. No rebase, history rewind, new PR or host change.

P3 scope correction at 8980fd5

The co-op's GPT delta review at af0fbfd32 accepted the four prior findings and identified one additional edit outside that fix scope. This push restores only the portable ai-memory serve example's --workspace local and its README registry binding. Read-only computation of the committed blob and registry confirms SHA-256 4fb68a7e452eb6b8050041789fb904d4bc1b383d88392202886ca9aa08d96615, 132,219 bytes. The content commit is followed by the registry-only last commit. No decision, receipt, recorded observation or other current carrier changes in this delta.

The landed-main exception does not apply: seathatflowsinourveins/native-agent-stack@e712bae606e8d27f010af8e3c13ded6b7a7c207a:recipes/README.md:375 retains --workspace local, and examples/ai-memory-project.toml.example:2 declares local. Main was checked by an independent read, including its cached GitHub commit identity; no main fetch/rebase or host selector change was performed. The source for the original native service interface remains akitaonrails/ai-memory@v2.5.2 at 7580b74d0fb9d14a6d949dc92f5ea8bb7feb3c83, as cited above. This is a portable-example scope restoration, not a change to the CC-selected installed workspace.

Validation: python3 -B -m unittest discover -s tests -p test_adoption_docs_consistency.py passed 39 tests (one skipped); python3 -B -m unittest discover -s tests -p test_evidence_manifest.py passed five tests. python3 -B scripts/validate.py passed before commit and again at exact head 8980fd5932f2f88ea44906a11c947832427f2147: 69 components, 10,341 hashed files, four profiles and 214 receipts. Commands used nice 19, idle I/O, and a durable TMPDIR. These are structural validation and local contract tests; no integration smoke, upstream test, current hosted CI or host migration is claimed.

Landing path remains: co-op short P3 delta read → command-center ACK after required hosted validation → 5f's assigned position in its remaining queue and sole-writer landing turn. One scope-fix push on the existing base; no rebase for DIRTY, new PR, model/alias/configuration change or second C2X smoke.

@seathatflowsinourveins seathatflowsinourveins added the lane:foundation Foundation lane: Claude/Codex setup, hosts, memory, RAG, research, workers label Oct 6, 2026
@seathatflowsinourveins seathatflowsinourveins changed the title docs: record accepted ai-memory Nemotron embedder docs: preserve memory decisions and record consolidated recall Oct 7, 2026
@seathatflowsinourveins seathatflowsinourveins changed the title docs: preserve memory decisions and record consolidated recall docs: preserve original memory records and add successor decision Oct 7, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lane:foundation Foundation lane: Claude/Codex setup, hosts, memory, RAG, research, workers

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant