From 8d69fbf8f03e9c5a2395a2d26c0a85756518c90d Mon Sep 17 00:00:00 2001 From: Ralf Anton Beier Date: Thu, 30 Jul 2026 19:11:55 +0200 Subject: [PATCH] chore(artifacts): tag the three ordeal artifacts human-scoped REQ-GUARD-HUMAN-SCOPED-001 landed the mechanism in #359 but tagged nothing with it. The guardrail exists because the autonomous cron picked up REQ-CODEGEN-LAYOUT-CERT-001, implemented it, self-recorded `verified` and merged it inside an hour -- asserting a proof that did not exist. Shipping the enforcement without applying it to the artifact that motivated it leaves the same hole open under a new name. All three are human-scoped by the definition in the guardrail itself (first wiring of an external dependency; narrowing a research-grade property to something a solver can actually decide; designing a falsification kill-criterion): REQ-CODEGEN-LAYOUT-CERT-001 rejected the artifact the guardrail traces-to; tagged so a revival cannot repeat the promotion REQ-CODEGEN-LAYOUT-CERT-002 rejected its successor, which explicitly says a future certificate "would have to be re-derived from scratch with a proof goal that a wrong encoder can actually falsify" REQ-PROOF-RTA-OVERFLOW-001 proposed the LIVE one -- the re-aimed ordeal beachhead, v0.36.0, and the next thing the cron would reach for `rejected` and `proposed` are both permitted statuses, so this is exit 0 today; the tag only bites on promotion to implemented/verified/released/ accepted/passing. Verified two-sidedly, because a guard that never fires is indistinguishable from a guard that cannot fire, and "exit 0" alone demonstrates neither: side 1 as committed -> exit 0, 6 tagged, 0 violations side 2 RTA-OVERFLOW-001 flipped to `verified` in a scratch copy -> exit 1, names that artifact Side 2 is the load-bearing one: it shows the tag binds on this specific id, not merely that the checker runs. Co-Authored-By: Claude Opus 4.8 (1M context) --- artifacts/requirements.yaml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/artifacts/requirements.yaml b/artifacts/requirements.yaml index f0c2b38..a2307ce 100644 --- a/artifacts/requirements.yaml +++ b/artifacts/requirements.yaml @@ -3256,7 +3256,7 @@ artifacts: produces it. The ordeal beachhead moves to REQ-PROOF-RTA-OVERFLOW-001, where bit-precise u64 wraparound is exactly such a property. status: rejected - tags: [codegen, ordeal, certificate, layout, wit, withdrawn, v0350] + tags: [codegen, ordeal, certificate, layout, wit, withdrawn, v0350, human-scoped] links: - type: traces-to target: REQ-CODEGEN-WIT-RECORDS-001 @@ -3280,7 +3280,7 @@ artifacts: goal that a wrong encoder can actually falsify, and justified against plain interval arithmetic. Not planned. status: rejected - tags: [codegen, ordeal, certificate, layout, wit, withdrawn] + tags: [codegen, ordeal, certificate, layout, wit, withdrawn, human-scoped] links: - type: traces-to target: REQ-CODEGEN-LAYOUT-CERT-001 @@ -3329,7 +3329,7 @@ artifacts: introduces a new multiplication cannot land silently. status: proposed release: v0.36.0 - tags: [proofs, ordeal, certificate, rta, overflow, v0360] + tags: [proofs, ordeal, certificate, rta, overflow, v0360, human-scoped] links: - type: traces-to target: REQ-PROOF-SCHED-CODEGEN-001