project-context-ledgerlisted

# ContextJoin Keep the approved Markdown project handbook current without turning it into a transcript or an unreviewed memory dump. The readable memory lives in `.project-context/views/*.md`; structured records exist to compile, review, synchronize, and protect those views. ## Onboard an existing project When the ledger is initialized in an existing project, actually read the project before writing context: 1. Run `contextjoin setup` with a factual name and short description when setup has not already completed. Never reuse a project ID from another project. Setup reports which Markdown documentation it detected. 2. **If Markdown documentation exists** (README, `docs/`, ARCHITECTURE, CONTRIBUTING, agent instruction files): read those files and distill them into the initial handbook — purpose fact, confirmed architecture decisions, active risks, current focus — one record per independent claim, each citing the source file. The handbook must agree with what the docs actually say, not with assumptions. 3. **If no Markdown documentation exists**: you author the central base for that folder yourself. Explore the manifests, directory structure, entry points, tests, and recent Git state, then record the project purpose, the observed architecture, and the current focus. Those compiled views become the folder's base documentation from that moment on. 4. Record only evidence-backed items. Do not convert code observations into product intent unless a source supports them; the user