Document on Registry::open that a Registry owns two directory-co-located stores (runs.jsonl + families.jsonl) #82
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Source: fieldtest milestone "The World, part II" — finding F8 (spec_gap, ratify).
See
docs/specs/fieldtest-milestone-the-world-orchestration-families.md.The behaviour is a reasonable design; the silence in the docs is the gap.
Registry::append_familywrites topath.with_file_name("families.jsonl")— afixed filename in the runs path's directory. Two
Registry::opencalls withdifferent runs filenames in the same directory therefore share one family
store. A fixture that isolated runs by a per-process filename
(
mw1-runs-<pid>.jsonl) got a shared/tmp/families.jsonland recovered 2families instead of 1; it had to switch to a per-process temp directory.
The sibling-path is documented on
append_family, butRegistry::open's ownrustdoc ("Bind to a JSONL path") does not mention that a second, directory-keyed
store rides along.
Action (ratify): note on
Registry::openrustdoc (and/or the C18 ledgerentry) that a
Registryowns two directory-co-located stores(
runs.jsonl+families.jsonl), so isolation is per-directory.