Sandboxed verification runs
Every artifact is exercised in isolation — real launches, real journeys, real failure injection. A claim without an execution trace is not evidence.
Forges operational
Nothing ships unproven.
The Certification Forge is an autonomous QA and release authority. It takes the work — from our forges or yours — runs it in isolation, chains the evidence, and signs a verdict anyone can verify. The customer control plane, API, evidence custody, and verification surface are live now.
PROOF OF WORK · SEAL
Sample artifact
Inspect the sanitized proof-of-work package for Certification before you buy — full evidence chain, no customer PII.
THE AUTHORITY
Hash-chained evidence
Each verification step is chained to the last, so the record cannot be quietly edited after the fact. The history is the proof.
Signed verdicts
The forge's verdict — certify or block — is cryptographically signed. Default verdict is BLOCK; promotion is earned by passing evidence.
Public verification
Anyone holding the seal can verify it against the evidence chain without trusting the platform. Proof that travels with the product.
LIVE / FAIL-CLOSED
Customer intake and verification are live.
Create governed projects, submit immutable artifact identities, inspect redacted evidence, evaluate release gates, publish verifiable seals, and audit the full chain through the live API.
The replacement family-model adapter is still passing its measured promotion gate. Until it clears the fixed evaluation threshold, new execution results remain NOT_READY instead of receiving an unearned seal. The service is live; trust stays fail-closed.
CREDITS · TRANSPARENCY
Certification workload calculator
Estimate credits for single-artifact seals and release-train batches before you open a certification run.
Certification100–250 credits
This run will consume ~100–250 credits
One governed intake, sandboxed run, hash-chained evidence, signed verdict for a single artifact.
| Forge | Work type | Estimated credits |
|---|---|---|
| Certification | Single artifact certificationOne governed intake, sandboxed run, hash-chained evidence, signed verdict for a single artifact. | 100–250 |
| Certification | Release-train batchBatch of related artifacts under one project with deploy-gate evaluation and public seal publish. | 400–1,000 |
CREDITS · POLICY
Credit policy
How credits expire, roll over, overage is priced, failed runs are treated, and what happens to exports after cancel.
| Topic | Summary | Detail |
|---|---|---|
| Credit expiration | Monthly allotments expire at the end of each billing period. | Subscription credits are granted at period start and expire when the period ends. Unused credits do not convert to cash. One-time top-up packs (when offered) expire 90 days after purchase unless the pack states otherwise. |
| Rollover | Up to 20% of unused monthly credits roll over once. | At most 20% of the period’s unused allotment may roll into the next billing period, and rolled credits expire at the end of that next period (no multi-month stacking). Enterprise committed-capacity plans may define custom rollover in the order form. |
| Overage price | $0.05 per credit after the monthly allotment is exhausted. | When a confirmed run would exceed remaining credits, we show the projected overage before you confirm. Overage is billed at $0.05 USD per credit (or the rate on your enterprise order form). You can decline overage and cancel the run with no charge. |
| Failed builds & retries | Platform faults are not charged; customer retries charge only after confirm. | If a run fails because of a platform or infrastructure fault (our side), consumed credits for that run are refunded to the period balance. Customer-initiated retries, re-specs, and re-runs after a fail-closed gate require a new estimate and a new CONFIRM; they consume credits only after you confirm. |
| Cancellation & export | Cancel anytime; finished work stays exportable for 90 days. | You may cancel a forge or Full Foundry subscription anytime; access continues through the paid period. Completed artifacts, reports, and seals remain available for export for 90 days after the subscription ends. Incomplete in-flight runs are stopped at period end; partial work that has not passed gates is not guaranteed exportable. See Refunds & Cancellation for billing refunds. |
BUNDLE · ALL FORGES
Full Foundry
Hephaestion Production + Daedalus Workshop + Certification seat — one account, one bill, shared priority queue.
Save $149/mo vs Production + Workshop bought separately ($299 + $449).
- 10,000 Hephaestion forge credits / month
- 6,000 Daedalus design credits / month
- Certification Forge project seat + deploy-gate API
- Priority queue across all three forges
- Shared account, single Stripe customer, per-forge cancel
- Export of completed artifacts retained 90 days after cancel
CERTIFICATION · CERTIFICATION RUN · PRE-EXECUTION
Start a certification run
Describe the artifact set, see This run will consume ~X–Y credits, then CONFIRM before any credits are consumed.