Before the worker starts
Keep the claimed job queued across startup.
Engineering / evidence to artifact
Build a prototype.
Keep the argument.
ProToPro connects a reported problem to a bounded product brief, an explicit human decision and an inspectable generated result. The engineering challenge is preserving that chain through failures.
Four boundaries. One traceable record.
- 01 / EVIDENCE
Original public report, source links and limitations
An observed report does not prove market demand.
- 02 / REVIEW
A human decision bound to an exact scope snapshot
A browser rehearsal cannot authorize a server build.
- 03 / EXECUTION
Persisted job, stable identities and graph checkpoints
An interrupted node may repeat a provider request.
- 04 / ACCEPTANCE
Generated source, artifact hash and recorded observations
Model-written QA does not prove functional behavior.
Decision / durable execution
Recover the work.
Preserve its identity.
Execution admission commits the run claim and job together. The job retains its opportunity and build identities; venture and build graphs save synchronous SQLite checkpoints. A same-host kernel lock prevents competing imported-brief workers.
Before recovery, the worker checks the approved input and its code/runtime fingerprint. Changed input or incompatible code stops execution for review. Missing model configuration leaves queued work inspectable.
The storage contract matters.
This is a single-host design with persistent database and checkpoint files. Ephemeral cloud storage cannot satisfy that contract. The system does not claim distributed scheduling or exactly-once billing.
A provider response interrupted before checkpoint persistence can be requested again. Legacy discovery-triggered execution retains its earlier recovery behavior; the new guarantee applies to imported approved briefs.
Validation / actual process termination
A restart assertion is not a restart experiment.
The local campaign kills a real worker process at each boundary, then starts a new process against the same isolated storage. Deterministic model fixtures exercise the production graphs without provider calls, email or publication.
After a venture checkpoint
Resume the existing opportunity; preserve saved evidence.
Between venture and build
Keep the completed dossier and assign one build identity.
After a build checkpoint
Preserve completed generated files and resume the same build.
After artifact persistence
Reuse the saved artifact instead of generating a replacement.
Additional tests cover live worker contention, concurrent HTTP admission, changed approval, code identity and terminal graph failures. Receipts retain identities, checkpoint counts, call sequences and artifact hashes. These fixtures establish recovery behavior, not generated-product quality.
Design contract / independent browser review
Make the product specific. Exercise the result.
New browser builds require a primary workflow, layout, visual direction, signature detail, interface states and responsive rules before engineering begins. Major and critical QA findings block completion. A source audit checks a limited structural floor; it does not judge visual quality.
The optional browser reviewer serves exported files in an isolated local session, blocks external requests and exercises declared scenarios at desktop, tablet and mobile widths. Decision Desk is the handcrafted reference for this workflow. It is not an AI output benchmark.
Public browser edition: no backend calls. Full execution: explicit connected mode, authenticated local backend and persistent storage. Provider-funded generation has not been benchmarked in this release.
What still needs independent evidence?
Functional quality
Generated files and model reviews need actual behavior tests against the approved criteria. Operator observations are recorded assertions.
Cost enforcement
Recorded estimated spend is not an atomic per-call reservation or guaranteed dollar ceiling. No paid model benchmark was run for recovery validation.
Remote availability
The public recorded walkthrough works without a live API. Authenticated operation depends on a separately available backend with suitable persistent storage.