Incomex AI Portal
KB-574D

dot-iu-cutter v0.5 Fabric Addendum Scope + WS-1 — GPT Review

11 min read Revision 1
dot-iu-cutterv0.5fabric-addendumws-1gpt-reviewpass-with-rulingsdieu44dieu382026-05-18

dot-iu-cutter v0.5 Fabric Addendum Scope + WS-1 — 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-fabric-addendum-existing-design-map-and-workstreams-2026-05-18.md
  - dot-iu-cutter-v0.5-WS1-relation-topic-assembly-design-brief-2026-05-18.md
  - dot-iu-cutter-v0.5-fabric-addendum-open-decisions-2026-05-18.md
  - dot-iu-cutter-v0.5-fabric-addendum-report-2026-05-18.md

Verdict

fabric_addendum_scope_ws1_package: PASS_WITH_RULINGS
agent_behavior: PASS_CORRECT
opus_review: SUBSTANTIALLY_CORRECT
forbidden_respected: true
self_advance_respected: true
ready_to_make_WS1_brief_authority: true
ready_for_schema_or_code_execution: false

Agent completed the requested design-only phase correctly. The package is coherent, references prior designs rather than redesigning them, identifies the true gaps G1..G5, and produces a useful WS-1 brief.

This review accepts the package as the current WS-1 design authority, with explicit rulings below.

Quality assessment

mandatory_read_coverage: PASS
avoid_redesign: PASS
G1_assembly_contract: PASS
G2_entity_binding: PASS_WITH_CLARIFICATION
G3_topic_registry: PASS
G4_cross_source_family_assembly: PASS_WITH_EDGE_GATE
G5_directus_boundary: PASS
open_decisions: PASS_WITH_RULINGS
no_executable_SQL: PASS
no_mutation: PASS

Opus's report is accurate: the output follows the prompt, stays within design-only boundaries, and does not violate forbidden operations.

Rulings on OD-FA1..OD-FA8

OD-FA1 — assembly_profile storage

ruling: APPROVE_LOGICAL_CONTRACT_NOW__PHYSICAL_STORAGE_DEFERRED

Approve assembly_profile as a logical contract now. Do not create a table yet. Physical storage must be designed later in a schema-design cycle with sovereign gate.

OD-FA2 — IU↔entity binding option

ruling: APPROVE_OPTION_D_HYBRID_WITH_BOUNDARY_CLARIFICATION

Approve Option D hybrid:

universal_edges:
  purpose: Object↔Object / IU↔IU semantic relation, preserving P44-4A semantics

iu_entity_binding:
  purpose: IU↔raw external/business authority entity binding

Boundary clarification:

registered_object:
  definition: object already governed by the Object/IU universe and eligible for universal_edges under P44-4A/OQC contracts
  examples: IU, publication object, registered projection object, governed document object

raw_entity:
  definition: authoritative object from a business or operational system that is not itself an IU/Object in the relation graph
  examples: customer_id, contract_id, invoice_id, GitHub file path, code module, Directus item id, report path

rule:
  - Use universal_edges only when both ends are governed Objects/IUs.
  - Use iu_entity_binding when one side is a raw external/business authority entity.
  - Do not copy full SQL/business data into IU text.
  - Assembly profiles may consume both universal_edges and iu_entity_binding.

This clarification is binding for WS-2/WS-3.

OD-FA3 — topic registry option

ruling: APPROVE_OPTION_C

Approve logical topic registry contract now; physical topic_vocab table remains deferred. This preserves P11D's defer decision while reducing duplicate topic risk.

OD-FA4 — new cross-family edge types

ruling: NOT_APPROVED_AS_6_EDGE_BATCH__REQUIRES_EDGE_APR_MINIMIZATION

The package correctly flags 6 candidate edge types, but GPT does not approve them as a batch. Before WS-3 can use new edge types, Agent must prepare a narrow APR/minimization note that classifies each candidate into one of three buckets:

bucket_1_reuse_existing_P44_edge:
  use_when: existing P44-4A edge already covers the semantics well enough

bucket_2_model_as_iu_entity_binding_or_assembly_relation:
  use_when: relation is mainly IU↔raw entity or assembly-local, not a durable IU↔IU semantic edge

bucket_3_candidate_new_edge_requires_APR:
  use_when: semantics are durable, cross-source, cannot be represented by existing P44 edges or binding without losing important meaning

Provisional guidance:

constrains:
  default: reuse governed_by or compatible/contradicts context, with relation metadata if needed
  new_edge_status: not approved now

maps_to_process:
  default: use iu_entity_binding when target is process entity; use existing references/implements if both sides are IUs
  new_edge_status: not approved now

maps_to_code:
  default: use iu_entity_binding when target is code file/module; use implements/references if both sides are IUs
  new_edge_status: not approved now

maps_to_requirement:
  default: evaluate case-by-case; often compliance_matrix assembly relation or implements/governed_by may cover it
  new_edge_status: candidate only, APR required if retained

evidenced_by:
  default: strongest candidate for a true new durable edge, because evidence relation differs from references/implements
  new_edge_status: candidate APR allowed

