Plan 3 / C2

Annual path (consistency checks)

This page is the contract-check page when Plan 3 becomes a candidate after eligibility review. Use `/c2` as the authority for the meaning and return boundary of C2; this page covers only contract conditions, submission targets, and next steps.

Plan 3 / C2 / Annual slot

Amounts are shown after click.

Go to form About C2 Consult

Summary

This lane fixes submission targets, acceptance conditions, and return scope up front so the prerequisites for Plan 3 are clear.

What you confirm here: submission targets / acceptance rule / verification surface.
Use `/c2` as the authority for the full return boundary.
Added summaries and submission support are scoped separately by contract.

Fit check (public)

You can fix objectives/constraints/conditions in writing (inputs can be defined).
Acceptance pass/fail criteria can be decided in advance.
Outputs can be presented as KPIs / summaries / comparison metrics.

Not a fit (rule of thumb): substituting the experiment itself / inputs cannot be fixed / pass‑fail criteria cannot be set.

The concrete target is finalized after eligibility confirmation.

What is fixed by contract

Plan 3 fixes the compare / consistency-gate target, acceptance conditions, return scope, and the verification surface used for submission in advance.

Use `/c2` as the authority for the full C2 explanation. This page handles only contract conditions and how to proceed.

Plan 3 Interface

Plan 3 fixes the internal compute engine and finalizes the input specification by individual contract. Changes after finalization are separated as a change request (a separate Evidence Pack).

Select input shapes (Adapters) from the catalog (up to 3) to clarify up front what must be provided.
Acceptance is performed according to the verification procedure and fixed to prevent definition drift.

Delivery process (public scope)

Stage	Content	Recipient prep	Acceptance check
Requirement confirmation	Organize use case / acceptance criteria / return scope	Prepare prerequisite info	Confirm agreed scope
Computation run	Executed in our private environment	Finalize input specification	Receive deliverable package
Delivery / acceptance	Provide deliverable package	Verify according to procedure	Confirm integrity / acceptance criteria

Acceptance is performed so the recipient can verify consistency by following the agreed procedure.

Public scope and disclosure conditions are fixed by individual contract.

Public verification is minimal; anything other than MATCH is treated as undetermined (undetermined does not imply tampering).

Flow: requirements → input spec → run → deliverable package → acceptance.

Reference pricing

Amounts and revision rate are shown after click.

Eligibility form

Organization (required)

Department (optional)

Contact name (optional)

Email (required)

Use summary (public level) (required)

Input types (max 3) (required)

Time series / logsCSV / JSONL (e.g., event logs, sensors, transactions, operation history)Specs / requirementsText / PDF (requirements, contract, constraints, audit requirements)Observational dataObservation IDs, metadata, error model (submission format fixed by contract)Design variables + constraintsOptimization inputs (variables / constraint gates / failure conditions)Graph structureNodes & edges (map structure into the compute substrate)Images / spectraFeature vectors already extracted, or extraction rules provided (details by contract)Other / TBDSpecial formats can be handled by contract (describe briefly in notes).

Note: You are selecting only the “shape” of inputs here. Concrete inputs are fixed by contract; changes after finalization are treated as a separate deliverable.

Third‑party audit / submission (optional)

Notes (optional)

Note: Intake is normally open. If reCAPTCHA does not appear, you cannot submit (it will show intake closed).

I agree to the Privacy Policy (required).Privacy Policy

Note: Eligibility check is a pre-check to start the process for the current year slot. After review, we will guide you through the next steps.

Standard Track

If you can accept publication of usage records and anti-exploration conditions, consider the Standard Track for the normal price range under public-use conditions. No slot limit. Current-year reference pricing is governed by /pricing with annual revision support.

See standard-track estimate →

Note: Anonymous Track (this page) and Standard Track cannot be combined.