dot-iu-cutter v0.5 WS-1 — Binding + Authority Clarification Note

Phase: design-only cleanup · 2026-05-18 · Authority: GPT review PASS_WITH_RULINGS (OD-FA2 = APPROVE_OPTION_D_HYBRID_WITH_BOUNDARY_CLARIFICATION; OD-FA7 = APPROVE_SOURCE_FAMILY_DEFAULT_WITH_UNIT_LEVEL_OVERRIDE). Self-contained.

Design-only. No tables/edges created, no schema/code/dry-run, no APR approval. This note formalizes the binding boundary and the authority_semantics override rule, and updates downstream routing.

---

1. registered_object vs raw_entity (binding boundary — binding for WS-2/WS-3)

registered_object:
  definition: >
    Object already governed by the Object/IU universe and eligible for
    universal_edges under P44-4A / OQC contracts.
  examples:
    - IU (information_unit)
    - 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

Reference: P44-4A §2.1 — a universal_edges endpoint must be an Object satisfying OQC ≥ 3/4. A raw_entity does not satisfy OQC and is not registered in the relation graph, so it cannot be a universal_edges endpoint. universal_edges semantics (P44-4A) are not redesigned here.

---

2. When universal_edges applies vs when iu_entity_binding applies

rule:
  - Use universal_edges ONLY when BOTH ends are governed Objects/IUs
    (registered_object ↔ registered_object). Preserves P44-4A semantics
    (8 core + 3 candidate edge types; INV-DUAL; reverse-index).
  - Use iu_entity_binding when ONE side is a raw external/business
    authority entity (registered_object IU ↔ raw_entity).
  - Do NOT copy full SQL/business data into IU text — bind by reference
    (entity_reference_registry: entity_ref_id, entity_kind, source_system,
    natural_key, authority_note) + provenance; read live from SSOT at
    assembly time.
  - assembly_profile MAY consume BOTH universal_edges and iu_entity_binding.

Decision table:

Source side	Target side	Mechanism
IU	IU / registered_object	universal_edges (P44-4A edge type)
IU	raw_entity (customer/contract/invoice/git file/code module/Directus item/report path)	iu_entity_binding (+ entity_reference_registry)
raw_entity	raw_entity	out of scope — neither side is an IU; not Fabric's concern

iu_entity_binding carries binding_kind (resolve via registry, e.g. describes|governs|implements|evidences|references_entity) + auditable provenance (who/when/why/source) + append-only retracted_at. SQL/entity remains authority; IU stores semantic reference only (Option D hybrid, OD-FA2).

---

3. How assembly_profile consumes both

assembly_profile (G1, OD-FA1 approved as logical contract) input_selector / relation_filter may pull:

• universal_edges rows (IU↔IU semantic relations, e.g. implements, governed_by, references, plus evidenced_by once APR-approved — see edge-minimization note);
• iu_entity_binding rows (IU↔raw_entity, e.g. an architecture-note IU bound to a GitHub file);
• assembly-local relations computed at assembly time (output-only grouping, not persisted).

The generic executor (OD-FA8 approved as logical direction) runs the P11D §6.1 pipeline GATHER→ENRICH→GROUP→QUALITY→PROVENANCE over the union, respecting P11D §5.3.1 edge whitelist for ENRICH. No code authorized.

---

4. authority_semantics — default + unit/span override

authority_semantics:
  default_source: source_family registry        # OD-FA7 default (WS-2 concretizes)
  roles:
    - normative_authority      # có quyền quy định (constitution / internal law / external gov law)
    - evidence_authority       # chứng minh đã/chưa làm (report, lesson, verification artifact)
    - implementation_authority # đang chạy thật (SQL schema, code artifact)
  override_allowed:
    level: unit-level OR span-level authority_role override
    when: a single source contains MIXED authority roles
  rule: >
    Assembly output MUST label EACH included unit as exactly one of
    normative_authority | evidence_authority | implementation_authority
    FOR THAT ASSEMBLY CONTEXT (default from source_family, replaced by
    unit/span override when present).

Mixed-authority source examples (override required):

• A law text with an attached explanatory appendix — law body = normative_authority; appendix/giải thích span = evidence_authority (explanatory, not binding).
• A report that embeds an official requirement excerpt — report body = evidence_authority; embedded requirement excerpt span = normative_authority.
• A code repository file containing both implementation and a compliance note — code = implementation_authority; embedded compliance-note span = normative_authority (or evidence_authority if it attests).

Default-only (no override) classification would mislabel these (entire file → one role), so unit/span override prevents false classification. Override is logical metadata at assembly/binding time — no new IU core column (respects P38-XC UMC; not over-design). Concrete attach point (source_family registry + override storage) is WS-2 work.

---

5. Updated downstream routing (per GPT rulings)

WS-1:
  status: brief + cleanup notes = current WS-1 authority AFTER this cleanup PASS
  carries: G1 assembly_profile (logical), Option D hybrid binding boundary (§1-§3),
           authority_semantics default+override (§4), edge-minimization (sole new
           edge candidate = evidenced_by, APR-gated)

WS-2 (Metadata Key Registry + Source Profile) — NEXT after cleanup PASS:
  scope: concretize metadata_key_registry (v0.5 Label/Metadata concept);
         source profile for internal_incomex_governance + external_government_law;
         grammar profile per source family;
         source_family registry + authority_semantics default mapping +
         unit/span override storage shape (OD-FA7);
         entity_reference_registry core-minimal concretization (OD-FA5)
  inherits OD: OD-A1, OD-L1..OD-L5, OD-FA7(registry)
  forbidden: no schema/table creation (design only)

edge APR (Đ32 cấp medium) — conditional:
  trigger: only if minimized set still requires a true new edge
  current: minimized set = { evidenced_by } (1) → APR readiness needed before
           WS-3 cross-source assembly uses it
  authority: GPT/User only (agent must NOT approve APR)

WS-3 (assembly-by-topic cross-source):
  gate: AFTER WS-2 AND evidenced_by APR readiness (or explicit decision to run
        WS-3 without evidenced_by)
  uses: generic executor + P11D pipeline + assembly_profile (G1)
  defer: P11D-β (source method detail), P11D-ζ (Q-T3 whitelist final)

WS-4 (Edit/Amend/Supersede):
  priority: high_after_WS1_WS2 (GPT Position)
  prerequisite: 23-P2 read-only inspection (version_seq) before any implement
  inherits: TD-P1 split/merge metadata propagation, OD-R1 forward-compensation
  status: detailed design deferred; WS-1 confirmed non-blocking for amend/split/merge/supersede

---

6. Statements & status

• Binding boundary (§1–§3) and authority_semantics override (§4) are binding for WS-2/WS-3 per GPT ruling.
• No edge type approved/created; no APR approved (sole new-edge candidate evidenced_by is APR-gated, GPT/User only).
• No table created, no schema/code/dry-run/Directus mutation/vector integration, no git commit.
• Not self-advancing to WS-2/WS-3/WS-4 — this is the corrective addendum only.
• Git/access: no repo/VPS access in this session. No write attempted. code_changed: false; commit_made: false.
• STOP after upload → route to GPT/User review.