lesson_from:
  default: evaluate reuse of derived_from/references plus source_family=lesson; do not create by default
  new_edge_status: candidate only, APR required if retained

No new edge type is approved by this review.

OD-FA5 — entity_reference_registry field scope

ruling: APPROVE_CORE_MINIMAL

Approve minimal core registry shape with deferred permission/snapshot details. This avoids over-design before a real contract/entity pilot.

OD-FA6 — Directus boundary formalization

ruling: APPROVE_AS_BOUNDARY_FORMAL_FOR_CURRENT_FLOW

Approve G5 as the formal Directus/IU Fabric boundary for this line of work. Later legal/law-level codification may be separate.

OD-FA7 — authority_semantics attach point

ruling: APPROVE_SOURCE_FAMILY_DEFAULT_WITH_UNIT_LEVEL_OVERRIDE

The Agent recommended deriving authority semantics from source_family. This is correct as the default. However, GPT adds an edge-case rule:

authority_semantics:
  default_source: source_family registry
  override_allowed: unit-level or span-level authority_role override when one source contains mixed authority roles
  examples:
    - a law text with an attached explanatory appendix
    - a report that embeds an official requirement excerpt
    - a code repository file that includes both implementation and compliance notes
  rule: assembly output must label whether each included unit is normative_authority, evidence_authority, or implementation_authority for that assembly context

This prevents false classification when a single source family contains mixed material.

OD-FA8 — assembly engine generic vs per-type

ruling: APPROVE_GENERIC_EXECUTOR_AS_LOGICAL_DIRECTION

Approve the logical direction of a generic executor that reads assembly_profile and runs P11D-style pipeline. No code work is authorized.

Required next phase

Do not jump directly to WS-2 or WS-3 implementation. The next phase should be a narrow design-review cleanup:

next_phase: v0_5_WS1_edge_APR_minimization_and_authority_override_note
nature: design_only

Purpose:

purpose:
  - convert OD-FA4 from a 6-edge candidate list into a minimized APR-ready recommendation
  - formalize registered_object vs raw_entity boundary for Option D hybrid binding
  - add authority_semantics override rule for mixed-authority sources
  - update routing for WS-2/WS-3 based on these rulings

This is a short corrective/addendum phase, not a redesign.

Agent directive for next phase

Open a design-only phase:

phase: v0_5_WS1_edge_APR_minimization_and_authority_override_note
output_path: knowledge/dev/laws/dieu44-trien-khai/v0.5-fabric-addendum-scope/

Read first:

read_first:
  - knowledge/dev/laws/dieu44-trien-khai/reviews/dot-iu-cutter-v0.5-fabric-addendum-scope-ws1-gpt-review-2026-05-18.md
  - knowledge/dev/laws/dieu44-trien-khai/v0.5-fabric-addendum-scope/dot-iu-cutter-v0.5-WS1-relation-topic-assembly-design-brief-2026-05-18.md
  - knowledge/dev/laws/dieu44-trien-khai/v0.5-fabric-addendum-scope/dot-iu-cutter-v0.5-fabric-addendum-open-decisions-2026-05-18.md
  - knowledge/dev/laws/dieu44-trien-khai/design/05-relation-edge-conformance-design.md
  - knowledge/dev/laws/dieu38-trien-khai/closure/p11d-logical-topic-view-proof-design.md

Create two files:

files:
  1:
    name: dot-iu-cutter-v0.5-WS1-edge-APR-minimization-note-2026-05-18.md
    content:
      - classify constrains, maps_to_requirement, maps_to_process, maps_to_code, evidenced_by, lesson_from into reuse_existing / entity_binding_or_assembly_relation / true_new_edge_APR
      - for each candidate, explain whether existing P44 edge covers it
      - recommend the smallest possible new edge set
      - prepare APR-ready wording only for truly necessary new edge types
      - do not approve or create edge types

  2:
    name: dot-iu-cutter-v0.5-WS1-binding-authority-clarification-note-2026-05-18.md
    content:
      - define registered_object vs raw_entity for Option D binding
      - define when universal_edges applies and when iu_entity_binding applies
      - add authority_semantics default + unit/span override rule
      - update downstream routing for WS-2/WS-3/WS-4

Forbidden:

forbidden:
  - schema migration
  - production write
  - code change
  - index DDL execution
  - CUT
  - VERIFY
  - dry-run
  - Directus mutation
  - vector/NoSQL integration
  - create edge types
  - create tables
  - approve APR on behalf of GPT/User
  - git commit

After upload, stop and route to GPT/User review.

Routing after cleanup phase

If cleanup PASS:

routing:
  1: promote WS-1 brief + cleanup notes as current WS-1 authority
  2: open WS-2 Metadata Key Registry + Source Profile design
  3: open edge APR only if minimized set still requires true new edges
  4: open WS-3 assembly-by-topic cross-source only after WS-2 and edge APR readiness

Final status

status: PASS_WITH_RULINGS
execution_authorized: false
next_action: run_short_design_cleanup_phase
Back to Knowledge Hub knowledge/dev/laws/dieu44-trien-khai/reviews/dot-iu-cutter-v0.5-fabric-addendum-scope-ws1-gpt-review-2026-05-18.md