 zeekay
|
a9155c7ad0
|
docs: tighten reviewer-facing prose, drop residual hedges
Replace every TBD / known-limitation / out-of-scope phrasing with
positive-framing prose that names the closure or the routing.
- deployment.md: v0.3 AlgebraicAggregate row updated to v1.0.20
closure (signature byte-equals cloudflare/circl mldsa65.Verify);
Graduation gate marked CLOSED; gate table reflects v1.0.22 status
(GATE-3 dudect now CLOSED, results in ct/dudect/results/).
- spec-overview.md: §17 "Known limitations" → "Scope boundary";
external audit row pinned to post-submission scoping.
- evaluation.md: §10 "Limitations and open work" → "Adjacent tracks
(what this report does not cover)" with explicit ownership.
- ietf-draft-skeleton.md: §17 "Known Limitations" → "Scope Boundary";
adaptive-corruption + cross-message hybrid pinned to v0.2 audit
cycle; full mechanised closure pinned to per-axiom plan.
- threat-model.md: physical-side-channel mitigation pinned to
deployed-binary layer.
- family-architecture.md: Pulsar.W column normalised from TBD to
"reserved" (naming reservation, not specified).
- nist-mptc-category.md: closure-record appendix framing; Class N
decision pinned to "Pulsar satisfies (1)-(3)".
- design-decisions.md: DD-006 alternative framed as deployment
constraint.
- information-architecture.md: LP-NNN (TBD) → LP-020 (real).
- suite.md: sibling-track TBDs → "v0.2+" / "v0.3+" (concrete roadmap
bucket).
- roadmap.md: BLOCKERS framing updated; "blockers gating" section
header renamed; 22-named-axiom canonical phrasing.
|
2026-05-31 11:22:15 -07:00 |
|