dot-iu-cutter v0.5 WS-1 — Edge APR Minimization + Binding/Authority Clarification Agent Prompt

Date: 2026-05-18
Phase: v0_5_WS1_edge_APR_minimization_and_authority_override_note
Nature: design-only cleanup
Authority: GPT review + Opus concurrence + User routing

---

0. Objective

Perform a short design-only cleanup before WS-1 is promoted as current authority.

This phase must:

objectives:
  - minimize OD-FA4 new edge candidates before any APR
  - clarify Option D hybrid binding boundary: registered_object vs raw_entity
  - clarify when universal_edges applies vs when iu_entity_binding applies
  - add authority_semantics default + unit/span-level override rule
  - update downstream routing for WS-2 / WS-3 / WS-4

This is not a redesign of WS-1 and not an execution phase.

---

1. Read first

Read the GPT review fully:

knowledge/dev/laws/dieu44-trien-khai/reviews/dot-iu-cutter-v0.5-fabric-addendum-scope-ws1-gpt-review-2026-05-18.md

Read these supporting documents before writing:

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

---

2. Output path

Create exactly 2 files under:

knowledge/dev/laws/dieu44-trien-khai/v0.5-fabric-addendum-scope/

Use tags:

tags:
  - dot-iu-cutter
  - v0.5
  - fabric-addendum
  - ws-1
  - edge-apr
  - binding
  - authority-semantics
  - design-only
  - dieu44
  - dieu38
  - 2026-05-18

---

3. File 1 — Edge APR minimization note

Create:

dot-iu-cutter-v0.5-WS1-edge-APR-minimization-note-2026-05-18.md

Required content:

required:
  - classify the 6 edge candidates:
      - constrains
      - maps_to_requirement
      - maps_to_process
      - maps_to_code
      - evidenced_by
      - lesson_from
  - classify each candidate into one of these buckets:
      bucket_1_reuse_existing_P44_edge
      bucket_2_model_as_iu_entity_binding_or_assembly_relation
      bucket_3_true_new_edge_requires_APR
  - for each candidate:
      - explain whether existing P44-4A edge semantics can cover it
      - explain when iu_entity_binding is better than a new edge
      - explain when assembly-local relation is enough
      - state whether it should remain an APR candidate
  - recommend the smallest possible new edge set
  - prepare APR-ready wording only for truly necessary new edge types
  - explicitly state that no edge type is approved or created by this note

Use GPT's provisional guidance as the starting point:

provisional_guidance:
  constrains:
    default: try reuse governed_by / compatible_with / contradicts context before creating new edge
  maps_to_process:
    default: use iu_entity_binding when target is process entity; use references/implements if both sides are IUs
  maps_to_code:
    default: use iu_entity_binding when target is code file/module; use implements/references if both sides are IUs
  maps_to_requirement:
    default: evaluate case-by-case; often compliance_matrix assembly relation or implements/governed_by may cover it
  evidenced_by:
    default: strongest candidate for true new durable edge
  lesson_from:
    default: try derived_from/references plus source_family=lesson before creating new edge

Quality bar:

edge_minimization_principle:
  - prefer reuse over new edge
  - prefer iu_entity_binding for IU→raw entity targets
  - prefer assembly-local relation for output-only grouping
  - only keep a new edge candidate when durable semantic meaning would be lost otherwise

---

4. File 2 — Binding + authority clarification note

Create:

dot-iu-cutter-v0.5-WS1-binding-authority-clarification-note-2026-05-18.md

Required content:

required:
  - define registered_object vs raw_entity
  - define when universal_edges applies
  - define when iu_entity_binding applies
  - clarify how assembly_profile may consume both universal_edges and iu_entity_binding
  - add authority_semantics rule:
      default: derive from source_family registry
      override: allow unit-level or span-level authority_role override for mixed-authority sources
  - include examples of mixed-authority sources:
      - law text with explanatory appendix
      - report embedding official requirement excerpt
      - code repository file containing implementation and compliance note
  - state that assembly output must label each included unit as one of:
      - normative_authority
      - evidence_authority
      - implementation_authority
  - update downstream routing for WS-2, WS-3, WS-4

Binding boundary must follow GPT ruling:

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.

---

5. 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
  - self-advance to WS-2/WS-3/WS-4

---

6. Git / access note

No code change expected.

If read-only repo/VPS access is available, report branch, HEAD, and git status --short -- iu-cutter.

If no repo/VPS access is available, state clearly:

no repo/VPS access in this session

Do not attempt any write operation.

---

7. Stop condition

After uploading the 2 files:

stop:
  - do not proceed to WS-2
  - do not proceed to WS-3
  - do not proceed to WS-4
  - route back to GPT/User review