Balanced is the ContextLean v0.3.0 product contract: produce a reliable project map and a compact coding discipline that helps agents find owners, limit exploration, preserve constraints, make focused changes, and verify sufficient coverage.
ContextLean no longer promises complete original-bootstrap compatibility. This is intentional product simplification. Accidentally weakening a retained coding safeguard would be a semantic regression; smaller context is not a justification for doing so.
The core keeps map-primary, owner-first and search-first navigation; source-over-map precedence; evidence-driven expansion; no ordinary whole-repository scans or unjustified rereads; relevant-only repository-state checks; preserved architecture; cohesive ownership; focused interfaces; and restrained structural changes directly available.
It retains the complete six-step reuse ladder, focused/readable implementation, no style-only or speculative rewrites, correctness/security/trust/data/accessibility and configuration protection, root-cause fixes, and practical regression checks. Proportional verification chooses sufficient coverage, not mandatory stages. Reuse equivalent passed coverage unless relevant code/test/config/environment changes, failures, unresolved results or project-required repeats justify reruns.
Map maintenance corrects known invalidation or encountered stale information only in the smallest affected map; otherwise leave maps alone. There is no after-every-task cadence, standing reusable-workflow documentation trigger or mandatory qualified Lean Review handoff. Generated guidance needs neither an installed ContextLean plugin nor setup/historical documents. Existing useful project-specific references survive.
- Lean Review owns optional architecture/extraction questions, refactor signals and coupling-specific advice. It remains advisory and read-only unless fixes are requested, with standalone behavior/safety safeguards.
- Authoring documentation owns map editorial standards and project-Skill thresholds, locations, portable sharing, discovery and relocation.
- Bootstrap owns compatible Claude imports, knowledge preservation and safe exclusion validation. Coding guidance stays provider-agnostic. Default setup does not create or synchronize project Skills.
- Measurement is separately requested. Default setup needs no Python helper, baseline capture or measurement report.
All four Skills require a user request. None is an automatic follow-up. No generic runtime reference is required merely to retain retired administration rules.
There is no default per-project transfer/hash ledger, all-historical-facets gate, universal historical safe-removal certificate, mandatory measurement report, recurring workflow discovery, project-Skill creation or fixed eight-category completion report.
Bootstrap still checks actual paths, owners, flows, commands, knowledge preservation, references/imports, exclusions and unauthorized changes. The selected coding kernel must work without loading setup documents. Do not delete old receipts, setup documents or historical evidence as cleanup. Historical test support retains the legacy inventory, fixture and checker for explicit inspection against matching source revisions, outside the packaged Bootstrap Skill and its prerequisites. No replacement per-project facet ledger is introduced.
Balanced retires universal original-bootstrap compatibility, recurring map-check rituals, mandatory project-Skill administration and transfer certification. The dated migration comparison preserves the reviewed dispositions; it is not a setup gate.
Deterministic tests generate representative guidance from the project map input and canonical core. They check core concepts/conditions, fresh files, imports, product preservation, idempotence, commands and frozen evidence. This is test scaffolding for a reviewed project, not a general automated installer or independent live-model bootstrap.
See v0.3.0 verification for measured size, checks and remaining limits. Historical completeness tests no longer gate ordinary setup.