dot-iu-cutter v0.5 evidenced_by APR — Sovereign GPT Ruling

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

Reviewed files:

files:
  - dot-iu-cutter-v0.5-evidenced-by-edge-APR-draft-2026-05-18.md
  - dot-iu-cutter-v0.5-evidenced-by-edge-risk-and-alternative-review-2026-05-18.md
  - dot-iu-cutter-v0.5-evidenced-by-APR-draft-report-2026-05-18.md

Verdict on draft quality

evidenced_by_APR_draft_package: PASS
agent_behavior: PASS_CORRECT
opus_review: CORRECT
forbidden_respected: true
self_advance_respected: true

The APR draft is complete, grounded in P44-4A §3.3, and correctly distinguishes evidenced_by from references, implements, derived_from, governed_by, and iu_entity_binding.

---

Sovereign decision on OD-EB1

OD_EB1_decision: APPROVE_EVIDENCED_BY_AS_NEW_DURABLE_EDGE_TYPE
apr_tier: medium_Điều_32
edge_type: evidenced_by
reverse_type: evidences
edge_family: relation_Cap_4
approval_scope: design_APR_approval_only

GPT approves evidenced_by as a valid new durable IU↔IU relation edge type, subject to the constraints below.

This approval means:

approved_meaning: >
  Source IU is evidenced_by Target IU when Target, an evidence-authority IU,
  attests that Source, a normative/requirement/claim IU, was satisfied,
  performed, or demonstrated.

reverse_meaning: >
  Target IU evidences Source IU.

---

Strict boundaries of approval

This ruling approves the edge type at the APR/design-governance level only. It does not authorize execution.

not_authorized_by_this_ruling:
  - edge_type vocab amendment execution
  - DOT Cap-4 checker code change
  - schema migration
  - table/view/function/index creation
  - production write
  - backfill
  - data migration
  - CUT
  - VERIFY
  - dry-run
  - Directus mutation
  - vector/NoSQL integration
  - git commit

Before evidenced_by can be used in any implementation or production path, a separate design/command-review cycle must specify and verify:

post_approval_required_work:
  - edge_type vocab framework amendment design
  - Cap-4 checker extension design
  - anti-drift validation rules
  - endpoint OQC validation
  - provenance/lifecycle validation
  - rollback/compensation plan for vocab/checker changes
  - command review before any execution

---

Binding usage rules

use_evidenced_by_when:
  - both endpoints are registered IUs / governed Objects
  - both endpoints satisfy OQC >= 3/4
  - source is a normative/requirement/claim IU
  - target is an evidence-authority IU
  - relation means target attests source was satisfied/performed/demonstrated

must_not_use_evidenced_by_when:
  - target is a raw evidence entity such as report path, file path, Directus item id, code module, SQL entity
  - relation is only a weak mention or citation
  - relation is implementation/spec realization
  - relation is creation provenance
  - relation is governance/authority control

Required alternatives:

raw_evidence_entity: use iu_entity_binding with binding_kind=evidences
weak_mention: use references
implementation_relationship: use implements
creation_provenance: use derived_from
governance_authority: use governed_by

---

Why approval is justified

justification:
  minimization_result: evidenced_by was the only survivor from the original 6 candidate edges
  semantic_gap: existing edges do not express durable attestation/proof
  compliance_need: future compliance_matrix and production evidence chains need queryable proof relation
  vocabulary_cost: exactly one new edge type
  interim_path: WS-3 remains valid with assembly-local alternative until implementation catches up

This is not vocabulary bloat. It is the minimal durable edge required to express evidence/attestation semantics.

---

Effect on authority set

The Information Unit Fabric design authority now includes:

authority_files:
  WS1: 6
  WS2: 4
  WS3: 4
  evidenced_by_APR_package: 3
  APR_ruling: 1
  total: 18
folder: knowledge/dev/laws/dieu44-trien-khai/v0.5-fabric-addendum-scope/
review_path: knowledge/dev/laws/dieu44-trien-khai/reviews/dot-iu-cutter-v0.5-evidenced-by-APR-sovereign-gpt-ruling-2026-05-18.md

Note: the 3 APR draft files plus this ruling are authority for design/governance, not implementation artifacts.

---

Next routing

Open a separate design-only phase:

next_phase: v0_5_evidenced_by_vocab_amend_and_cap4_extension_design
nature: design_only

Purpose:

purpose:
  - convert approved APR semantics into a concrete vocab amendment design
  - define Cap-4 checker extension design
  - define anti-drift, endpoint, provenance, lifecycle validation rules
  - define verification plan
  - define rollback/compensation plan
  - still avoid execution

This phase should not modify code or schema. It should produce design artifacts for later command review.

After that phase passes, the project may choose between:

later_options:
  - schema_design_Q5 for registries and assembly_profile/topic/entity metadata
  - compliance_matrix logical proof using approved evidenced_by semantics
  - source/grammar ratification for actual Constitution fixture

---

Final status

status: EVIDENCED_BY_APR_APPROVED_AT_DESIGN_GOVERNANCE_LEVEL
execution_authorized: false
next_action: open_vocab_amend_and_cap4_extension_design_phase