P04-01: 同時発生の更新規約

2026-10-18 11:16:06 +09:00
parent 20d0ae5990
commit 1b08d6b0fc
7 changed files with 377 additions and 34 deletions
@@ -0,0 +1,51 @@
+# REPAIR33 — blocked, no implementation or acceptance claim
+
+P04-01 remains incomplete. Only this status and REPAIR33_STATIC_CHECKS.json
+were added. Checker, fixtures, wrapper and S5 run documents remain unchanged.
+No Git writes, Runner operations, fixture execution or engine runs occurred.
+
+The instruction to return blocked for missing specifications applies to these
+unresolved input contracts:
+
+- The Root-supplied Q descriptor has no supplied schema or existing definition
+  in the inspected checker, S5 wrapper or local execution documentation.
+  `verify_roles` requires `product_binding` to contain exactly `tested_product`
+  and `runner_inputs`. Each runner input references an existing native receipt,
+  wrapper and materials; it does not define M/S fields or the wrapper's fresh-Q
+  configuration input. Specify the descriptor fields/types and how M, S, Q,
+  staged product, settings, markers, policy and material bindings are obtained
+  without inventing another input contract. Future hashes are not requested.
+- The requested combined control includes matching Runner/Root records, but
+  `normal_c_join.verify(database, approved_database, candidate, submission,
+  hashes)` accepts only Runner databases and caller-supplied commit strings.
+  Its CLI has no Root exact-candidate record input or verification. Specify
+  that record's schema and binding, or explicitly confirm that Root performs
+  this join outside this verifier and define the combined control boundary.
+  The verifier was neither weakened nor called from the checker.
+
+These are contract questions, not requests for permission expansion. Runner
+core, Owner CLI and the reference core were not read. No dependency on them
+was introduced. No speculative partial implementation was made.
+
+Actual verification: six existing Python files compiled with py_compile;
+generated bytecode was placed under the allowed execution directory and
+removed. Pure AST inspection confirmed the normal_c_join parameter list;
+a source assertion confirmed runner_inputs is present. Actual outputs are
+recorded in REPAIR33_STATIC_CHECKS.json. All twelve discovered fixture files
+are individually listed there as unexecuted; Root runs them later with its
+own scratch directory. No test or acceptance result is inferred from syntax.
+
+An initial shell here-document command failed before Python started with
+`can't create temp file for here document: operation not permitted`.
+It produced no verification result. The checks were then run using python3
+`-c`, without shell temporary-file redirection.
+
+Explicitly pending: this REPAIR33 implementation; S5 destruction, midnight
+and exit drivers; fresh-Q plumbing for S1–S4 and the collector; all 184
+executable suites and the 329 parse verifier; the truthful index; Root's
+fixed run order, independent review and normal integration/final joins.
+
+Formal 16/88, original 30/88, seven domains plus EV, all six D05 approvals
+and P04 credit 0 remain fixed. M remains
+`c0ea009b28a7649aca6a433a1a24dc0be5e7ab81`. No condition credit, original
+completion, self-reported acceptance or cap change is claimed.