Expand description
CH-14 conformance harness.
Validates that a compiled agent descriptor’s declared v2 sections
(model_requirements, prompt_dialect, context_strategy) are
satisfiable at load time and honored at run time — by driving the exact
runtime functions a real request uses (ModelRouter::route,
PromptDialect::detect, apply_strategy), not a re-implementation of
them. This is genuinely new test infrastructure (per assessment.md,
there was no “conformance” concept anywhere in the repo before this).
rag_configuration and api_harness are declarative-only sections with
no corresponding runtime decision to conform against yet (RAG posture is
read by the retrieval pipeline directly; API harness just advertises
transport support) — out of scope for this harness, consistent with
plan.md’s own framing (“declared model/dialect/context are satisfiable at
load and honored at run”).
A section left at its parsed default (which is indistinguishable from
“the author declared nothing here”, since #[serde(default)] produces
the same value either way) is reported as CheckResult::NotDeclared
rather than checked — there’s nothing to conform to.
Structs§
- Conformance
Report - Full conformance report for one compiled descriptor’s IR payload.
Enums§
- Check
Result - Outcome of one section’s conformance check.
Functions§
- check_
conformance - Run the full conformance check against a compiled descriptor’s IR.