Propose a change. Cite your reasoning.
Blueprints in this series are versioned specifications, not fixed text. Anyone — a ministry architect, an implementer, a standards body — can push a Request for Comment against a specific layer. Reviewed proposals inform the next version.
How this works
Every RFC targets one publication layer (PL-01 through PL-06). The Lab’s editorial team reviews each submission for fit against the layer’s design principles before it moves from New submission to Under review.
Your name/handle and proposal are published in the feed once approved, if you opt in below. Your email is never published — it is used only so the editorial team can follow up directly.
Strong RFCs cite the specific interface, principle, or clause they change (e.g. “SEC-PRIV” or “P-2”), and explain the impact on implementers already building to the current version.
Push an RFC
Fields marked with the layer selector help route your proposal to the right editor.
Community contributions
2 proposalsAdd USSD/SMS fallback conformance tests to PL-01 ASSERT
Open discussionPL-01 requires low-tech channel support in principle, but the ASSERT interface spec has no conformance test for USSD-based assertion. Proposing a test vector set so implementations can actually be certified against it, not just described as compliant.
Clarify PPID rotation policy across agency boundaries
Under reviewThe SEC-PRIV section mandates Pairwise Pseudonymous Identifiers but doesn't specify a rotation cadence or what happens to historical PPIDs when an agency is dissolved or merged. Proposing a minimum rotation policy and a succession rule for agency PPID namespaces.