GPT Review — E4 APR Request Package FAC-07/08/09

Date: 2026-04-27
Scope: Review knowledge/dev/laws/dieu38-trien-khai/P9-e4-apr-request-fac-07-08-09.md against Handoff, P8 v0.4 §5, Đ24/Đ32/Đ33/Đ35 governance constraints.

Verdict

PASS WITH MINOR PATCHES BEFORE NEXT GATE.

E4 is correctly framed as a doc/governance request package. It does not create facets, does not write taxonomy_facets, does not run E5/E7/P9, and correctly treats FAC-07/FAC-08/FAC-09 as candidates subject to Council/User approve/modify/reject.

Evidence checked

• knowledge/dev/laws/dieu38-trien-khai/index.md — confirms P8 v0.4, E-E3 PASS, next E4 APR FAC-07/08/09.
• knowledge/dev/laws/dieu38-trien-khai/P8-implementation-design-plan-v0-1.md — §5.1 alias mapping; §5.3 governed APR/DOT/API flow; §5.4 entity_labels-only.
• knowledge/dev/laws/dieu38-trien-khai/P8-s5-amendment-e-e3.md — APPLIED, doc-only, no DDL/DML.
• knowledge/dev/laws/dieu38-trien-khai/P9-tier2-remediation-design.md — R1 requires governed taxonomy addition; no direct seed; no APR = no facet creation.
• knowledge/dev/laws/dieu38-trien-khai/P9-e4-apr-request-fac-07-08-09.md — reviewed draft.

Constitutional / law check

Rule	Result	Note
Đ24 labels	PASS	E4 preserves label storage through entity_labels; facet creation is via taxonomy governance.
Đ32 APR	PASS	Council/User can approve, modify, reject, or partial approve.
Đ33 API/DOT flow	PASS with wording patch	E5 must execute approved writes via Directus API/DOT only, not manual SQL/UI.
Đ35 DOT	PASS	DOT-TAC-LABEL-SYNC is named as execution path after approval.
P8 v0.4 §5	PASS	doc/topic/layer are aliases; FAC-07/08/09 are candidates only.
No mutation in E4	PASS	E4 is doc-only; no DDL/DML/facet creation.

Required minor patches

1. Clarify label values are not approved by current facet-only APR payload.
   Current machine-readable APR payload requests only taxonomy_facets INSERTs. Section 7 says E5 will also create initial taxonomy_labels; this would be an additional mutation not covered by the shown payload. Patch by either:

   • adding child APR payload entries for taxonomy_labels, or
   • marking initial label values as preview-only and requiring separate APR/request payload before creation.

2. Clarify E5 boundary.
   E5 may execute only approved APR items. If APR approves facets only, E5 creates facets only. No automatic label-value creation unless explicitly approved in APR payload.

3. Retain candidate wording everywhere.
   Keep FAC-07/08/09 phrased as candidate/proposed codes until APR outcome is recorded. Production identity must remain APR outcome.

Direction

Opus should patch E4 with the three items above, then report back for GPT/User review. Do not run E5, E7, or P9. Do not create APR records, facets, or labels unless a separate governed approval gate explicitly authorizes that mutation.

Next gate after patch

• If patched E4 passes: submit/review APR decision package.
• If Council/User approves or modifies: prepare E5 execution prompt scoped to the approved APR outcome only.
• If rejected: patch P8 §5 alias mapping and design an alternative; no creation.