docs: start original P13-03 and preserve spec hash repair evidence

2026-10-13 03:33:42 +09:00
parent e1a1651e15
commit 1f6c46d9f5
11 changed files with 86 additions and 8 deletions
@@ -0,0 +1,14 @@
+# P13-03 executor input: unchanged specification SHA conventions
+
+This is root-supplied execution context, not worker implementation, accepted output, a policy change, or an extra repair allowance. Read before treating the spec hash as changed.
+
+Runner runner/core.py git(repo, ...) returns subprocess stdout.strip(); registration hashes git show text after that strip. For the identical P13-03.json bytes in production and the managed checkout:
+
+- raw file SHA256: 917cf1504bbfc700e0da42b2db496b42486fe3c36c680f301f58cf34c95267b6
+- Runner text SHA256 (UTF-8 decode, strip, encode): e1255835c1227e02bac42eb99b026b0fcbe69c272f9ed0b36199a2daf8d55c53
+
+The second matches the unchanged contract spec_sha256. All six source_pins matched the initial worker read. Nothing in spec, original rules, input files or contract has changed. Record raw and Runner hashes as different named fields; do not compare raw file SHA against Runner text SHA.
+
+The frozen input/work_packages.json is the plan snapshot at contract base e1a1651e15bbc9a0526ef31d0b2786feb20d8cd1. Plan status naturally changes during a delivery, so preserve/verify that input against its actual base Git blob with its raw SHA, and separately record current source applicability. Do not pretend a baseline pin is a current-live plan hash. Actual original/asset/source files must still match their recorded applicability; stale source and false content completion are rejected.
+
+Implement only the existing immutable P13-03 spec and allowed paths. This context adds no game policy or number. Required checker and negative cases, actual difference ledger, independent formal review and integration remain. No engine, full regression, new assets or original atom completion edits. Do not treat this context as the deliverable ledger.