Module conformance 

Conformance & reproducibility scorecard (conformance-v1, EPIC 12.17).

A self-check any user or CI can run to prove this instance honors its own contracts and that its extension surface behaves. It exercises three areas:

• contracts — every machine-verified contract version is present.
• reproducibility — the public discovery documents (/v1/capabilities, /v1/openapi.json) are deterministic (same bytes across two builds).
• extensions — every registered compressor / chunker / read-mode in the extension_registry satisfies the stable invariants the engine relies on (determinism, budget honoring, coverage).

The output is a Scorecard: a flat list of Checks plus a pass count. It is data, not prose, so it can be rendered (CLI), shared (JSON), or gated on (all_passed() in tests/conformance_suite.rs).

Structs

Check

One conformance check result.

ConformanceFailure

ConformanceResult

Result of checking a capability manifest or invocation against contract rules.

Scorecard

The full result of a conformance run.

Functions

check_invocation_conformance

Validate a CapabilityResult against the manifest’s declared constraints.

check_manifest_conformance

Validate a CapabilityManifestV1 against OCLA contract rules.

register_read_mode_renderer

Register the ctx_read renderer the accuracy checks run against. The read tools live above the engine; the CLI registers them at start-up (tools::ctx_read::register_conformance_renderer). The first registration wins.

run

Run the full conformance suite against this instance.

Type Aliases

ReadModeRenderer

The ctx_read mode renderer the accuracy checks measure: the signature of tools::ctx_read::process_mode (content, mode, file ref, short name, extension, original tokens, CRP mode, file path, task) returning the rendered view and its pre-footer body token count.