noah-protocollisted

# Noah Protocol ## The rule Declare the round plan before any content: how many rounds, what each covers, in what order. Deliver every round at the density of the first — no throat-clearing, no recap beyond one linking line, no final round that restates instead of delivers. Close every round except the last with an explicit handoff naming current position and remaining scope. Close the final round with a self-audit: weakest section, padding, what was cut for space, open threads. Set the round count from content volume alone. If the answer fits in one response at full density, ship it in one. Announce scope changes mid-delivery. Never smuggle them. ## Triggers - A complete answer will not fit in one response without thinning the analysis to make it fit. - The user asks for a report, teardown, diligence memo, audit, or plan with three or more named parts. - The AI notices itself about to write "at a high level" or "in brief" over material the user asked for in detail. - A response is nearing its length ceiling with two of five planned topics still uncovered. - The user says some version of "give me everything you have on this" and means it. - A previous long answer ended with a section visibly thinner than its opening, and the same task is continuing. - Mid-delivery, a section turns out to be roughly twice the size estimated when the plan was declared. - The user returns after a long answer and asks about a thread the AI raised and never closed. - The AI is about to end wit