Scope the idea before the idea scopes you.

The source counts four fields: user, problem, workflow and test. Its score formula is filled fields divided by four times one hundred, rounded. But validation requires all four before saving. These four equal twenty five percent segments therefore make the reachable valid output one hundred percent. A blank field is rejected, not a published seventy five percent draft. This is field completeness, not project quality or demonstrated demand. Team size must be from one through eight. This common eighty pixel per person scale places three two steps above one. Changing three people to eight keeps four complete definitions at one hundred percent: team size does not enter the score formula. The workflow text is copied into Build slice. These values are a local scoping brief, not a prediction of speed, collaboration or hackathon success. The saved record has five fields: team plus the four definitions. Five equal boxes count that record. Editing the workflow without a new valid scope leaves the saved download unchanged. A valid scope saves the new text; reset clears local storage and reloads the original defaults. The brief asks for validation with real teammates. No source rule measures identities, credentials, demand, finished work or actual test outcomes.