Skip to content

spec(ws): SPEC-001 v1.5 pair_ot ownership wire shapes#111

Merged
Augustas11 merged 1 commit into
mainfrom
feat/spec-001-v1.5-pair-ot-amendment
Jun 21, 2026
Merged

spec(ws): SPEC-001 v1.5 pair_ot ownership wire shapes#111
Augustas11 merged 1 commit into
mainfrom
feat/spec-001-v1.5-pair-ot-amendment

Conversation

@Augustas11

Copy link
Copy Markdown
Owner

Summary

  • Bump SPEC-001 to v1.5 for pair_ot + claim_url ack fields
  • Add ownership_event and ownership_status server-pushed frame shapes
  • Add durable audit prompt for the SPEC-001 v1.5 amendment

Validation

  • git diff --check
  • code/spec auditor: 0 critical / 0 high / 0 medium
  • security auditor: 0 critical / 0 high / 0 medium
  • architecture auditor: 0 critical / 0 high / 0 medium

No implementation files changed.

Adds the SPEC-001 v1.5 wire contract that SPEC-014 can consume without making SPEC-014 the protocol owner. The amendment keeps emission timing in the future SPEC-003 FR-C10 policy surface and gives needs_claim a dedicated C->P ownership_status carrier instead of overloading provider heartbeats or ownership_event.

Constraint: GitHub-auth implementation branch is reserved for the five-phase feature branch; this amendment must ship from a separate branch.

Rejected: Commit from feat/spec-014-v0.2-github-auth | reserved branch must remain for later implementation phases.

Rejected: Carry needs_claim on heartbeat or ownership_event | wrong direction or ambiguous ownership semantics.

Confidence: high

Scope-risk: narrow

Directive: Keep SPEC-001 limited to wire shape; put emission policy in SPEC-003 and bind/storage behavior in SPEC-014 implementation work.

Tested: git diff --check; code/spec auditor 0 C/H/M; security auditor 0 C/H/M; architecture auditor 0 C/H/M.

Not-tested: Runtime tests not applicable for markdown-only spec amendment.
@Augustas11 Augustas11 merged commit 8839e5a into main Jun 21, 2026
5 checks passed
@Augustas11 Augustas11 deleted the feat/spec-001-v1.5-pair-ot-amendment branch June 21, 2026 16:52
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