Repository navigation
[context-loading] Stop overclaiming determinism + hook-force scope-touch detection #73
Description
Activity
- added a commit that references this issue
on Jun 21, 2026 Resolved in full.
Scope-touch half — shipped in
ca 2.5.0(#116): CI (H-15), deploy/IaC (H-16), and auth (H-17) touches are now detected mechanically bypost-write-edit.py, andcommit-gatedispatchessecurity-revieweron a staged CI/deploy touch even on bare/commit. Advisory, not blocking — a workflow runs only once merged and IaC bites only on apply, so the hard commit-blocks stay reserved for the irreversible-once-committed harms (secret/migration/crypto).Overclaim half — already resolved before this work: the
ORCHESTRATOR.mddeterminism overclaim was removed by the #103 kernel trim, andlazy-load-bundles.mdinvariant #1 already correctly scopes determinism to the bundle leaf-load map (redirect inference and lane triage are inherently judgment and no longer claimed otherwise).
Source: context-loading review (upheld under challenge, both halves).
Problem: Docs claim the load model is "deterministic and reproducible," but only the
anti-slop-designbundle's leaf-selection actually is. Three decisions rely on the model judging: redirect inference (redirect.md:4-5), small-vs-full-lane triage (feature.md), and scope-touch detection (ORCHESTRATOR.md:140-144— the reference-map read only happens if the model notices the touch).lazy-load-bundles.md:36explicitly forbids "load if you judge X" selection — but enforces it only inside the bundle, not at the orchestrator tier.Do:
hooks/pre-edit.py/hooks/pre-write.py— a crypto/secret/migration edit emits a breadcrumb that mechanically forces the governing read, moving detection off the model onto the hook layer. This is enforcement-not-trust applied to the loading model itself.Related: the
/add-depand migration enforcement issues are the same root cause (soft scope-touch firing).