GPT Decision — P10B Cross-Machine FAIL: Option B

Date: 2026-04-29

Decision

Choose Option B — promote SQL package artifacts to KB before PF-R2 / execute.

Do not use /tmp as source-of-truth across machines.

Rationale

This is the second cross-machine failure:

1. candidate-units-r2.json existed on one machine but not the other.
2. The FIX SQL bundle existed on VPS /tmp but PF-R2 ran on Mac.

This is no longer an incidental failure; it is an operating-pattern failure.

/tmp is acceptable as a local workspace only. It is not an inter-agent or cross-machine SSOT.

Direction to Opus

Create a micro-step:

P10B-2B-FIX-PROMOTE — Promote D28 FIX SQL Package to KB

Scope: read-only file upload. No SQL execution.

Agent must run on the machine that has /tmp/p10b-2b-fix/ files, preferably VPS where FIX package was generated.

Upload canonical package artifacts to KB folder:

knowledge/dev/laws/dieu38-trien-khai/data/p10b-d28-fix-package/

Required uploads:

1. candidate-units-r2.json
2. birth-gate-requirements.json
3. insert-candidate.sql
4. render.sql
5. rollback.sql
6. verify-counts.sql
7. generator script(s), e.g. gen.py, build_matrix.py if present
8. package manifest manifest.json

Manifest requirements

manifest.json must include:

• file names;
• KB paths;
• SHA256;
• byte size;
• source local path;
• generated_at;
• package version: p10b-2b-fix;
• expected row counts: pub=1, lu=27, uv=27, pm=27;
• note: PF-R2 required before execute.

Next step after promotion

Patch PF-R2 to fetch all files from KB canonical package folder into a local workdir, then verify SHA from manifest.json.

PF-R2 may run on any machine after promotion.

Permanent rule

Any artifact needed by a later step or another machine must be promoted to KB or repo SSOT before handoff.

Do not pass /tmp paths as cross-agent inputs.