Conformance classes

A tool claims one or more conformance classes and proves each one against the conformance suite. Find the class that matches what your tool does, then read the sections it points to.

Informative

This page summarises section 2 and does not add requirements. The conformance suite of section 21 is not yet published, so no class can be claimed today; the schemas already let you check shapes.

Producer

Your tool writes artifacts: a model manifest, a test result, a scenario.

1. Validate every document against its published schema before you send it (see the quickstart).
2. Fill all seven estimand fields. Where your source does not say, write "undeclared" rather than guess, so the gate engine can fill it from the source-type default and label the assumption (section 5).
3. Carry spec_version and the provenance fields of section 6.

Consumer

Your tool reads artifacts and shows or combines their numbers.

1. Keep every fallbacks entry you receive and pass it on with anything you derive from it.
2. If you have a user interface, show the trust label and each fallback label beside the number it applies to.
3. In strict mode (on_gate_fail: "strict"), stop where a gate would have fallen back (section 15).

Engine adapter

Your tool wraps a modelling engine and answers standard requests.

1. Declare the standard requests and tiers you support in your metadata (section 8).
2. Answer the ones you declare; return a typed error for the rest (section 19).
3. You never need to run another vendor’s engine to conform.

Gate engine

Your tool evaluates the published policies.

1. Evaluate each gate on every operation and transition its applies_to names.
2. Keep the eight hard stops as stops, and let every other gate fall back, exclude and continue, route or warn as the catalogue says (section 15).

Agent host

Your tool runs a decision agent such as Newton.

1. Prefer validated artifacts, write drafts only, and cite a source or label a best guess.
2. Keep reading and acting tools separate, as G-NEW-02 requires (section 17).

Log verifier

Your tool checks the integrity log independently of whoever runs it.

1. Reproduce the test vectors of section 18.
2. Check each checkpoint’s consistency proof against the one before it, and raise integrity.broken when a check fails.

Hosted endpoint

Your tool serves a model over HTTP (Tier X) and keeps its internals private.

1. Answer the capability handshake with your manifest, input schema and spec version (section 8).
2. Serve the standard requests you declare over the section 19 API, with typed errors for the rest.

Request and response examples

Request and response pairs will be added here from the OpenAPI document once it is published.