# Phase 999.2: L2 Knowledge Compiler And Hygiene (BACKLOG) - Context

**Captured:** 2026-04-04
**Status:** Backlog
**Mode:** Future `L2` improvement inspired by LLM-compiled knowledge-base
workflows (Obsidian/wiki style) without disturbing the current v1.4 execution
sequence

<domain>
## Intent

Improve `L2` so it behaves less like a passive storage layer and more like a
compiled, self-auditing knowledge surface.

This is not a near-term runtime-routing task.
It is a later-layer improvement for how mature topic outputs become durable,
queryable, and internally coherent.

</domain>

<candidate_learnings>
## Candidate Learnings To Revisit Later

- keep a clear separation between raw intake and compiled trusted knowledge
- support incremental compilation from raw/topic artifacts into connected
  Markdown/wiki-style `L2` objects
- generate and maintain backlinks, concept pages, and cross-topic link surfaces
- add `L2` hygiene/health-check passes for:
  - stale summaries
  - missing links
  - contradictory notes
  - missing concept bridge pages
- isolate agent-generated scratch or provisional writeback from trusted `L2`
  until review passes, to reduce pollution
- consider future "query-scoped temporary compiled wiki" behavior as a later
  extension rather than the default storage model

</candidate_learnings>

<fit_with_aitp>
## Fit With AITP

Potentially valuable for:

- `L2` canonical note quality
- concept-network density
- trust-preserving knowledge maintenance
- better long-horizon reuse across topics

Must still preserve:

- governed promotion into `L2`
- the difference between trusted `L2` and exploratory `L3`
- protocol-first truth boundaries instead of free-form note pollution

</fit_with_aitp>

<why_not_now>
## Why This Is Deferred

- current v1.4 priority is still runtime simplification, checkpoint hardening,
  projection-aware routing, and topic-family reuse
- changing `L2` too early would mix storage innovation with unfinished runtime
  autonomy boundaries
- this idea should build on a stable post-v1.4 base

</why_not_now>

<source_note>
## Source Note

Reference inspiration:

- <https://a2a-mcp.org/blog/andrej-karpathy-llm-knowledge-bases-obsidian-wiki-zh>

Use the ideas, not the product assumptions.
AITP should borrow the compiled-knowledge and hygiene-loop lessons without
collapsing `L2` into a generic personal wiki.

</source_note>
