sdlc-ledger

# sdlc-ledger The team's shared coordination log — who claimed what, what's done, what's handed off to whom. It is **not your code history**: it lives on its own git branch (`sdlc-ledger`), checked out as a worktree under `.sdlc/ledger/`, so pulling it never touches your working tree. Each person writes only their own `entries/<login>.jsonl`, so concurrent writers can never conflict; the team view is their union. The scripts live in the loop skill. Resolve their directory once, then call them — the user never types a python path: ```bash LS="${CLAUDE_SKILL_DIR}/../sdlc-loop/scripts" ``` ## Turn it on + set it up (once per repo, then once per teammate's clone) 1. Ensure `.sdlc/config.json` has `"ledger": { "enabled": true }` (off by default — a team surface is opted into explicitly). Add the `lease` block too if you want to tune the claim-lease TTL. 2. **One command creates everything** — the ops branch, your entries file, the `TEAM.md` rollup, and pushes it so the team can see it: ```bash python3 "$LS/sync.py" bootstrap .sdlc ``` Idempotent (safe to re-run). Each teammate runs this once in their own clone to join. The worktree must also be git-ignored so it never lands in a code PR — use the safe helper, which never clobbers or narrows an ignore rule you already set (and can target `.git/info/exclude` instead of the shared `.gitignore` for a local-only adoption): `python3 "${CLAUDE_SKILL_DIR}/../sdlc-setup/scripts/setup.py" ignore . --scope ...