Halloween DealsAmazon USHalloween week deals: useful picks before month-endAmazon US: current deals, useful picks and tech finds.Check DealsSlow PC?RecommendedPC slow today? Run a repair scan before it gets worseResolve common Windows issues and optimize system performance.Scan NowHalloween DealsAmazon USOctober picks are moving - compare before checkoutAmazon US: current deals, useful picks and tech finds.See Picks×
FREEDOM251

Freedom251 › Blog › build planning

Our scoping tool refuses in 4 of the 7 states it can be in, and that ratio is not a tuning choice

By Freedom251 Team · · 4 min read

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

A scope gate that refuses in four of its seven states is doing what it was designed to do. In the WhittleOS design described in its guide, What to build first — and the case where you should not be asking yet, a build scope is returned only when the latest idea verdict is BUILD, VALIDATE, or PILOT_FIRST. For HOLD, KILL, UNKNOWN, and an idea with no prior run, the scope stays empty and the output points to validation instead.

The seven states and what each one returns

The gate reads the latest idea verdict and maps each possible verdict, plus the case where no prior run exists, to a decision. Three states permit a scope. Four refuse one.

As an Amazon Associate I earn from qualifying purchases.

Gate state Result
BUILD Scope returned
VALIDATE Scope returned
PILOT_FIRST Scope returned
HOLD Refused; scope empty
KILL Refused; scope empty
UNKNOWN Refused; scope empty
No prior run Refused; scope empty

Two of the refusals are easy to misread. HOLD is an inconclusive result, not a rejection, yet it refuses just as firmly as KILL. The no-prior-run state covers an idea that has never been checked, which means the gate does not treat “never checked” as a neutral starting point.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Why the ratio is structural rather than tunable

The four-of-seven split follows from two things: the mapping itself, and a fail-closed default. Anything not positively treated as validated is treated as unvalidated. The gate does not ask whether an idea looks good enough to scope. It asks whether a validated verdict exists. Moving a threshold would not change that, because the refusal comes from the default, not from a cutoff.

When the gate refuses, the guide’s instruction is to leave the scope empty and write a short paragraph explaining why. The guide’s wording is:

“The instruction is to leave the scope empty and write a paragraph explaining that we do not build a plan for an unvalidated idea, pointing at async validation instead.”

The refusal does not produce a smaller scope with a caveat attached. A reduced plan for an unvalidated idea would still be a plan, and a plan is exactly what the gate is built to withhold.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

A scope is not a verdict

The scope projection is separate from the idea verdict, and it does not re-decide the idea. When it runs without a validated verdict, it reports UNKNOWN as the verdict, a placeholder score of 50, and MEDIUM confidence. The 50 is explicitly a placeholder, not a measured score. The projection structures work that comes after validation; it does not manufacture evidence of demand.

Boris Binyaminov states the principle directly in the guide:

“A scope is not a verdict, and a tool that let a scoping pass raise an idea’s score would be laundering enthusiasm into evidence.”

The six enforced scope fields

When a scope is returned, six fields are enforced:

  • mvp_goal: what v0.1 demonstrates, and the success criterion for that demonstration.
  • must_have_features: the minimum feature set. Each feature must name the job it serves, and the parser checks for this.
  • non_goals: what is deliberately excluded from the build.
  • user_flow: the end-to-end happy path.
  • tickets: ordered, implementation-ready work items.
  • stop_loss: the condition under which building stops and the work returns to validation.

The guide also requests data_model and acceptance_criteria, but neither is enforced, so the contract does not reject a scope that lacks them.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Where the contract is looser than its wording

Two checks show the gap between what the contract asks for and what the parser actually guarantees.

  • Non-goals. The contract asks for more than one non-goal, but the invariant rejects only an empty list. A scope with exactly one non-goal passes. The implementation should not be described as enforcing multiple non-goals. If your own gate needs that guarantee, add an explicit minimum-count check.
  • Build window. The parser accepts build windows from one to four weeks. A window outside that range is not accepted.

Applying the same logic to your own idea

  1. Find your latest idea verdict. If you have never run a check, treat the idea as unvalidated and start with validation rather than a build plan.
  2. If the verdict is HOLD, KILL, or UNKNOWN, do not ask for a build scope. Run the validation that would produce a clearer verdict first.
  3. If the verdict is BUILD, VALIDATE, or PILOT_FIRST, a scope is appropriate. Check it against the six enforced fields before you start, and confirm that the non-goals list has more than one entry if you want the contract’s intent, not just its minimum.
  4. Write the stop-loss condition in terms you can measure before the first ticket is started, so the point of returning to validation is decided in advance.

Dates and what the four-of-seven figure covers

The guide was published September 7, 2026 and updated September 24, 2026. A DEV Community copy by Boris Binyaminov, dated September 16, 2026, carries the same title and makes the same argument. The count of four refusing states is a product-specific figure reported by its publisher, WhittleOS. It is not an independently audited industry statistic. The state list, the field list, and the build-window range describe the tool as documented in that guide, and they are the product’s own design choices rather than general rules for scoping software.

The DEV Community copy is available at Our scoping tool refuses in 4 of the 7 states it can be in, and that ratio is not a tuning choice.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

build planningMVP scopingproduct validationsolo foundersWhittleOS

Leave a Reply

Your email address will not be published. Required fields are marked *

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Recommended PC Tool
Recommended PC Tool
PC Slower Than It Used to Be?Free scan - under a minute
Outdated Drivers Are Slowing You DownFree scan - exact matches

Two free Windows tools

One Free Minute Could Fix That PC

Before you go - each of these free tools takes about a minute and tackles what quietly slows a Windows PC down.

Special offer. View Outbyte info, uninstall instructions, EULA, and Privacy Policy.