Record sibling write-atomicity decisions for Cut 5
Soul found the TS and Python caches writing stores before validating, TS open to async interleaving, Python accepting globals under any key, and Rust's load_soa clearing before it could fail. Operator chose A throughout: a per-cache TS queue for mutations, globals only under __global__, delete Rust's uncalled load_envelope and make load_soa atomic, and leave error wording alone. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
parent
bd2ebfe7d2
commit
4fba9f6c35
1 changed files with 1 additions and 1 deletions
|
|
@ -1271,7 +1271,7 @@ the behavior change.
|
|||
become single calls; `_all_specific_stores` (`:304-311`) deleted;
|
||||
`pull_all_backing_stores` (`:111`) iterates the distinct stores. Tests:
|
||||
`test_second_generic_store_rejected`, `test_type_claimed_twice_rejected`,
|
||||
`test_types_route_to_home_store`. Command: `python -m unittest discover -s tests` in `packages\cultcache-py` with `PYTHONPATH=src` (pytest is not installed; the suite is unittest). Soul, Cut 5: the siblings did not enforce C#'s "a record's home cannot change after admission" or refuse a record loaded from a store that is not its home, and TS and Rust rejected zero-store writes the contract treats as in-memory; all three are brought to the C# reference in a follow-up commit on the same branch, and Python's `add_backing_store(store, [])` becomes a generic store.
|
||||
`test_types_route_to_home_store`. Command: `python -m unittest discover -s tests` in `packages\cultcache-py` with `PYTHONPATH=src` (pytest is not installed; the suite is unittest). Soul, Cut 5: the siblings did not enforce C#'s "a record's home cannot change after admission" or refuse a record loaded from a store that is not its home, and TS and Rust rejected zero-store writes the contract treats as in-memory; all three are brought to the C# reference in a follow-up commit on the same branch, and Python's `add_backing_store(store, [])` becomes a generic store. A later Soul pass over the sibling series found TS and Python write paths touching the store before validation and accessors ran, TS open to async interleaving, Python accepting a global under any key, and Rust `load_soa` non-atomic. Operator decisions (2026-09-14, all option A): a TS cache serializes attach, pull, writes and registrations through one per-cache queue (its own mutations only, not observer delivery); TS and Python store a global only under `__global__`; Rust deletes the uncalled `load_envelope` and makes `load_soa` atomic with the home check; cross-runtime error wording stays as is. Every sibling write validates everything before touching a store, and a refused write changes neither store nor cache.
|
||||
Version `0.2.0` -> `0.3.0`.
|
||||
- Soul: the nine tests; `rg -n "mirror" packages\cultcache-ts\src packages\cultcache-rs\src packages\cultcache-py\src`
|
||||
empty; `npm test` green including the routed-file reads.
|
||||
|
|
|
|||
Loading…
Reference in a new issue