SnapOS-conformant is not a style. It is a versioned audit-output contract.
The Conformance Suite defines the minimum public interface for outputs that claim SnapOS compatibility or conformance. It does not disclose the private audit engine.
A SnapOS-conformant audit is an output that passes a versioned schema, minimum witnesses, allowed result labels, counter-hypothesis requirement, reopen triggers and a reliance statement. SnapOS compatibility is an output property, not a self-description.
Conceptual use
Uses SnapOS terms, failure modes or public frames. No conformance claim without schema and witnesses.
Schema-mappable output
Separates claim, evidence, assumption, decision and regime; identifies at least the required core witnesses.
Versioned output contract
Meets schema, witness set, result labels, counter-hypothesis, reopen trigger and reliance statement.
Future registry status
Certification requires a later qualification, registry, QA and attestation layer. It cannot be self-declared.
What may be published
Output duties
Audit ID, version, audit object, object boundary, decision object, claims, evidence sources, assumptions, regime, context, authority, temporal validity, transfer claim, finding, limitations, reopen trigger and reliance statement.
Minimum witnesses
Source, object, evidence, decision, authority, temporal, transfer and reviewer witnesses. If a witness is not applicable, the output must say why.
Allowed result labels
SUPPORTED, SUPPORTED WITH CONDITIONS, UNSUPPORTED TRANSFER, REVIEW REQUIRED, DO NOT RELY, OUT OF SCOPE, INSUFFICIENT EVIDENCE and NON-CONFORMANT OUTPUT.
Conformance gates
C1–C10 cover object isolation, claim/evidence separation, assumptions, regime declaration, authority, time, transfer, falsification, reopen trigger and reliance.
What is not disclosed
The Conformance Suite does not publish internal operator sequences, scoring, weights, the full failure library, benchmark evaluation logic, prompt chains, trigger chains, private orchestration or internal R&D heuristics.
Publish the grammar. Standardize the interface. Certify the execution. Protect the compiler.