GPT Review — P10B-2C D28 FAIL BG-UV-02 + Fix Path

Date: 2026-04-29

Verdict

Analysis accepted. Database safe. Fix path authorized.

P10B-2C failed correctly at birth gate BG-UV-02. Transaction auto-rolled back. Baseline preserved. No data loss.

This is not a segmentation/hash/render problem. Candidate JSON and 27-unit evidence remain valid.

Root cause

The D28 tac_unit_version INSERT omitted description.

Current birth gate fn_tac_birth_gate_uv blocks inserts when a section type has description_required=true and description is missing.

D32 passed because its generator included a description=title stub. D28 used a different generator and missed the column.

Process failure

The package/PF review checked:

• row counts,
• SQL escaping,
• transaction structure,
• destructive commands,
• body hashes,
• basic trigger inventory.

But it did not verify candidate data and generated SQL against every birth-gate requirement.

Authorized fix path

Proceed with P10B-2B-FIX — D28 Package Regeneration with Birth-Gate Compliance Matrix.

Do not redo segmentation or hashing.

Required fix tasks

1. Re-read live birth gate function/source and config:

   • fn_tac_birth_gate_lu
   • fn_tac_birth_gate_uv
   • fn_tac_birth_gate_pm if applicable
   • tac_birth_gate_config

2. Build a birth-gate compliance matrix covering all active/blocking requirements:

   • LU: canonical_address regex, section_type, lifecycle/status, parent constraints, required fields.
   • UV: title, body_required, description_required, provenance/review/lifecycle rules, any derived/hash rules.
   • PM: publication/LU/UV linkage, render_order, lifecycle/immutability guards.

3. Patch generator:

   • Add description column to tac_unit_version insert.
   • Use description = title stub for MVP, unless a better generated description is already available.
   • Preserve all existing body escaping, candidate JSON, and SQL structure.

4. Regenerate package files:

   • insert-candidate.sql
   • render.sql if unchanged still include SHA in report
   • rollback.sql if unchanged still include SHA in report
   • verify-counts.sql if unchanged still include SHA in report

5. Run package-level checks:

   • candidate JSON SHA unchanged.
   • 27/27 body SHA unchanged.
   • SQL escaping still safe.
   • collision still 0.
   • description column present in every UV INSERT.
   • sample UV rows include description.

6. Upload P10B-2B-FIX report and STOP.

7. Then run P10B-2C-PF-R2 before execute.

MVP decision

description = title stub is acceptable for MVP, consistent with D32. Production can later generate richer descriptions via Đ43-style templates.

Permanent rule

Every future package generation must include a birth-gate compliance matrix, not only trigger inventory.

PF must also inspect representative INSERT column lists for gate-required fields.