# Requirements: v1.68 Persistent Wiki-Style Knowledge Compilation

## Milestone Goal

Move beyond retrieval-only `L2` helper views by compiling repeated reading,
discussion, and route-comparison outcomes into one durable linked research-brain
surface, while keeping authoritative `L2` writeback behind existing `L4`
promotion gates.

## Completed Requirements

### Compilation Contract

- [x] `REQ-KCOMP-01`: the repository defines one explicit compiled-knowledge
  contract that can summarize what knowledge was added, updated, contradicted,
  or still provisional, rather than only dumping raw graph indexes and reports.
- [x] `REQ-KCOMP-02`: the compilation contract stays non-authoritative: it may
  include canonical, staged, and provisional research surfaces, but it must not
  bypass `L4` validation and canonical promotion gates.

### Runtime And Operator Surface

- [x] `REQ-KCOMP-03`: operators can materialize one durable compiled-knowledge
  report from the current workspace through a production CLI/service path.
- [x] `REQ-KCOMP-04`: the compiled report includes linked navigation plus
  explicit update/change summaries so the operator can see what new knowledge
  was added or changed since the last compilation.

### Verification

- [x] `REQ-VERIFY-01`: the milestone includes targeted regression coverage and
  one bounded acceptance path for the compiled-knowledge surface before later
  phases extend the `L1/L2` stack.

### L1 Three-Layer Vault

- [x] `REQ-L1VAULT-01`: the repository materializes one explicit `L1`
  raw/wiki/output vault under each topic intake root without duplicating
  authoritative source inputs into another writable truth surface.
- [x] `REQ-L1VAULT-02`: the wiki layer stays Obsidian-compatible and
  inspectable, with frontmatter, lowercase filenames, wikilinks, and one
  schema/governance page that defines page types, ingestion rules, and
  cross-link conventions.
- [x] `REQ-L1VAULT-03`: the output layer emits one derived digest plus one
  explicit flowback ledger that records what valuable output was synced back
  into the wiki layer.
- [x] `REQ-L1VAULT-04`: existing runtime compatibility artifacts
  (`research_question.contract`, `control_note`, `operator_console`) remain
  preserved and linked inside the new `L1` vault instead of being displaced by
  it.

### L2 Statement Compilation Pilot

- [x] `REQ-M2F-01`: the milestone pilots a bounded statement-compilation lane
  that turns informal theoretical-physics content into structured declaration
  skeletons before proof repair.
- [x] `REQ-M2F-02`: the pilot keeps verifier-guided repair and downstream
  target selection explicit without locking AITP to one proof assistant.

## Requirement Outcomes

- `REQ-KCOMP-01`: validated exactly as written through the new
  compiled-knowledge contract and report artifact family.
- `REQ-KCOMP-02`: validated exactly as written through explicit canonical /
  staging authority markers.
- `REQ-KCOMP-03`: validated exactly as written through the production
  `compile-l2-knowledge-report` CLI/service path.
- `REQ-KCOMP-04`: validated exactly as written through linked change summaries
  and previous-snapshot comparisons.
- `REQ-VERIFY-01`: validated through the dedicated compiled-knowledge
  acceptance lane plus the bounded regression gate.
- `REQ-L1VAULT-01`: validated through the new topic-scoped `L1` vault rooted at
  `intake/topics/<topic_slug>/vault/`.
- `REQ-L1VAULT-02`: validated through Obsidian-compatible wiki pages plus the
  local vault schema page.
- `REQ-L1VAULT-03`: validated through the derived output digest and explicit
  `flowback.jsonl` receipts.
- `REQ-L1VAULT-04`: validated through linked compatibility refs to
  `research_question.contract`, `control_note`, and `operator_console`.
- `REQ-M2F-01`: validated through candidate-scoped statement-compilation
  packets and declaration skeletons before proof repair.
- `REQ-M2F-02`: validated through proof-repair plans and downstream targets
  that explicitly name `lean4` and `symbolic_checker` instead of locking the
  packet to one proof assistant.

## Traceability

| Requirement | Phase | Status |
|-------------|-------|--------|
| REQ-KCOMP-01 | Phase 138 | Complete |
| REQ-KCOMP-02 | Phase 138 | Complete |
| REQ-KCOMP-03 | Phase 139 | Complete |
| REQ-KCOMP-04 | Phase 139 | Complete |
| REQ-VERIFY-01 | Phase 140 | Complete |
| REQ-L1VAULT-01 | Phase 141 | Complete |
| REQ-L1VAULT-02 | Phase 141 | Complete |
| REQ-L1VAULT-03 | Phase 141 | Complete |
| REQ-L1VAULT-04 | Phase 141 | Complete |
| REQ-M2F-01 | Phase 142 | Complete |
| REQ-M2F-02 | Phase 142 | Complete |
