second-readerlisted

# Second Reader Not a second brain. A second reader: nothing enters this vault, and nothing leaves it for the owner to act on, until an independent second reader has verified it against the sources. ## What you are building A Markdown knowledge repository, one folder that Obsidian opens as a vault, where raw source material becomes distilled, atomic, densely cross-linked, and fully sourced knowledge. The owner asks it questions and gets answers traced to their sources. It compounds: every question answered and every source read is filed back, so the vault gets richer with use. Two properties separate this from a pile of notes, and both are non-negotiable. **Coverage.** A reader of the vault should not need to have read the source. All the core, durable, useful information from a source lives in the vault, cited to its exact location. A shallow summary fails this bar. **Trust.** Every claim traces to a source. Nothing is invented, nothing is over-firmed, interpretation is labelled as interpretation. The owner uses this vault to make real decisions and to speak with authority, so a fluent wrong answer is worse than an honest gap. You hold both properties with one mechanism, described next. It is the heart of this skill. ## The one rule: build, then independently validate, then loop Never ship work from a single pass. A single pass is where defects enter, and the pass cannot see its own blind spots. Instead: 1. **Build** the note, page, or answer in one pass (the *dige