GPT Analysis — Topic Axis Governance Operational Gap and Design Direction

Date: 2026-06-01 Reviewer: GPT Council

Verdict

User is correct: besides the technical build authorization gap, the topic/semantic-axis workflow is a real design gap. Governance alone cannot solve semantic correctness. Topic determination must rely on Điều 38 Text-as-Code and Điều 39 Knowledge Graph / semantic relation infrastructure, with governance managing lifecycle, ownership, approval, UI exposure, and issue detection.

Key design principle

Do not force immediate certainty for semantic topics. Separate:

• source reconstruction / containment axis: deterministic, structure-first;
• topic/professional semantic axis: uncertain, evidence/confidence/proposal-driven;
• UI/governed topics: stable subset approved for human-facing navigation;
• KG/search topics: broader, dynamic, AI-facing, can remain provisional.

Required design additions before topic/IU operational build

• Topic Registry / Axis Registry readiness.
• Topic hierarchy / DAG relation model, allowing multi-parent topics.
• Topic lifecycle: candidate, provisional, active, merged, split, deprecated, rejected.
• Topic provenance/evidence/confidence model.
• Human-specified topic path as highest priority.
• AI-proposed topic path with human/governance approval before UI-fixed status.
• KG-assisted discovery path under Điều 39 for dynamic/AI-facing retrieval.
• Governance coverage trigger when a topic becomes fixed/governed/UI-visible.
• Quality loops for wrong topic, overlap, drift, too-broad/too-narrow topics, duplicate aliases.
• Clear boundary: containment axis can be validated by reconstruction; semantic topic axis requires evidence and review.

Operational implication

Do not build topic/UI/axis operational workflows yet. First run a broad live audit and design addendum connecting Điều 38, Điều 39, taxonomy/label, IU, KG, and One-Roof Governance. Phase 1 foundation substrate can still proceed after authorization issue is solved if it remains empty/inactive, but T6/T7/backfill/topic/IU operational activation must wait for this addendum.