Skip to content

spec: ratify RFC-001 (issue #56) - #113

Merged
trendvidia merged 2 commits into
mainfrom
rfc001-56-ratify
Jul 16, 2026
Merged

spec: ratify RFC-001 (issue #56)#113
trendvidia merged 2 commits into
mainfrom
rfc001-56-ratify

Conversation

@trendvidia

Copy link
Copy Markdown
Owner

Summary

Ratifies RFC-001 — Protowire Schema Extensions (S3 closer; #56): header status Draft → Ratified (2026-07-16), authors set, and §13 rows 13/14 now cite their freshly filed tracking issues (#111 sensitivity-class taxonomy, #112 @encrypted(key_ref)).

Acceptance criteria (#56)

Closes #56. Tracked by #55. Next and final S3 item: #57 (generate + submit IETF -01).

Status Draft → Ratified (2026-07-16). §13 rows 13/14 now cite their
tracking issues (GH #111, #112) — with those filed, every open
question is either resolved in the RFC (S1: #11#16; S2: #15
source grammar, #21 sensitivity, #35 path scheme; S3: #22
engine-expression scope, #23 no dual-emission) or tracked as a
separate issue (GH #59, #66#69, #103, #111, #112). All v1.2 surface
is strictly additive; no locked decision blocks an existing port's
roadmap (per-port adoption is M9+, gated on the conformance corpus).
@trendvidia
trendvidia merged commit bdb1cb7 into main Jul 16, 2026
4 checks passed
@trendvidia
trendvidia deleted the rfc001-56-ratify branch July 16, 2026 20:22
@trendvidia trendvidia mentioned this pull request Jul 16, 2026
3 tasks
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.

Ratify RFC-001

1 participant