Elnor Repo Reader

# E3/E4 Charter — DOC82 Knowledge + Source/Evidence — Opening Brief

**Family member:** DOC82 (member **3 of 8** — the Canonical Knowledge + Source/Evidence plane; the **truth plane**). Memory Control Plane family (ADQ-210/220).
**Drafted as:** the **E3 + E4 lockstep pair** (plan §12.3). **E3 = Knowledge** (the Assertion family + lifecycle/state machine + warrant ladder + bitemporal axes). **E4 = Source / Evidence** (SourceEnvelope, EvidenceRecord/EvidenceSupportEdge, corpus hierarchy, parse-quality bounds). They are drafted together because `EvidenceSupportEdge` depends on the source-span / `SourceEnvelope` contracts (plan §12.3).
**Status:** scaffolding — **NOT yet approved; NOT drafted.** Awaiting architect charter-scope approval (high-risk slice) **and** resolution of two hard pre-conditions (§0 below).
**Predecessors:** E0 (DOC80 core) RATIFIED 2026-06-01; E1/E2 (DOC81 Scope & Policy) RATIFIED 2026-06-08. DOC82 binds to both by reference.

---

## §0. TWO HARD PRE-CONDITIONS — must resolve BEFORE the draft (this is the charter's distinguishing feature)

Unlike E0/E1/E2, the DOC82 charter **cannot be drafted blind** — the Stage-6 input index pins two architectural decisions as "must be finalized/done before drafting":

1. **ADQ-202 — Corpus hierarchy (→ E4; HARD COMMITMENT, "not infinite defer").** The internal deep-ingestion structures that sit BEHIND user-visible Libraries must be fully resolved at this charter. It gates ADQ-402 (DOC73 corpus-source-bindings) and ADQ-404. *Open question for the charter:* the exact hierarchy — Library (user-visible) → Corpus/SourceCollection (internal) → Source → Artifact/Segment — and which layers DOC82 owns vs consumes from DOC25/DOC87.
2. **ADQ-219 — DOC73 ConsolidatedUnderstanding (CU) reconciliation (→ E3/E4; "must be done before drafting").** DOC73 owns CU *semantics*; DOC82 *consumes* it — either **directly** or, if the reconciliation surfaces divergence, via the **`SourceBoundSynthesisAdapter`** wrapper (a mapping table, not a redefinition). The charter must perform the DOC73 reconciliation and **finalize the direct-consume vs adapter path before drafting**. Convergence obligation = **OPA-035**.

**Architect decision needed (see the packet presentation):** how to discharge these two — a focused pre-charter analysis/red-team round (recommended: I prepare the corpus-hierarchy options + the CU reconciliation analysis for your decision, then draft), vs folding the resolution into the charter draft itself. Everything below assumes they're resolved first.

---

## §1. What DOC82 owns (the truth plane — from `DOC80_Owner_Map.md`)

**The Assertion family + full lifecycle/state machine (B9 — DOC82 owns the whole machine; DOC72 stores graph payload; EC executes writes):**
`Assertion` · `AssertionVariant` · `AssertionCandidate` · **`AssertionCandidateEmission`** (the named E3↔E5 handoff: schema_owner DOC82, produced-by DOC83 — DR-008) · `AssertionResolution` · `AssertionDedupeOutcome` (orthogonal to disposition; ABC §7.8) · `AssertionMergeOperation/Reconciliation/Split/Unmerge` (reversible, auditable) · `AssertionRelationEdge` (schema only; storage DOC72; EC executes traversal scope checks per the DOC81 §8 / ADQ-315 policy) · `AssertionIdentitySignature` · `AssertionLifecycleState` (the full state machine) · `AssertionTemporalProfile` (the temporal classes).

**The warrant ladder:** `EpistemicKind` / `UseWarrant` / `EffectiveWarrant` (EC executes warrant evaluation) — plus the Stage-6-input schemas to slot: `WarrantEvaluationResult`, `WarrantConsequenceRegistry`, `DomainProfileWarrantPolicy` (Skeletal §576).

