Skip to content

groove: adopt the Ranked-Ownership Cleave spec (B2 cleave) — standard… - #552

Merged
hyperpolymath merged 2 commits into
mainfrom
groove/ranked-ownership-cleave-spec
Jul 28, 2026
Merged

groove: adopt the Ranked-Ownership Cleave spec (B2 cleave) — standard…#552
hyperpolymath merged 2 commits into
mainfrom
groove/ranked-ownership-cleave-spec

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

…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.

Summary

Closes #

Type of change

  • 🐛 Bug fix (non-breaking change that fixes an issue)
  • ✨ New feature (non-breaking change that adds functionality)
  • 💥 Breaking change (would change existing behaviour)
  • 🕳️ Soundness fix (fixes a checker/proof false-negative)
  • 📖 Documentation
  • 🧹 Refactor / tech debt (behaviour-preserving)
  • ⚡ Performance
  • 🔧 Build / CI / tooling

How has this been verified?

Checklist

  • My commits are signed (git commit -S).
  • I ran the project's own checks/tests locally and they pass.
  • New files carry the correct SPDX-License-Identifier (code/config MPL-2.0,
    prose CC-BY-SA-4.0); I did not relicense existing files.
  • Docs are updated, and no public claim now overstates what the code does.
  • I have not introduced a soundness hole (or I have flagged where I might have).

Notes for reviewers

hyperpolymath and others added 2 commits July 11, 2026 09:34
…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>
@hyperpolymath
hyperpolymath merged commit 7497943 into main Jul 28, 2026
1 check passed
@hyperpolymath
hyperpolymath deleted the groove/ranked-ownership-cleave-spec branch July 28, 2026 07:09
@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant