dot-iu-cutter v0.5 WS-2 Metadata Key Registry + Source Profile — GPT Review

Date: 2026-05-18 Reviewer: GPT Reviewed package: knowledge/dev/laws/dieu44-trien-khai/v0.5-fabric-addendum-scope/

Reviewed files:

files:
  - dot-iu-cutter-v0.5-WS2-metadata-key-registry-design-2026-05-18.md
  - dot-iu-cutter-v0.5-WS2-source-family-grammar-authority-design-2026-05-18.md
  - dot-iu-cutter-v0.5-WS2-entity-registry-and-address-namespacing-design-2026-05-18.md
  - dot-iu-cutter-v0.5-WS2-report-2026-05-18.md

Verdict

ws2_metadata_source_profile_package: PASS
agent_behavior: PASS_CORRECT
opus_review: CORRECT
forbidden_respected: true
self_advance_respected: true
ws2_authority_status: READY_TO_PROMOTE
execution_authorized: false

Agent completed WS-2 correctly. The package concretizes metadata registry, source family registry, grammar profiles, authority semantics, entity reference registry, and canonical address namespacing without schema/code execution and without redesigning WS-1/v0.5 concepts.

---

Review findings

D1 — metadata_key_registry

status: PASS

The 11-field pseudo-schema, OD-L1..L5 treatment, and promotion governance are accepted as logical design. No physical table creation is authorized.

D2/D3/D4 — source family / grammar profile / authority semantics

status: PASS

The design correctly separates three independent axes:

source_family: what kind of document/source this is
source_authority_class: how authoritative/trusted the source is
authority_semantics: what role it plays in an assembly context

This separation is important and is accepted as binding for later WS-3 and source/grammar ratification.

Accepted seeds:

source_families_minimum:
  - internal_incomex_constitution
  - internal_incomex_law
  - internal_process
  - external_government_law
  - sql_entity
  - code_artifact
  - report
  - lesson
  - architecture_note

grammar_profiles_minimum:
  - incomex-architecture-constitution-v4
  - vn-national-law

Authority override remains logical only; span-level mechanics may be deferred until a mixed-authority pilot.

D5 — entity_reference_registry

status: PASS

The core-minimal 5-field registry plus deferred permission/snapshot refs is accepted. This is consistent with WS-1 Option D hybrid and avoids over-design before a real contract/entity pilot.

D6 — canonical_address namespacing / OD-A1

status: PASS_WITH_RULING

GPT confirms Agent/Opus recommendation:

canonical_address_scheme: "<DOCPREFIX>/<L1>-<L2>-...-<Lk>"
separator_rule:
  docprefix_separator: "/"
  hierarchy_level_separator: "-"

Reason:

reason:
  - slash cleanly separates document identity from path inside document
  - hyphen preserves readable legacy hierarchy style
  - matches canon example ICX-CONST/NT-12
  - coexists with legacy addresses such as D38-DIEU28-S3-P1

Binding rule:

address_docprefix:
  source: source_document registry
  uniqueness: unique per source_document family/version as governed later
  hardcode: forbidden

status_markers:
  rule: never encode volatile status markers such as ✅ or 📋 into canonical_address
  location: metadata/status policy, not address

---

Promotion ruling

promote_WS2_authority: YES

The current Information Unit Fabric design authority now consists of:

WS1_authority_files: 6
WS2_authority_files: 4
total_authority_files: 10
folder: knowledge/dev/laws/dieu44-trien-khai/v0.5-fabric-addendum-scope/

WS-1 + WS-2 are now accepted as the current logical design authority for the Information Unit Fabric addendum.

---

Next routing decision

GPT agrees with Opus recommendation: open WS-3 next.

next_phase: v0_5_WS3_cross_source_topic_assembly_logical_proof
nature: design_only_logical_proof

Why WS-3 next:

reason:
  - WS-1 defined assembly_profile, binding, authority semantics, Directus boundary
  - WS-2 defined metadata/source/grammar/entity/address registry contracts
  - WS-3 should now test whether these designs work together in a logical cross-source assembly proof
  - physical schema tables should wait until after this logical proof

evidenced_by APR remains a parallel/conditional design route, not a blocker if WS-3 runs without persisting or requiring the new edge.

WS-3 must not execute code, create views/tables, mutate data, run dry-run, or approve/create evidenced_by. It may use evidenced_by only as a proposed/APR-gated relation in logical examples, or show alternative output without it.

---

WS-3 directive summary

WS-3 should create a logical proof for cross-source topic assembly, using a sample topic such as:

sample_topic: collection_structure
human_label: cấu trúc collection

The proof should show how the system assembles a chain across:

chain:
  - internal_incomex_constitution
  - internal_incomex_law
  - internal_process
  - sql_entity / Directus collection / PG schema
  - code_artifact
  - report
  - lesson

WS-3 should consume:

inputs:
  - assembly_profile logical contract from WS-1
  - topic registry logical contract from WS-1
  - source_family registry from WS-2
  - grammar_profile from WS-2
  - authority_semantics default + override from WS-2
  - entity_reference_registry from WS-2
  - canonical_address scheme from WS-2
  - edge minimization result from WS-1 cleanup

Required outputs should be defined in a separate Agent prompt.

---

Still forbidden

still_forbidden:
  - schema migration
  - table creation
  - edge type creation
  - production write
  - code change
  - index DDL execution
  - CUT
  - VERIFY
  - dry-run
  - Directus mutation
  - vector/NoSQL integration
  - git commit
  - Agent self-advance

Final status

status: WS2_PASS__WS1_WS2_AUTHORITY_PROMOTED
next_action: open_WS3_cross_source_topic_assembly_logical_proof