Comparing 49b7943420...8a03d99e31 - stack - Mosaic Gitea

mosaicstack/stack

Author	SHA1	Message	Date
fred	8a03d99e31	contract(custody-schema): revision 13 — withdraw wrong §4.5 repair attribution (sol r12 F20 residual) ci/woodpecker/pr/ci Pipeline was successful Details Sol's r12 confirm closed F18/F19 and found one MINOR residual on F20: rev 12 assigned the terminated ordinary writer's committed-but-unpointed content to §4.5 repair, but §4.5 enumerates pointers and repairs the opposite state (pointer present, content absent) — unpointed content is outside its input, so the §7.10 assertion had no conforming transition. Per the prescribed correction: the §4.5 repair assertion is removed from §3.7 and §7.10; the no-upsert assertion stays; the state is what §3.7 and §7.16 already define — inert unpointed content (no pointer, no read path, no repair transition; a §4.5 cycle run against it changes nothing), never acknowledged, converging only through the client's retry as a fresh lock acquisition under a new token that recommits and completes the pointer upsert. Preamble Revision 13 paragraph added.	2026-08-27 04:48:07 -05:00
fred	8085982396	contract(custody-schema): revision 12 — exact token comparison base case, split stale database-half boundary ci/woodpecker/pr/ci Pipeline was successful Details sol r11 APPROVE minors: - F19: strictly-less-than refusal made explicit; absent recorded token compares lower than every minted token, first acceptance creates the record; §7.10 virgin-locator control + delayed-first-grant race. - F18 residual closed: §7.10 managed-deletion fault predicate restated as the exact §4.7 predicate (advance's epoch mint and token record permitted). - F20: pre-advance linearization boundary distinguishes database halves — pair-conditioned step 2 for deletion/repair; terminated ordinary writer performs no pointer upsert, retry is a fresh acquisition; §7.10 control runs both branches. - §8 item 16 revision-12 clause; preamble Revision 12 paragraph.	2026-08-27 04:19:19 -05:00
fred	2c02631324	custody contract revision 11: acquisition-token guard on the fence-advance (sol r10 F16 residual, F18) ci/woodpecker/pr/ci Pipeline was successful Details The fence-advance is itself fenced against an older acquisition: a per-locator acquisition token minted by the lock authority at every lock grant, carried unchanged across the acquisition's brain operations and swap-loop retries, compared and recorded by the brain store atomically with every brain mutation (advance included). A superseded acquisition's delayed advance is refused, mints nothing, and yields no usable fence (mandatory abort-release-surface, expected on deadline supersession). The 'refused unconditionally' claim is precisified to the exact linearization boundary; the pre-step-1 interruption predicates are restated over exact content/database state, expressly permitting the advance's epoch/token change (F18). New §7.10 stale-advance refusal and pre-advance linearization controls; token invariants added to the fence static controls (§7.10, §7.16); §8 item 16 and preamble extended.	2026-08-27 03:47:21 -05:00
fred	b10cfb1e69	docs: custody-schema contract revision 10 (sol r9 F16 residual + F17: ABA-resistant per-locator fence epoch — fresh mint on every mutation incl. byte-identical and absence tombstone, fence-advance at lock acquisition invalidating stale tails before first mutation, repair advances before observing; distinct-locator no-contention narrowed to locator locks) ci/woodpecker/pr/ci Pipeline was successful Details	2026-08-27 03:04:52 -05:00
fred	c6a2237dde	docs: custody-schema contract revision 9 (sol r8 F15 residual + F16: independent deadline supervisor, brain fence via conditional application, reservation-at-skip, computed fixed cycle maximum with explicit exceedance carry-over) ci/woodpecker/pr/ci Pipeline was successful Details	2026-08-27 02:22:17 -05:00
fred	f8ac64f58a	docs: custody-schema contract revision 8 (sol r7 residual F15: declared hold deadline + arrival-order grants make the one-cycle bound wall-clock provable) ci/woodpecker/pr/ci Pipeline was successful Details	2026-08-26 23:08:12 -05:00
fred	482400d93c	docs: custody-schema contract revision 7 (sol r6 F15: within-cycle blocking retry preserves the one-cycle orphan bound under lock contention) ci/woodpecker/pr/ci Pipeline failed Details	2026-08-26 22:38:20 -05:00
fred	8ca4564b5e	docs: custody-schema contract revision 6 (sol r5 residuals F9/F12 + F14) ci/woodpecker/pr/ci Pipeline was successful Details	2026-08-26 22:06:00 -05:00
fred	a8111998c7	docs: custody-schema contract revision 5 (sol r4 residuals F9/F11 + F12/F13) ci/woodpecker/pr/ci Pipeline failed Details	2026-08-26 21:25:53 -05:00
fred	269aeda193	docs: custody-schema contract revision 4 (sol r3 residuals F1/F2/F4/F6/F7/F9 + F10/F11) ci/woodpecker/pr/ci Pipeline failed Details	2026-08-26 21:02:12 -05:00
fred	671b872ec9	docs: custody-schema contract revision 3 (sol re-review residuals F1-F9) ci/woodpecker/pr/ci Pipeline was successful Details	2026-08-26 20:33:21 -05:00
fred	8079d8dc91	docs(custody): revision 2 — classifier registry, grantee model, exact schemas, witness closure (sol r1 F1-F6) ci/woodpecker/pr/ci Pipeline is running Details	2026-08-26 19:39:04 -05:00
fred	caa5b04096	docs: custody pointer and consent schema contract (S2 contract 7) ci/woodpecker/pr/ci Pipeline is running Details	2026-08-26 19:10:12 -05:00

1 changed files with 1742 additions and 0 deletions

docs/requirements/custody-schema.md

+1742

View File

File diff suppressed because it is too large Load Diff