Proof Lab
In buildEvidence first. Claims second.
The Software 4 All Proof Lab studies how AI-built software moves from demo to controlled software path.
Accepted claims should map to evidence before being registered. Claims without evidence remain unregistered. The Proof Lab is where evidence is produced, validated, and stored before any readiness claim is made.
FounderGate core harness
proof path 01
V8-A build stages · 4 of 4
internal, recorded
External operator proof
not yet started
Commercial / security certification
no evidence → blocked
Claim → evidence mapping. Unsupported claims remain blocked until evidence exists.
Roadmap Tracker v2 Snapshot
FounderGate V8-A — recorded evidence, not claims.
As of July 10, 2026 · Roadmap V8.11 · Repo private · V8-A4 product SHA a957b01 · Suite 36/36 green. Four internal build stages are done and recorded. Full V8-A acceptance still requires a real stranger test.
V8-A ledger
Recorded · illustrativeV8-A1
acd2b04
V8-A2
dba8720
V8-A3
e92f8b9
V8-A4
a957b01
Accepted / Closed
V8-A1 · Truth Dashboard
accepted at acd2b04
V8-A2 · Preview Bay + Bug Collector
accepted and closed at dba8720
V8-A3 · File Cabinet
accepted and closed at e92f8b9
V8-A4 · Project Guide
witnessed and closed at a957b01
Checker HIGH findings + Audits
- — V8-A2: caught 0.0.0.0 bind before merge
- — V8-A3: caught 2 HIGH leaks
- — V8-A4: caught 1 HIGH
- — V8-A3 advisor audit 6/6 PASS
- — V8-A4 audit 6/6 PASS
- — V8-A3 amended post-acceptance: hard-link fail-closed fix
Stranger test remaining
A real non-developer must run all 7 steps unaided — no terminal, no code, no help. Their notes become evidence; every confusion becomes a permanent guard.
Unsupported claims remain blocked until evidence exists.
Interactive Proof Systems
Six artifacts. One evidence discipline.
Each artifact handles a different part of the proof lifecycle—from recording what happened to preventing unsupported claims from moving forward. Open any artifact for its full interactive illustration.
Lab Notes
Turn observations into recorded findings.
Explore artifactEvidence Packets
Assemble what was checked, what is missing, what decision is needed.
Explore artifactProof Ledger
A running record of gate runs, decisions, and open gaps.
Explore artifactClaim Register
Claims cannot move forward without evidence.
Explore artifactAI-Built App Failure Patterns
Recurring failures become permanent guardrails.
Explore artifactBenchmarks
Measure whether supported claims are getting stronger.
Explore artifactArtifact relationship map
One shared discipline.
- 01 · Lab Notes
- 02 · Evidence Packets
- 03 · Proof Ledger
- 04 · Claim Register
- 06 · Benchmarks
- 05· Failure Patterns · feeds back into notes, evidence & benchmarks
The artifacts are separate tools, but they share one discipline: evidence is recorded, gaps remain visible, and unsupported claims stay blocked.
Proof Paths
Four defined proof paths.
Internal proof comes before commercial proof. No external operator proof has been completed yet. The four proof paths are defined — completion of each requires evidence before the next begins.
FounderGate core harness
The primary internal proof path. Tests FounderGate gate logic, evidence packet format, and approval decision workflow.
AKIOR / Accior
Internal stress project. Tests FounderGate under complex multi-feature build conditions. Evidence is logged but not shared externally.
Private Note Therapist
Privacy-sensitive internal proof path. Tests FounderGate under data sensitivity constraints. Evidence is logged but not shared externally.
Outside design partners
Future proof path with qualified external design partners. Not yet started. Intake when evidence readiness gate passes.
Commercial proof requires external operator evidence. Outside design partner proof path not yet started. Internal proof only at this stage.
Research / Proof Lab
In buildResearching the proof layer for AI-built software.
The Software 4 All Proof Lab studies how AI-built software moves from demo to controlled software path. It focuses on evidence packets, builder/checker separation, protected files, false-green detection, non-developer approval review, and claim discipline. Evidence first. Claims second.
Lab Notes
Ongoing research notes on AI-built app failure patterns, approval review workflows, and evidence discipline.
Evidence Packets
Structured records of what was checked, what evidence exists, and what decision the Approval Authority must make.
Proof Ledger
Running record of accepted gate runs, decisions, accepted claim mappings, and open proof gaps.
Claim Register
Accepted claims mapped against evidence. Unsupported claims remain blocked until evidence exists.
AI-Built App Failure Patterns
Research into how AI-built apps fail — false-green detection, missing evidence, weak auth boundaries, and demo-to-real gaps.
Benchmarks
Baseline measurements for gate performance, evidence completeness, and proof path progress over time.
Public-safe research themes
Illustrative product mockup. Sample values shown. Proof-gated claims only.
Research themes shown are public-safe only. Internal policy engine mechanics, proprietary prompts and rules, full harness scripts, private logs, source code, and automation keys are not disclosed.
Claim Discipline
Disciplined claim control is the point.
Not making a claim is not a weakness. It is the evidence discipline that makes any future claim credible. The following rules govern what Software 4 All can and cannot claim.
Unsupported claim
Blocked at the gate
No evidence packet → claim not registered. It cannot proceed to any readiness statement.
Evidence-backed claim
May proceed
Claim maps to an evidence packet → registered. Only then may it support a scoped statement.
Roadmap accepted does not equal product built.
Mockup does not equal deployed product.
Internal proof does not equal outside proof.
No commercial claim is made without external evidence.
No production claim is made without deployment evidence.
No platform claim is made without outside operator evidence.
No security claim is made without security review evidence.