GPT Review — E-E3 Amendment P8 §5

Date: 2026-04-27 Scope: Review Opus E-E3 amendment draft for P8 §5 Đ24 Label Integration.

Verdict

PASS with minor wording patches before applying into P8 v0.4.

Checks

• Doc-only scope: PASS. No DDL/DML, no facet creation, no taxonomy write.
• Đ24: PASS. Labels remain in entity_labels only; doc/topic/layer are aliases; production uses governed facets after APR.
• Đ32/APR: PASS. No APR = no facet creation. Candidate codes FAC-07/FAC-08/FAC-09 are not treated as approved.
• P9 Tier 2 sequencing: PASS. E2 amendment creates basis for later E4 APR request.
• E-R3 adapter reference: PASS with wording patch needed; created function is a production artifact, but runtime write through it still requires checker/DOT scope and governed execution.

Required minor patches

1. In §5.1, change “Production code sẽ là kết quả APR” to “Production code/facet identity sẽ là kết quả APR.” This avoids implying only code can change while name/scope can also be modified/rejected.
2. In §5.3 flow, make clear APR creation itself must be via approved DOT/API path; do not imply manual APR creation.
3. In §5.5, add “Function exists; usage by checkers/DOTs requires those DOTs to be registered/approved.”
4. In §5.2 coverage, replace approximate counts (~30/~40) with “verified by P7A/C2B set; exact count in reports” or exact counts if Opus can cite them.

Direction

Patch the amendment, then apply it into P8 as v0.4 OFFICIAL draft/revision. After P8 v0.4 is updated, proceed to E4 APR request design for FAC-07/08/09. Do not create facets, register DOTs, or start P9 migration.