synthesis-backloglisted

# Synthesis Backlog ## Why this exists Osmani's loop-engineering rule: *"the model forgets everything between runs so the memory has to be on disk and not in the context. The agent forgets, the repo doesn't."* Before this skill, the thread of *"what's processed but not yet synthesized"* lived only in the conversation and reset every session — so the user had to manually re-ask "go through today's files." This skill makes that state a **file**: `$VAULT_DIR/_Synthesis Backlog.md`. It is the loop's spine; everything else (triage, the maker/checker pass) rides on it. This is the discovery/triage half of the loop. The other pieces: - **readwise-deep-read** — ingests + highlights (the *maker* for pipeline output); logs each doc here. - **vault-hygiene-checker** — verifies synthesis quality (the *checker*); run for link/dup/orphan checks. ## The backlog file A normal Obsidian markdown table (the user reads and edits it) at vault root (NOT under `Resources/`, so it isn't published). Hidden `<!-- BACKLOG:ACTIVE:START/END -->` markers make programmatic append/update robust without disturbing the prose. Columns: **Date · Title · doc_id · Type · Atoms · MOC · Read · Notes** States: `pending` · `done` · `skip` · `—` - **Atoms** — did this doc spawn permanent note(s)? - **MOC** — is it wired into a MOC? - **Read** — has the user actually read/synthesized it? (the comprehension-debt guard: `read: no` = processed-but-unread) ## Tool: `backlog.py` ```bash # log a processed doc (idempo