A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live
I0841
Cache equivalence proved by property-shaped cases
Where it stands
devtask.issueMoves
plan.transitionWhat it is
- Objective
- For every read-only command in the registry, run it with the cache cold, warm, and disabled, on this repository and on a synthetic one, and assert byte-identical output and exit code; then mutate one file and assert the changed output is served.
- Why
- A cache that changes a result is worse than no cache; the proof has to cover every reader, not the one that was tested.
- Now
- No cache exists yet.
- Wanted
- One case iterating the registry's read-only commands, so a command added later is covered by existing.
- Done when
- unknown: the record declares no `completion`
- Risk
- Commands whose output carries a timestamp (context) are compared after the timestamp line is dropped, and the case says which line.
Acceptance
- The case reads the registry for the command list and fails if it is empty
- Every read-only command is byte-identical across modes
- A mutated file changes the output and the counters show a miss
- Validation
bash test/run.sh 86_cache_equivalence- Evidence required
flatten_cache- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
test/casesshare/commands.yaml- Not
- none
- Depends on
- Priority
- p0
- Profile
- implementation
- Parallel safe
- false
- Owner
- unknown: the record declares no `owner`
The work so far
- Branches
- none
- Merged
- none
- Commits
0- Trunk
- master
- Sessions
- none
- Created
- 2026-09-05
- Updated
- 2026-09-05
- Started
- unknown: the record declares no `started_at`
- Verified
- unknown: the record declares no `verified_at`
- Completed
- unknown: the record declares no `completed_at`
Synchronisation
- Adapter
scripts/github-sync- Repository
- unknown: the derived plan's header carries no repository
- External issue
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
- State there
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
Findings
Nothing is wrong with these records.