Project proof
These examples show the type of work behind ProofForge Rescue: public intake flow, local control-plane tooling, and proof-first quality gates. Each item states what is proven and what is not.
Public website
A public static service site for scoped rescue sprints. It keeps payment locked until written scope, exposes a clear intake path, and separates support proof from revenue proof.
Proven: HTTP 200 public page, scope-first offer, intake copy, hidden payment-link boundary, and support-only proof contract.
Not claimed: customer payment, live settlement, guaranteed repair, or completed client order.
Open siteLocal tooling
Local automation and governance tooling used to route tasks, write receipts, enforce stop/pause rules, track token budget, and keep claims tied to evidence.
Proven: installed files, gates, receipts, stopped-state checks, acceptance matrix work, and deterministic validators.
Not claimed: public SaaS, customer deployment, unlimited agent capacity, or autonomous production unlock.
Request packetQuality gates
Local research around video artifact probing, frame sampling, ffprobe checks, and quality-scoring boundaries for generated media.
Proven: support renders, artifact probes, quality-gate receipts, and a strict rule that screenshots alone do not prove video quality.
Not claimed: Seedance-class parity, production-ready video generator, or customer-ready AI-video product.
Request packetEach serious claim should map to a file, gate, browser proof, or test result.
Support proof, local tooling proof, and paid customer proof are different classes.
The safest first engagement is a scoped diagnostic before a rebuild or live change.