groove: adopt the Ranked-Ownership Cleave spec (B2 cleave) — closes #386#481
Merged
Conversation
…s#386 Canonical normative spec for groove teardown: the discipline by which a groove connection closes cleanly and provably leaves zero residue (⊥). Covers the B2 (live-governance / lifecycle-residue) layer only. - groove-protocol/spec/GROOVE-RANKED-OWNERSHIP-CLEAVE-SPEC.adoc — v0.2.0-draft.1: two well-founded measures (occupancy = renewable lease; discharge = residue→⊥), cycle-freedom from well-foundedness of `owns`, edge classification (owns=linear / borrow=affine / observe|peer=unrestricted), partial-order fidelity (children-before-parent; Dershowitz–Manna multiset), ordinals only static-at-connect (ε₀+ forbidden), joint completion + survivor-owns-the-wipe rupture policy, and 13 normative invariants RC-1…RC-13 each with a falsifier. - groove-protocol/README.adoc — cleave-surface layering (A/B1/B2/C1/C2) + index. - Pointer from the superseded groove-browser-harness template. Provenance corrections folded in (verified against the gossamer tree): host proof is ResourceCleanup.idr (not GrooveTermination.idr); `owns` is linear not affine; the graph invariants are VACUOUSLY satisfied today (flat groove array, no owns graph) — a green checker is not yet a real guarantee. Addresses gossamer#82 item 6. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adopts the canonical Groove Ranked-Ownership Cleave spec — the discipline by which a groove connection closes cleanly and provably leaves zero residue (
⊥). Closes the gap #386 identified (standards had no canonical groove teardown spec, only the T2-high harness template).groove-protocol/spec/GROOVE-RANKED-OWNERSHIP-CLEAVE-SPEC.adoc— v0.2.0-draft.1, Internet-Draft style, covering the B2 (live-governance / lifecycle-residue) layer only.groove-protocol/README.adoc— the cleave-surface layering (A / B1 / B2 / C1 / C2) + spec index.groove-browser-harness.md.The spec (per #386's outline)
⊥= zero residue).ownsrelation itself → ownership cycles unrepresentable → underwrites no-GC/no-refcount.owns=linearlet!/borrow=affinelet/observe|peer=unrestricted; onlyownsenters the residue proof.ε₀+ forbidden), joint completion + survivor-owns-the-wipe rupture policy.RC-1…RC-13, each with a falsifier — drops into theRC-N/falsifier respec idiom for a contractile/k9 checker.Provenance corrections folded in (verified against the gossamer tree)
ResourceCleanup.idr(notGrooveTermination.idr— that's connect-side bounded-length).ownsis linear, not affine.RC-1/RC-9/RC-12) are vacuously satisfied today (flat groove array, noownsgraph) — the caveat is retained in §10 so a green checker isn't mistaken for a real guarantee.Addresses
hyperpolymath/gossamer#82item 6 (B-layer normative doc). Closes #386.🤖 Generated with Claude Code