Repository navigation
docs: ai-memory allowlist capture was not in force on this host (correction #144) - #988
Merged
seathatflowsinourveins merged 3 commits intoOct 11, 2026
Merged
Conversation
seathatflowsinourveins
added a commit
that referenced
this pull request
Oct 10, 2026
…e working check The GPT read of #988 found two P2s. The prescribed `ai-memory hook --check-capture` cannot run without --event, --agent and --server-url; the doc now gives the documented form (recipes/README.md:418) and what to expect for enrolled and excluded directories, plus the inverse. And "lane worktrees carry none and are not captured" was not exact: a worktree below the enrolled checkout, or one that receives the marker through .worktreeinclude, is enrolled by design (recipes/README.md, "Worktrees and the capture marker"). The paragraph now states that design, that read snapshots and blind lanes must never carry or inherit the marker (the read kit aborts on any ancestor marker), and the measured state: 2 of 404 worktrees carry a marker, none nested under the main checkout. Co-Authored-By: Claude Opus 5.5 <[email protected]>
…s host (correction #144) On the current host (ai-memory 2.6.0) the capture-mode file the installer writes under --apply was absent, so lifecycle capture ran in the default denylist mode and captured every directory, including scratch and test worktrees and GPT read snapshots. The maintenance doc said the allowlist installers had been applied. It now records the measurement, the vendor source lines, and the repair under this stack's untracked per-checkout marker convention (.gitignore:73): the main checkout carries the marker, the trading repository carries none, read snapshots strip copied markers, and install-hooks re-applies allowlist mode; plus how to verify it. Co-Authored-By: Claude Opus 5.5 <[email protected]>
…e working check The GPT read of #988 found two P2s. The prescribed `ai-memory hook --check-capture` cannot run without --event, --agent and --server-url; the doc now gives the documented form (recipes/README.md:418) and what to expect for enrolled and excluded directories, plus the inverse. And "lane worktrees carry none and are not captured" was not exact: a worktree below the enrolled checkout, or one that receives the marker through .worktreeinclude, is enrolled by design (recipes/README.md, "Worktrees and the capture marker"). The paragraph now states that design, that read snapshots and blind lanes must never carry or inherit the marker (the read kit aborts on any ancestor marker), and the measured state: 2 of 404 worktrees carry a marker, none nested under the main checkout. Co-Authored-By: Claude Opus 5.5 <[email protected]>
…read's P3 citations The GPT micro of 77e95b7 (P2) found no regression for the two corrected statements, so the correction rule (AGENTS.md, Corrections) was not met. Two doc-contract tests fail on the first version's text (8690d10: 2 failures) and pass at this head: - the documented check carries hook --event --agent --server-url --check-capture --data-dir (HookArgs, ai-memory v2.6.0 cli.rs:2957-2966; the bare form exits 2); - enrollment follows recipes/README.md "Worktrees and the capture marker" (marker walk to $HOME, marker.rs:938-1025; .worktreeinclude), without the false "lane worktrees carry none". The independent Claude read's P3s: the per-event read is hook.rs:720-726 and the v2.6.3 reader sits unchanged at :1383-1399; the read kit strips markers, then aborts on a remaining or ancestor marker; the trading-research bank is cited (foundation-finalization :70,157) instead of the unsourced "exposure tags"; the check lines are recipes/README.md:419-421. Co-Authored-By: Claude Opus 5.5 <[email protected]>
seathatflowsinourveins
force-pushed
the
cc/ai-memory-allowlist-marker-20261010
branch
from
October 11, 2026 01:38
77e95b7 to
862ae2d
Compare
seathatflowsinourveins
deleted the
cc/ai-memory-allowlist-marker-20261010
branch
October 11, 2026 02:27
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.
Summary
docs/memory-landscape-maintenance.md: a dated correction (CC correction Make verdict-review-gate apply the landscape validator's withheld-key policy #144). On this host at the time of the finding (ai-memory 2.6.0; the host runs 2.6.3 since 2026-10-10T22:09Z, where the same mechanism holds),<data_dir>/capture-modewas absent, so lifecycle capture ran in the default denylist mode and captured every directory, including scratch and test worktrees and GPT read snapshots. The doc had recorded allowlist capture as applied..gitignore:73): the main checkout carries.ai-memory.toml(the one adopted project); worktrees below the enrolled checkout, or ones that receive the marker through.worktreeinclude, are enrolled by design; read snapshots and blind lanes must never carry or inherit the marker; measured: 2 of 404 worktrees carry one, none nested under the main checkout. the trading repository has none, because its research memory goes to Hindsight'strading-researchbank with exposure tags. The CC re-applies allowlist mode with the vendor installer and verifies it with--check-captureandai-memory status.manifests/evidence.json: the doc is re-registered per the hot-file protocol.SOTA sources
docs/marker-file.md(marker lookup and allowlist opt-in),install_hooks.rs:703-710, 1055-1069(the mode file is written only under--apply),hook.rs:1340-1356(the mode is read per event; denylist when the file is absent),docs/install.md:599-609(--check-capture).Tests
python3 scripts/validate.py: rc 0. The change is documentation plus its registration; no code changes.🤖 Generated with Claude Code