dot-iu-cutter v0.5 — evidenced_by edge_type Vocab Amendment Design

Phase: v0_5_evidenced_by_vocab_amend_and_cap4_extension_design · Nature: design_only · Date: 2026-05-18 Authority: Sovereign GPT ruling OD_EB1_decision: APPROVE_EVIDENCED_BY_AS_NEW_DURABLE_EDGE_TYPE (apr_tier: medium_Điều_32, approval_scope: design_APR_approval_only) + P44-4A 05-relation-edge-conformance-design.md §3.3 step 4.

⚠️ GATING BANNER

phase: design_only
vocab_amend_executed: false        # NO real edge_type vocab change performed
dot_config_mutated: false
directus_mutated: false
code_change: false
sql_executed: none
schema_change: none
execution_authorized: false        # per sovereign ruling: execution NOT authorized
decision_authority: GPT / User ONLY for any future command-review
self_advance: PROHIBITED

This document specifies what the vocab amendment should be. It does not perform it. evidenced_by is APPROVED at design-governance level only; the vocab framework is NOT amended by this file. P44-4A §3.3 step 4 ("APR PASS → amend edge_type vocab framework") is NOT executed here — it requires a separate command-review cycle.

---

1. Scope

This is P44-4A §3.3 step 4 design (vocab amendment), translating the GPT-approved APR semantics into a concrete, reviewable vocab-entry specification. It does not re-argue the APR (that was decided — QG1: this file consumes the ruling, it does not repeat the draft's justification). It produces no executable SQL or config mutation (QG2).

In scope: the logical vocab entry, namespace treatment, lifecycle default, fit with the existing 8+3 set. Out of scope (forbidden): real vocab/config write, code, schema, Directus mutation, dry-run, backfill, data migration, CUT/VERIFY, git commit, self-advance to command execution / schema / compliance_matrix.

2. Proposed edge_type vocab entry (logical specification — NOT applied)

The edge_type vocab framework is the authoritative, non-hardcoded source the DOT Cap-4 writer reads (P44-4A NT4: "Cấm hardcode edge_type list — phải đọc từ vocab framework"). The proposed logical entry to be added (post command-review, NOT now):

# LOGICAL SPEC ONLY — not a config payload, not applied
edge_type_vocab_entry:
  edge_type:        evidenced_by
  reverse_type:     evidences
  owner_law_code:   NRM-LAW-44                 # object-edge ownership (P44-4A §2.3)
  edge_family:      relation                    # Cap-4 (P44-4A §5.8) — NOT composition/Cap-5
  cap_layer:        Cap-4
  directionality:   directional                 # 1 chiều; reverse served via reverse-index
  symmetric:        false
  default_state:    proposed                     # derived/semantic edge default (P44-4A §4.4)
  provenance_required: true                       # post-Đ44 (INV-E4)
  endpoint_kind:    IU<->IU                       # both registered_object / OQC>=3/4
  introduced_by:    "APR Đ32 medium — sovereign GPT ruling 2026-05-18 (OD-EB1 APPROVE)"
  classification:   "P44-4A §3.3 extension (not a Core, not a §3.2 Candidate)"
  vocab_set_after_amend: "8 Core + 3 Candidate + 1 Extension (evidenced_by)"

Logical only. The physical shape of a vocab entry (dot_config row / framework record / JSON schema) is not specified here and not written; that is a command-review concern. This is the semantic contract the future amendment must satisfy.

3. Reverse-type treatment

reverse_type: evidences
convention: named-inverse directional pair (P44-4A §3.4)
  analogous_to:
    - governed_by <-> governs
    - implements  <-> implemented_by
  NOT_like:
    - contradicts (symmetric) — evidenced_by is NOT symmetric
    - supersedes  (1-way, no named reverse) — evidenced_by HAS a named reverse
reverse_serving:
  mechanism: P44-4A §6 reverse-index materialization (DOT-maintained)
  second_physical_row_required: false   # forward row only; reverse via index
  deferred: reverse-index passes P1/P2/P3 remain deferred (carried, not closed here)

4. Namespace treatment — OPEN P44-4-α (still relevant — NOT closed here)

owner_law_code: NRM-LAW-44     # object-edge; tags this as a Đ44 Object-layer edge
namespace_status: OPEN P44-4-α  # STILL OPEN in P44-4A §2.3 — NOT closed by this design
open_question: >
  Final edge_type namespace scheme: prefix `obj.`/`sem.` (e.g. obj.evidenced_by)
  vs `owner_layer` tag vs both. P44-4A §2.3 defers this to the vocab-framework APR.
this_design_position:
  - tag owner_law_code = NRM-LAW-44 (object-edge layer) — unambiguous regardless of scheme
  - if a prefix scheme is later adopted, the canonical token becomes `obj.evidenced_by`
  - this design does NOT pre-empt or decide P44-4-α (flagged as OPEN — QG7)
decision_owner: GPT / User at vocab-framework APR (NOT self-decided here)

5. Lifecycle status proposal

Conforms to P44-4A §4.4 (E7 status enum + transitions). No new lifecycle invented.

status_enum: {proposed, active, deprecated, retired}      # P44-4A §4.4 — unchanged
default_for_evidenced_by: proposed                          # derived/semantic edge → `proposed`
transitions:
  proposed -> active:     after DOT Cap-4 checker verify OR human review (attestation confirmed)
  active   -> deprecated: when superseded (via `supersedes` edge) or evidence retracted upstream
  deprecated -> retired:  after grace period (defer post-pilot — P44-4A §4.4)
oqc2_audit: >=2 status states MUST hold real rows in production (INV-E5) — post-implementation concern
note: lifecycle ENFORCEMENT is a Cap-4 checker concern → see cap4-checker-extension-design file

6. Fit with the existing 8 Core + 3 Candidate set

existing_set:
  core_8:      [contains, references, depends_on, uses, implements, supersedes, contradicts, compatible_with]
  candidate_3: [derived_from, governed_by, published_in]
evidenced_by_placement:
  class: §3.3 EXTENSION  (NOT a Core, NOT a §3.2 Candidate)
  family: relation / Cap-4  (joins references/depends_on/uses/implements/derived_from/governed_by/published_in)
  composition_set_unaffected: [contains, belongs_to, part_of_composite]  # Cap-5 untouched
non_overlap_with_set (semantic carve — enforced by Cap-4, see checker design):
  vs references:   evidenced_by adds attestation/"proves performed"; references = read-only mention
  vs implements:   evidenced_by = proof-of-satisfaction; implements = spec realization
  vs derived_from: evidenced_by = evidentiary; derived_from = creation provenance
  vs governed_by:  evidenced_by = attestation (opposite intent); governed_by = authority/control
  vs iu_entity_binding(binding_kind=evidences): evidenced_by = IU<->IU graph edge;
       binding = IU<->raw_entity reference (NOT a universal_edges row) — boundary preserved (QG3)
vocab_cost: +1 edge_type only (minimized from 6 — WS-1); no Core/Candidate definition changed
candidate_dependency_note: >
  evidenced_by does NOT depend on derived_from/governed_by Candidate ratification.
  The broader WS-1 minimization (constrains->governed_by, lesson_from->derived_from)
  still tracks BP-WS2-2 — NOT resolved here (QG7).

7. Explicit non-execution statement

vocab_amend_executed: false
edge_type_vocab_framework_mutated: false
dot_config_or_directus_mutated: false
code_or_schema_changed: false
sql_executed: none
this_file_is: a logical vocab-entry SPECIFICATION for future command-review
execution_path: separate command-review cycle, GPT/User-authorized — NOT this phase
self_advance: PROHIBITED

Design only. The vocab framework is NOT amended. evidenced_by is approved at design-governance level; it is NOT yet in any vocab and NOT usable until a future command-review executes this specification under explicit GPT/User authorization.

---

Companion files: cap4-checker-extension-design, verification-and-rollback-plan, vocab-cap4-design-report.