# Phase 185.2 Context: Global L2 Reuse Context And Capability Plane

## Why this phase exists

The repository already has usable but still fragmented pieces of reusable
knowledge and execution visibility:

- canonical `L2`,
- compiled `L2`,
- staging,
- `consult-l2`,
- topic skill projections,
- backend bridges,
- execution-task contracts,
- and runtime executor hints.

But `L3` still does not consume them through one bounded reusable read path.

That leaves two real gaps:

1. `L3` idea and plan work still rely too heavily on scattered runtime memory,
2. `L3` still lacks one explicit capability plane for tools, servers,
   environments, and workflows before it writes a concrete execution plan.

## Bounded goal

Turn the existing reusable-memory and execution-resource pieces into one honest
progressive planning stack:

- global authoritative `L2`,
- global Obsidian-friendly Markdown mirror,
- global runtime capability plane,
- topic-scoped `idea_reuse_context`,
- topic-scoped `plan_reuse_context`,
- topic-scoped `execution_resource_context`,
- and explicit resource refs in `L3` planning surfaces.

## Explicit scope

In scope:

- global `L2` reuse context design
- topic-linked evidence fields on reusable units
- capability cards for tools, servers, environments, and workflows
- natural-language capability declaration write-in path
- progressive `L3` read surfaces
- explicit plan refs for concrete resources

Out of scope:

- full authoritative `L4 -> L2` promotion closure
- full automatic capability discovery across all machines
- replacing canonical truth with compiled markdown
- redesigning all canonical unit families in one step
