Price pre-audit, T4–T1 core, post-audit, and the scorer. Approve from repository evidence.
Contest-style discovery with permanent proof: estimate pre-audit, core T4–T1 pool, T0 final review, formal-methods prep, Native v5 scorer, and post-audit fix rounds — each fee separate.
Four prices with four different evidence boundaries.
They belong in one plan, but they are not interchangeable percentages or reused deployed-pricing labels.
Lock the snapshot, map risk surfaces, prepare invariants, run readiness gates, and send a bounded brief to core reviewers.
10%, 15%, or 20% of core02ReviewCore auditT4 function → T3 contract → T2 cross-contract → T1 system, with validation cascade and T0 report lock.
Repository-scored tier pool03VerifyPost-auditPrice the real baseline-to-fix diff, then use an equal-work panel and an independent reviewer to verify remediation.
Quoted after the fix diff exists04ExplainNative scorerBuild a native v5 /1400 evidence record with visible blockers, missing proof, freshness, and policy-bounded status.
Offer applied automaticallyBuild the funding plan line by line.
Scope inputs create a public estimate. Repository parsing replaces the estimated clusters, reviewer slots, schedule, and exclusions before approval.
Repository identity
This is what turns the estimate into an auditable plan.
Approved-scope estimate
Use production implementation code and material dependencies only.
Lifecycle coverage
Recommended services are selected, but each amount stays visible.
What is policy-backed, and what is still an estimate?
3% protocol fee, automatic final-review fee, pre-audit reviewer premiums, scorer reservation bands, and post-audit manifest formula.
Clusters, reviewer slots, selected depth, pool band, and schedule because browser inputs are not an AST and call graph.
Included files, exclusions, exact whole-function ownership, reviewer availability, delivery windows, and the final deposit.
See exactly how much the score offer saves.
The dated native lifecycle offer is applied to the scorer reservation automatically. It does not add points, change the score, or lower the review depth. Audit pricing still follows accepted repository scope.
The button does more than save a calculator.
It moves the repository identity and scope assumptions into onboarding so an approved plan can replace browser estimates.
- 1Lock repository identity
Repository URL, exact commit, chain, scope files, exclusions, and notes.
- 2Build deterministic clusters
Whole-function ownership, call-graph closures, risk scores, reviewer slots, and timeline windows.
- 3Approve the deposit
Admin review confirms the plan, reviewer availability, optional reserves, and the final amount.
