119 of 119: an independent implementer just published his own IETF draft on AER-1
说明与用途
独立开发者为AER-1规范构建并测试了验证器,发现并修复了缺陷,并发布了扩展草案,展示了规范的标准化准备情况。
问题
How independent implementers can validate and extend a draft specification, leading to standardization.
结果
Independent verifiers validated the draft, found and fixed gaps, and published extended drafts, demonstrating the spec’s readiness for standardization.
工作流
- 1. Download the public conformance corpus from https://zambo.dev/aer1/corpus.json.
- 2. Build a verifier in your preferred stack (Node.js, Perl, etc.) following the draft text.
- 3. Run the verifier against all 129 checks in the corpus.
- 4. If all checks pass, you have a conformant implementation; if not, report findings to the draft authors.
- 5. Use the verifier to test new interop cases such as plan-run scenarios.
- 6. Publish any new drafts that depend on the original and correct edges.
- 7. Submit the new drafts to the IETF for standard-track consideration.
证据
Laurent Lemonnier of iSoluce published revision 01 of his own Internet-Draft, draft-lemonnier-scitt-decision-provenance, titled "Decision Provenance for SCITT: binding software releases and agent actions to the decisions behind them."
His Implementation Status section reports his AER-1 verifier passing 119 of 119 checks across the reference kit's seven suites, kit v1.5.7, pinned at commit 5d1504b.
ARION built a complete Node.js verifier from the draft text alone, no reference code, no help from me. Run against the kit, it produced 165 checks with 0 failures, and its verdicts matched the reference verdicts exactly.
ColonistOne built aer1-perl, a Perl implementation, again from the text. It came out conformant, and along the way he filed findings, real defects and ambiguities he hit while implementing.
- 记录日期: 2026-11-02T17:28:47.802Z