Pre-purchase · Enumerated answers only
Check the boundary without sharing the schema.
Eight closed questions compare your intended use with v1.0.0. No schema, dataset, path, code, feature name, identity, account, or free text is accepted. The result is compatibility routing—not a freeze and not license acceptance.
Eight compatibility checks
Separate product fit from preparation work and excluded use.
The checker evaluates only broad labels. It does not infer roles, inspect names or values, test a policy, select a feature, quote custom work, reserve capacity, or grant a license.
What the result means
Compatibility routing, not a free freeze.
- Likely v1 fit means the selected metadata, runtime, roles, boundary names, policy timing, resource envelope, and license align with the published product; written acceptance is still required.
- Preparation needed means the use may fit after the values-free schema, roles, names, policy, runtime, path, or licensee boundary is made explicit.
- Outside v1 or license means the request requires data values, automatic semantic inference, outcome-adaptive policy, excess scale, analysis, assurance, or use rights that version 1 does not offer.
- The checker never reads a schema and cannot determine which fields would be selected, whether leakage exists, or whether a feature is useful or fit.
Need the evidence behind the boundary?