**Evidence + source:** `EvidenceRecord` · `EvidenceSupportEdge` (support_relation enum; ABC §4.2) · `SourceEnvelope` (carries source ref/kind/authority/visibility/parse-quality/injection-risk/materialization) · `SourceRegionRef`/`SourceSegmentRef` · `SourceAuthorityScope`/`SourceAuthorityClass` · `ExtractionRouteContext` (route is provenance, not identity; ABC §1.2) · `CascadingSourceInvalidation` **source-side payload** (the envelope is DOC81's; DOC82 owns the payload).

**Bitemporal (Skeletal §10/§11):** `valid_time` (when the proposition holds in the world) + `transaction_time` (when the system recorded it) on the Assertion family — enables time-window warrant degradation, litigation "what did I know about X as of date D" queries, and audit integrity.

**Lineage + adapters:** `VersionedClaim → AssertionVariant` lineage table (DOC82 owns the mapping; DOC73 retains VersionedClaim — DR-003 resolved) · `SourceBoundSynthesisAdapter` (conditional wrapper, ADQ-219) · `KnowledgeProjection` + `KnowledgeProjectionInvalidationPolicy` (under SemanticProjectionContract) · `LibrarySourceBindingConsumptionContract`.

## §2. What DOC82 does NOT own (consumes by reference)
- **ConsolidatedUnderstanding semantics** → **DOC73** (ADQ-219; consume direct or via adapter).
- **SourceArtifact / ArtifactSegment / SourceParseQualitySidecar / file-materialization** → **DOC25** (DOC82 consumes via `SourceEnvelope` segment refs; ADQ-303 thresholds DAMS/DOC25; ADQ-401 materialization).
- **Graph payload storage + six-dimensional knowledge + Entity** → **DOC72** (consume via graph-payload refs; `ExternalDependencyRecord` required).
- **Policy/scope gates** → **DOC81** (`EffectiveMemoryPolicy` meet, `ScopeResolutionResult`, `PolicyStamp`, `disclosure_class`, the `CascadingSourceInvalidation` envelope, `AssertionRelationEdge` traversal-scope-check policy §8).
- **Registries + proof spine** → **DOC80 core** (ReasonCode, DomainProfile, ContextPacketProof, MemoryFlowCertificate, MemoryCoordinationTrace, memory-object taxonomy, compute-budget).
- **Library-as-container / CorpusIndex / SourceCollection** → DOC87 (container) / DOC25 (bindings).
- **Durable writes + warrant execution + resolution execution** → **EC**.

## §3. Draft targets (provisional — finalized after the §0 pre-conditions resolve)
1. `Assertion` + bitemporal axes + `AssertionVariant` (scoped/conditional). 2. `AssertionCandidate` + `AssertionCandidateEmission` (the E3↔E5 handoff contract). 3. `AssertionResolution` + `AssertionDedupeOutcome` (the canonical-resolution pair). 4. The full `AssertionLifecycleState` state machine (candidate → variant → resolution → promotion → dedupe; + merge/reconcile/split/unmerge). 5. `AssertionRelationEdge` schema (consuming DOC81's §8 traversal policy). 6. `AssertionIdentitySignature` + dedupe. 7. The **warrant ladder** (`EpistemicKind`/`UseWarrant`/`EffectiveWarrant` + `WarrantEvaluationResult`/`WarrantConsequenceRegistry`/`DomainProfileWarrantPolicy`). 8. The **`(temporal_class, epistemic_kind)` validity table** (ADQ-314 — invalid combos flagged at lifecycle transition). 9. `SourceEnvelope` + `SourceRegionRef`/`SourceSegmentRef` + `SourceAuthorityScope`/`Class`. 10. `EvidenceRecord` + `EvidenceSupportEdge` (support_relation enum). 11. The **corpus hierarchy** (ADQ-202 — Library→Corpus→Source→Artifact; owned vs consumed layers). 12. `ExtractionRouteContext` (provenance not identity). 13. `CascadingSourceInvalidation` source-side payload + **polarity-aware warrant recompute / re-proof** (the DOC82 side of DOC81's monotonicity law — supporting vs contrary source removal). 14. The CU consumption contract + `SourceBoundSynthesisAdapter` (ADQ-219 path). 15. `VersionedClaim → AssertionVariant` lineage table (§10.8 lints). 16. `KnowledgeProjection` + invalidation policy. 17. The 9 OPA Bucket-A obligations (filing-unit/version, court-disposition, ruling-disposition, observation-lifecycle, promoted-claim memory-kind, not-evidence guardrail, SourceArtifact). 18. The DOC82→{DOC83,DOC84,DOC85,DOC87} export contracts. 19. Cross-cutting invariants (warrant monotonicity, not-evidence guardrail, one-owner placement vs ABC §2.1 semantics). 20. Open-items / architect-review flags (≤5).

## §4. Seniority + placement discipline (load-bearing — flag for the drafter)
- **ABC R0.2 is senior to the Concept Model (DR-001) for SEMANTICS** (identity / relation / warrant / disposition / merge / dedupe behavior). The Concept Model §17.3 11-value disposition enum stays **retired** (G-2); ABC §7.8's 7-value `AssertionCandidateDisposition` + `AssertionDedupeOutcome` are defined at DOC82 only.
- **D-SEED-2 overrides ABC §2.1's PLACEMENT.** ABC §2.1 assigns Assertion/Variant to DOC72 and Evidence to the DOC73/DAMS seam; the family **re-homes** them to DOC82. The drafter MUST treat ABC §2.1 as authoritative for *semantics*, NOT *placement* — `DOC80_Owner_Map.md` is canonical for placement.

## §5. The lockstep (plan §12.3) + exit criteria
**E3 declares the knowledge objects** (Assertion family, warrant, lifecycle, bitemporal); **E4 declares + validates the source/evidence backing** (SourceEnvelope, EvidenceSupportEdge, corpus hierarchy, parse-quality bounds) — together because evidence support depends on the source-span contracts. **Exit:** all 20 targets land; the two pre-conditions (§0) are resolved with their decisions recorded; ABC §7.8 enums defined DOC82-only; bitemporal axes present; warrant monotonicity wired to DOC81's law; all 9 OPA rows + DR-002/DR-008 land; no-phantom discipline (every contract traces to ABC R0.2 / Owner Map / Skeletal / ADQ / OPA / E0 / DOC81 §, else `OPEN_FOR_ARCHITECT_REVIEW` ≤ 5); one-owner held; no E0/DOC81 re-declaration.

**Charter status: NOT YET APPROVED — pending architect charter-scope sign-off + the §0 pre-condition decisions.**