Skip to content

spec(coord): SPEC-003 v0.10 — FR-C10 pair_ot minting policy (SPEC-014 v0.2 upstream amendment)#112

Merged
Augustas11 merged 1 commit into
mainfrom
feat/spec-003-v0.10-fr-c10
Jun 21, 2026
Merged

spec(coord): SPEC-003 v0.10 — FR-C10 pair_ot minting policy (SPEC-014 v0.2 upstream amendment)#112
Augustas11 merged 1 commit into
mainfrom
feat/spec-003-v0.10-fr-c10

Conversation

@Augustas11

Copy link
Copy Markdown
Owner

Summary

  • Bumps SPEC-003 to v0.10 and adds FR-C10 for coordinator-side pair_ot / claim_url emission policy.
  • Adds the dedicated SPEC-003 v0.10 FR-C10 audit prompt.
  • Keeps SPEC-001 as the wire-shape owner and SPEC-014 as the downstream consumer.

Validation

  • git diff --check
  • Code/spec auditor: PASS, C=0 H=0 M=0 L=0
  • Security auditor: PASS, C=0 H=0 M=0 L=0
  • Architecture auditor: PASS, C=0 H=0 M=0 L=0

Notes

This is spec-only. Runtime implementation remains for SPEC-014 v0.2 Phase 2A.

SPEC-014 v0.2 needs a SPEC-003-owned coordinator policy for when pair_ot and claim_url are emitted, while SPEC-001 owns only the wire shape.

Constraint: SPEC-014 GitHub-auth worktree remains reserved for the later five-phase implementation

Rejected: authoring wire schema in SPEC-003 | SPEC-001 v1.5 is the protocol owner

Rejected: committing from feat/spec-014-v0.2-github-auth | branch is reserved for GitHub auth implementation

Confidence: high

Scope-risk: narrow

Directive: keep FR-C10 as emission policy only; bind route behavior and portal surfaces remain downstream SPEC-014 work

Tested: git diff --check; code/spec, security, and architecture auditor rounds to 0 critical/high/medium/low

Not-tested: runtime tests not applicable to spec-only amendment
@Augustas11 Augustas11 merged commit c986bab into main Jun 21, 2026
5 checks passed
@Augustas11 Augustas11 deleted the feat/spec-003-v0.10-fr-c10 branch June 21, 2026 17:10
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