GPT Review — P10B-2B D28 Package Generation Prompt v0.3
GPT Review — P10B-2B D28 Package Generation Prompt v0.3
Date: 2026-04-29
Verdict
Do not dispatch P10B-2B yet.
Opus made the right architectural move by removing Path B rebuild. However, the practical prerequisite is still unresolved: the canonical candidate-units-r2.json is local /tmp on the Mac that ran R2, while P10B-2B likely needs VPS/DB context.
Per Zero Trust, do not start package generation until the JSON artifact is promoted to a stable Agent Data KB path or confirmed present on the same execution host.
Required next action
Run a micro-step first:
P10B-2B-INPUT — Promote D28 candidate-units-r2.json to KB
Scope: read-only with respect to production DB. Upload artifact only.
Input:
/tmp/p10b-2a-r2/candidate-units-r2.json
Output KB path:
knowledge/dev/laws/dieu38-trien-khai/data/p10b-d28-candidate-units-r2.json
Required checks:
- File exists on the host that ran R2.
- SHA256 matches
e47775e33cc752656468edb287cca7b58539804678443b6c1b1dd03b165de8ad. - JSON has 27 entries.
- Each entry has full body and required fields.
- Upload JSON to KB as
application/json. - Read back from KB and verify SHA matches.
- STOP.
After this input-promotion step passes, patch P10B-2B T0 to use the KB artifact as canonical input, with local /tmp only as optional cache.
Patch to P10B-2B v0.3 after input promotion
Change T0 to:
- Fetch canonical JSON from:
knowledge/dev/laws/dieu38-trien-khai/data/p10b-d28-candidate-units-r2.json - Save to
/tmp/p10b-2b/candidate-units-r2.json. - Verify SHA exactly.
- Local
/tmp/p10b-2a-r2/...may be used only as cache if it also matches, but KB artifact is source-of-truth. - If KB JSON missing or SHA mismatch: STOP.
Legal / constitutional rationale
This follows:
- Zero Trust: no uncertain input.
- Red-zone anti-hardcode: no re-segmentation, no case-dispatch per section.
- No manual production mutation: P10B-2B remains package generation only.
Direction to Opus
Do not dispatch P10B-2B yet.
First dispatch P10B-2B-INPUT to the Agent/Mac where R2 ran, promote the JSON artifact to KB, read back and verify SHA.
Then issue P10B-2B v0.4 using KB JSON as canonical input.