lythoskill-project-scribe-weeklylisted

# Project Scribe — Weekly > Distill, don't replay. The core thread matters; the 17 commits that touched it don't. ## Value Boundary Weekly is a **memory offloading mechanism**, not a menu listing. | Direct queries (skip these) | Scribe-weekly must synthesize | |-----------------------------|-------------------------------| | `git log --since="7 days ago"` | The *one* decision that mattered most | | `ls daily/2026-05-*` | Why the planned vs actual divergence happened | | `cat cortex/INDEX.md` | Which emergent threads earned attention | | `bunx @lythos/project-cortex list` | What pattern is hardening into a project trait | If the next agent can find it via `ls daily/`, `git log`, or `cortex index` — don't replicate it. Link to it. **Why this matters**: A future agent reading a weekly cold (no daily access) should get the *compressed representation* of the week's cognitive work — the pattern, not the commits. Without this, every agent must reconstruct the narrative from 6 daily files + 29 commits + 10 ADRs. Weekly offloads that reconstruction cost once, permanently. ## Weekly Prep (like `cortex probe` — gather before you write) **Do NOT start writing from memory.** Run prep first. This is the write-side counterpart to onboarding's read-side: just as onboarding reads daily → verifies git → presents summary, weekly prep gathers all sources → surfaces anomalies → ranks importance. ### Step 1: Gather (deterministic) ```bash # Daily surface — which days had activity? ls dai