declared compression
procedureDeliberately merging or skipping framing layers, but only when you write down what you combined and why, where the next session will see it.
The ri-stage move of combining or skipping Kamae chain layers, legitimate only when declared in writing where the next session will read it—a note naming what was combined and why—as opposed to silent elision. The declaration is what keeps the compressed chain accountable. Canonical instance: sageframe-mcp ho-00; this framework's own ho overview runs on one.
When to Do What. ### For a Brand-New Project
Write all four framing documents in order. Don't skip steps. The seed might take an hour or two—but the precedential thinking that feeds it may have taken days, weeks, or longer. The System Design might take an hour. The README might take 30 minutes. The Ho Overview might take an hour. Total investment in the documents themselves: 3–5 hours before writing any hos.
The seed's time budget is different from the other documents because it draws on upstream work. The precedential thinking—researching the landscape, trying existing tools, talking to people who have the problem—may happen over days or weeks before you sit down to write the seed. The writing itself captures what you've already been thinking. The other three documents are produced in a more concentrated burst, each building on the last.
This is not wasted time. It's the cheapest place to discover that your scope is wrong, your architecture doesn't work, or your project needs to be split into two projects. Fixing these problems in the framing phase costs hours. Fixing them in Ho 6 costs weeks.