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

## Result

`v1.68` is complete.

## Overview

`v1.68` moved AITP beyond retrieval-only helper views into one bounded durable
research-brain surface. It closed the compiled-knowledge contract, added
operator-visible acceptance, refactored `L1` into a raw/wiki/output vault with
explicit flowback, and piloted a pre-Lean statement-compilation stage before
proof repair.

**Phases:** 138-142
**Total Plans:** 5
**Total Tasks:** 10
**Shipped:** 2026-04-12

## Phase Details

### Phase 138: Knowledge Compilation Contract

**Goal:** Lock one explicit compiled-knowledge contract that extends the
current `L2` compiler helpers with added/updated/provisional/contradiction
semantics while preserving the existing `L4` promotion boundary.

**Plans:** 1 plan

Plans:

- [x] `138-01`: compiled-knowledge contract and production command

**Outcome:**

- landed `compile-l2-knowledge-report`
- wrote `workspace_knowledge_report.json|md`
- made canonical versus staging authority explicit instead of flattening both
  into one fake truth surface

### Phase 139: Compiled Knowledge Surface And Acceptance

**Goal:** Make the compiled-knowledge surface operator-visible and
acceptance-backed through one dedicated bounded runtime script plus aligned L2
compiler docs.

**Plans:** 1 plan

Plans:

- [x] `139-01`: compiled-knowledge surface and isolated acceptance

**Outcome:**

- landed `run_l2_knowledge_report_acceptance.py`
- verified previous-snapshot detection and contradiction-watch rows on an
  isolated temp kernel root
- aligned runtime docs and tests to the new acceptance lane

### Phase 140: Closure And Regression Audit

**Goal:** Run one bounded regression gate over the compiled-knowledge surface
before later `L1` and `L2` follow-on work.

**Plans:** 1 plan

Plans:

- [x] `140-01`: final targeted regression gate for compiled knowledge

**Outcome:**

- re-ran the targeted compiled-knowledge test slices
- re-ran the isolated acceptance script
- kept the milestone open and honest instead of pretending this was milestone
  closure

### Phase 141: Adopt LLM-Wiki-Skill Three-Layer Vault And Flowback Into L1 Knowledge Compilation

**Goal:** Refactor `L1` knowledge compilation to adopt the three-layer
raw/wiki/output vault pattern with explicit flowback and schema governance.

**Plans:** 1 plan

Plans:

- [x] `141-01`: materialize the `L1` raw/wiki/output vault and flowback ledger

**Outcome:**

- landed `knowledge_hub/l1_vault_support.py`
- materialized `intake/topics/<topic_slug>/vault/raw|wiki|output`
- preserved `research_question.contract`, `control_note`, and
  `operator_console` as linked compatibility surfaces

### Phase 142: Pilot M2F Statement-Compilation Pattern For L2 Automated Formalization

**Goal:** Pilot the two-stage M2F-style pattern by compiling bounded informal
theory statements into declaration skeletons before proof repair.

**Plans:** 1 plan

Plans:

- [x] `142-01`: statement-compilation packets, proof-repair plans, runtime
  exposure, and downstream Lean-bridge consumption

**Outcome:**

- landed `aitp statement-compilation`
- wrote candidate-scoped `statement_compilation.json|md` and
  `proof_repair_plan.json|md`
- made `prepare_lean_bridge()` consume the compiled statement packet instead of
  hiding Stage 1 inside the Lean packet itself

## Milestone Summary

**Key Accomplishments:**

- one explicit compiled-knowledge report now records additions, updates,
  contradictions, and provisional rows
- one bounded compiled-knowledge acceptance lane now exists
- one persistent `L1` raw/wiki/output vault now exists on the topic-shell path
- one explicit statement-compilation surface now separates declaration
  skeleton generation from proof repair
- one downstream Lean bridge now consumes the upstream statement-compilation
  packet explicitly

**Issues Resolved:**

- closed the gap where `L2` only had raw graph/index helper views
- closed the gap where `L1` had no explicit persistent wiki-style compiled
  vault
- closed the gap where declaration skeletons were implicit inside the Lean
  bridge instead of being a first-class artifact

**Issues Deferred:**

- Layer 0 source discovery before registration
- broader graph-growth and multi-user validation
- whole-topic or whole-paper automated formalization

**Technical Debt / Honest Gaps:**

- the statement-compilation pilot is bounded and intentionally not a
  whole-paper formalization engine
- DeepXiv or equivalent discovery integration still remains external to the
  current shipped milestone

---

For current planning state after `v1.68`, continue from the next active
milestone and fresh requirements definition.
