Repository navigation
docs: preserve original memory records and add successor decision - #800
Draft
seathatflowsinourveins wants to merge 16 commits into
Draft
seathatflowsinourveins wants to merge 16 commits into
seathatflowsinourveins wants to merge 16 commits into
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.
0d5e6506434fab598dee861c749a22e628beb75a.lane:foundation; remains draft for the command center's cross-family read.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
7580b74d0fb9d14a6d949dc92f5ea8bb7feb3c83: prefix configuration, factory, embedding prefix application.d1f2f25730bbd775b99b29185134bc86653bf2d1: released query/passage preprocessing and4096D identity. vLLM0.31.0 is the accepted native serving source.5fc4ce20917b916240cef27c212c387a177f115b, is the named challenger; published methodology is upstream evidence, not a local comparison with ai-memory.Evidence-class table
8624a287a3df356e4ddabfdd0975ad4b93ca85d83ad57e9bbd36edc6df64339b; local29-target comparison is not upstream acceptance or a product-selection votebeba568b..., private one-rerun receipt772f222f0107cffcc48b3b328b527bcfb4a65101d027d11006c2dc87959d32ed:191characters/factoffset77; one completed source job before2native queries/1page read; recall/controltrue, strictfalse remains nongate0070add553649e97bd6a59b27ac00592773398ffaaa3559f48fe40dc75cad7e7; three model files, not a DB-row purge or backup deletionLocal commands run
All host-heavy commands ran at nice19/idle I/O. No test is described as upstream acceptance.
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.mdis 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
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 head8980fd5932f2f88ea44906a11c947832427f2147: 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-maxalias: 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
af0fbfd32accepted the four prior findings and identified one additional edit outside that fix scope. This push restores only the portableai-memory serveexample's--workspace localand its README registry binding. Read-only computation of the committed blob and registry confirms SHA-2564fb68a7e452eb6b8050041789fb904d4bc1b383d88392202886ca9aa08d96615, 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:375retains--workspace local, andexamples/ai-memory-project.toml.example:2declareslocal. 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 remainsakitaonrails/ai-memory@v2.5.2at7580b74d0fb9d14a6d949dc92f5ea8bb7feb3c83, 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.pypassed 39 tests (one skipped);python3 -B -m unittest discover -s tests -p test_evidence_manifest.pypassed five tests.python3 -B scripts/validate.pypassed before commit and again at exact head8980fd5932f2f88ea44906a11c947832427f2147: 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.