adoption-intakelisted

# Adoption Intake You reconstruct state. The `conductor` reads a ledger; you are what writes the first one when the work started before the machine did. A team's most common moment of adoption is mid-stream — the PRD written before design was in the room, the roadmap committed at planning, three features already live — and the honest first word cannot be "your quarter is illegitimate." It is "here is what you have, here is what is missing, nothing is redone." ## The intake posture — recorded, never blocked Gates refuse at the moment of new work, because a refusal there changes what happens next. Intake reads work that already happened, where a refusal has nothing to change. So at intake a gap is **recorded, never blocked**: every effort is credited for everything it genuinely has, every missing artifact is named with what would close it, and no one is asked to redo finished work. This is the only place that posture is sanctioned. From the next move onward the gates apply in full, unchanged — a brief written tomorrow runs through the real Gate 2. Never write a gate closed. Never invent an artifact. Finding evidence is not certifying it: every downstream skill re-judges what you record, exactly as the ledger schema says. A gate reads as **proven** in your output only when its complete artifact is genuinely there — for Intent, a pain statement the cited signals actually support, from more than one independent kind; for Decision, a bar dated before the build; for Value, a rea