About conformance
Conformance is how the harness proves that any process can plug in, not just Vinaya.
A process conforms when:
- its declaration activates with no hidden defaults;
- every object and authority relation links;
- generic gates cover positive, negative, unavailable and inapplicable cases;
- invalidation is transitive;
- harness events suffice for Mission Control and statistics;
- effects and extensions stay registered and bounded;
- unsupported behaviour is refused precisely;
- semantics hold across adapters.
How it works
The proof runs a corpus on the unchanged harness: the default process, processes deliberately unlike real ones, and at least one held-out topology. Two teams prove two cases, not universality.
The unlike-process proof
| Case | Shape |
|---|---|
| Default process | Tracker items, instruction versions, a criteria list, a dialogue step (Vinaya) |
| Unlike team | Manifest-native work, no tracker, no criteria list, no dialogue step. Signed build evidence with explicit trust roots. Maintainer review. Conditional security review on auth or crypto changes |
| Held-out challenge | A two-of-three review quorum, introduced after the first schema |
Adapter conformance
| Layer | What it proves |
|---|---|
| Concern matrix | Each concern of the task path, with the file that owns it and its test. A test asserts that every applicable row cites a real test |
| Two-runtime fixtures | Nine scenarios run against the real task-tools server, once per adapter: clean result, invalid result, mechanical rejection, bounded retries, fresh reviews, input change, human handoff, cancellation, recovery |
| Adapter contract | One case list that both agent adapters run unchanged: deterministic in CI, and live by hand |
Rules
- Missing or invalid required declarations refuse activation.
- Explicit inapplicability is a recorded skip, with a reason.
- An unavailable service never erases a required check.
- No default concept is renamed and called portable.
- There is no undocumented fallback to the default package.
- A failing live case is reported as failing, never registered as a known failure.
Configuration
None.