Ho System, Actually Build the software. Develop the judgment.

compressed chain

definition
depth 3/3 − deeper + surface

The chain of up-front framing documents when a seasoned practitioner has deliberately merged or skipped some of its layers.

The state of a Kamae chain whose layers have been combined or skipped by a ri-stage practitioner. Legitimate only as the result of a declared compression (see next); a chain compressed silently is drift.

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.