Elnor Repo Reader

ELNOR REPO READER TEXT MIRROR
Original path: Memory Rebuild Docs/Flattening/Aspirational Completion/Aspirational_Completion_Register.md
Source repo: /Users/OpenClaw1/Elnor/Elnor Specs
Git branch: main
Git commit: dbaa25962edc11ab30e8d4ca1715f9ae5bf77331
Generated: 2026-06-09T01:23:58.539Z

---

# DOC80 Memory Rebuild — Aspirational Completion Register (Stage 4)

**Repository:** github.com/wbrody/Elnor-Specs — branch `main`
**Generated:** 2026-05-25 (Stage 4)
**Rows:** 5

One AspirationalCapabilityCompletionRecord (plan §7) per aspirational-valuable capability identified in Stage 3.

Per architect direction (Will, 2026-05-25), proposal-named files are NOT auto-demoted. The 5 below were flagged genuinely preliminary by Codex review and confirmed by Will; they are preserved as completion obligations.

Per plan §7: `minimum_completion_for_v5` is an architect decision unless a pre-approved target rule covers it. Most rows below require architect adjudication; queue items ADQ-401 through ADQ-404 carry the decisions.

## Rows

| completion_id | capability_ref | value_statement | target_landing | minimum_completion_for_v5 | owner_doc_target | op_a_candidate_required | decision_ref |
|---|---|---|---|---|---|---|---|
| AC-001 | cap-doc25-file-materialization-and-provider-profiles-proposal-v1 | DOC25 file materialization + provider profiles + remote access — load-bearing for DOC25 parse/materialization crown-jewel family; defines materialization_state semantics, provider profile registry, and remote-access policy seams. | include_as_future_completion_obligation | schema_plus_owner_boundary | DOC25 | yes | ADQ-401 |
| AC-002 | cap-doc73-corpus-source-bindings-proposal-v1 | DOC73 corpus source bindings — concrete source for the plan §6.4 Library/corpus deep-ingestion crown-jewel family; defines binding contract between TopicCollectionDirective + Library/corpus and the canonical AssertionCandidate pipeline. | include_as_future_completion_obligation | schema_plus_lints_and_fixtures | DOC73 / Memory Control Plane | yes | ADQ-202, ADQ-402 |
| AC-003 | cap-doc73-proposal-section-6-4-mechanism-4-rollup-v1 | DOC73 RecentActivityRollup mechanism (§6.4 mechanism 4) — load-bearing for plan §6.4 RecentActivityRollup crown-jewel family. Orientation-only seam; must not become evidence / warrant / pseudo-truth. | include_in_doc80_v5_core | schema_plus_lints_and_fixtures | DOC73 (generation) + DOC80 Memory Control Plane core (consumption, invariant, lints/fixtures) | yes | ADQ-405 |
| AC-004 | cap-memory-intake-and-at-use-disciplines-proposal-v1 | Cross-doc memory intake + at-use disciplines proposal — load-bearing for source-bound discipline at intake and at use; bridges DOC25 (source authority), DOC73 (CU/source-bound), and Memory Control Plane (memory use contract). | include_as_future_completion_obligation | schema_plus_lints_and_fixtures | Memory Control Plane (DOC80 core) + DOC25 + DOC73 | yes | ADQ-403 |
| AC-005 | cap-ec-core-addendum-a-intake-routing-for-corpus-bindings-propos | EC Core intake routing for corpus source bindings — defines EC role in routing extraction outputs through corpus bindings; load-bearing for PropA/EC policy + Library/corpus crown-jewel families. | include_as_future_completion_obligation | schema_plus_owner_boundary | EC Core + Memory Control Plane | yes | ADQ-202, ADQ-404 |

## Missing to complete (per row)

- **AC-001**: Stage 5 confirmation that DOC25 owns materialization_state + provider profiles; Stage 6 charter for E4 (Source / Evidence / parse-quality gate) names the contract; Stage 8 patch resolves provider profile registry
- **AC-002**: Stage 5 confirms binding scope; Stage 6 E1/E2 (Scope/Policy lockstep) + E3/E4 (Knowledge/Source lockstep) include binding fixtures; Stage 8 fixes Library/Corpus duality (ADQ-202)
- **AC-003**: Stage 6 E6 charter names the consumption contract, the can_orient_only invariant, delivery constraints, and the lint/fixture proving orientation-only behavior (per ADQ-405 may/may-not list). ABC §4.4 already mandates can_orient_only enforcement; the lint/fixture proves it.
- **AC-004**: Stage 5 confirms scope; Stage 6 E0 (cross-cutting) + E3/E4 absorb the disciplines as fixtures; OP-A row required
- **AC-005**: Stage 5 confirms EC vs DOC73 routing scope; Stage 6 E1/E2 (Scope/Policy lockstep) names EC's contract; ADQ-202 (Corpus hierarchy) must resolve first