| Filename | Latest commit message | Latest commit date |
|---|---|---|
A subject's resolutions and a repo's assignments on a mind each carried one key, so the second record of either overwrote the first and a withdrawn resolution could not be kept under its subject. Both keys now end in a writer-set `sequence: u32`, `n<N>`, last so the history of a subject or a repo is one key prefix and R2 keeps that prefix exact: `question.Q1.n` cannot match `question.Q10.n1`, and a withdrawal keys one nesting out under the resolution it withdraws. `assigned_on` stops being a key input and stays a field, validated where every field is, so the same assignment recorded on two days is one document and a repo transferred away and back on one day does not collide. A hand-off is unchanged in shape and key: a transfer back is the same document with the instances swapped, and no field names a return. Nesting arithmetic moves with the shape: each nesting prepends `resolution.` and appends `.n<s>`, so a chain composes `14 * (d - 1) + L` bytes against `LOCAL_MAX`, and both fixtures key four deep. The leaf refuses no sequence value -- not `0`, not a gap -- as it refuses no `revision` value; which sequence a document may claim and which record is in force are admission's, and are not in this crate. `pipeline_id` gains no arm and no key is parsed back. Two schema files regenerate from the derivation, gaining the property, the required entry and the new doc comments. No epoch moves: no store is written at this epoch and no reader is pinned to the file. Cut 6b's M2 is re-anchored on the new parts line, as N7 and N8 re-anchored Cut 6's M12 and M13. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> |
||
| .. | ||
| src | ||
| Cargo.toml | ||