01Audience one
Founder
The Founder owns the idea, enters the evidence, and reads the survival verdict before committing further.
- Owns the idea and the verdict
- Records evidence by class
- Reads the build status and done notice
Owns the idea
first-project
by
Patrick N
Patrick NBUILD ME A NEXT 1 MILLION WOTH IDEA , think of something build it and make sure it has potential and can survive , i mean an idea with strong MOA make it and tell me once done
Comments (0)
Sign in to leave a comment
Project Tasks
20 planning tasks#1
Generate system requirement document
0m 53s0.05 cr used
Done#2
Generate personas & user flows
0m 6s0.05 cr used
Done#5
Architecture
0.05 cr needed
Backlog#6
Workspace task plan
0.05 cr needed
Backlog#7
Create flow for Founder
0m 5sCredits in parent
Done#8
Create flow for End user
0m 4sCredits in parent
Done#9
Landing
2m 42sCredits in subtasks
Done#10
Sign Up
Credits in subtasks
Backlog#11
Build Status
Credits in subtasks
Backlog#12
Login
Credits in subtasks
Backlog#13
Workspace
Credits in subtasks
Backlog#14
Landing / Hero
0m 28s0.85 cr used
Done#15
Landing / Evidence Classes
0m 30s0.85 cr used
Done#16
Landing / Audience And Verdict
0m 26s0.85 cr used
Done#17
Landing / Navigation
0m 0s0.85 cr used
Done#18
Landing / Footer
0m 1s0.85 cr used
Done#19
Navigation
0m 19sCredits in parent
Done#20
Footer
0m 25sCredits in parent
Done#21
Fix Landing: The required coded preview assigns the strong-proof bar black instead of the SRD’s red…
0m 51sCredits unavailable
Done#22
Fix Landing review finding: frontend/src/components/Landing Hero.jsx: The required…
0m 21s0 cr used
Done
proofline
Validate an ideawith evidence,not hype.
01
Proofline records your market, moat, and demand evidence, classifies each item by strength, and computes a survival verdict before you commit further.
Evidence classesStrength
Strong proof
Verified demand: paying pilots and repeated usage with a dated source.
Class
Weak proof
A claim in progress: signals that hint at demand but are not yet sourced.
Class
Missing
Not evidenced yet. The workspace names the gap before you commit.
Class
StrongWeakMissingVerdict computed per idea
Built for Founders and End users — proof before commitment.
02Evidence classes
Proof, coded by strength.
Every piece of evidence is filed into one of three classes. Colour makes strength readable before a single word is read.
- Strong
- Weak
- Missing
DefinitionCount
- Strong proof
Evidence that survives scrutiny — named market signals, a stated moat claim, and demand proof the founder can stand behind.
1Class - Weak proof
Evidence that hints at demand but does not yet settle it — anecdote, a single signal, or a claim still being tested.
1Class - Missing
The class with no evidence recorded yet. Named plainly so the gap is visible before any further commitment.
1Class
Strong proof carries the verdict. Weak proof submits to review. Missing is named, never hidden.
Audience & verdict
02Audience two
End user
The End user is the operator who opens the built product, completes the main validation task on a shared idea, and receives a clear result.
- Completes the main validation task
- Works a shared idea
- Receives a clear result
Works the validation
03Concept
Survival verdict
A computed read on whether the idea has the market opportunity and durability to survive, and exactly which evidence is still missing.
InputEvery evidence item is classified.
ComputeStrength counts drive the verdict.
OutcomeOne survival verdict, plus what is missing.
Strong proofWeak proofMissing
You see at a glance whether the idea can survive, and what to gather next.
Survival verdictComputed
proofline
Validate an ideawith evidence,not hype.
01
Proofline records your market, moat, and demand evidence, classifies each item by strength, and computes a survival verdict before you commit further.
Evidence classesStrength
Strong proof
Verified demand: paying pilots and repeated usage with a dated source.
Class
Weak proof
A claim in progress: signals that hint at demand but are not yet sourced.
Class
Missing
Not evidenced yet. The workspace names the gap before you commit.
Class
StrongWeakMissingVerdict computed per idea
Built for Founders and End users — proof before commitment.
02Evidence classes
Proof, coded by strength.
Every piece of evidence is filed into one of three classes. Colour makes strength readable before a single word is read.
- Strong
- Weak
- Missing
DefinitionCount
- Strong proof
Evidence that survives scrutiny — named market signals, a stated moat claim, and demand proof the founder can stand behind.
1Class - Weak proof
Evidence that hints at demand but does not yet settle it — anecdote, a single signal, or a claim still being tested.
1Class - Missing
The class with no evidence recorded yet. Named plainly so the gap is visible before any further commitment.
1Class
Strong proof carries the verdict. Weak proof submits to review. Missing is named, never hidden.
Audience & verdict
01Audience one
Founder
The Founder owns the idea, enters the evidence, and reads the survival verdict before committing further.
- Owns the idea and the verdict
- Records evidence by class
- Reads the build status and done notice
Owns the idea
02Audience two
End user
The End user is the operator who opens the built product, completes the main validation task on a shared idea, and receives a clear result.
- Completes the main validation task
- Works a shared idea
- Receives a clear result
Works the validation
03Concept
Survival verdict
A computed read on whether the idea has the market opportunity and durability to survive, and exactly which evidence is still missing.
InputEvery evidence item is classified.
ComputeStrength counts drive the verdict.
OutcomeOne survival verdict, plus what is missing.
Strong proofWeak proofMissing
You see at a glance whether the idea can survive, and what to gather next.
Survival verdictComputed
No comments yet. Be the first!