19 Conformance (GTP)

Documentation, non-normative; machine-optimized text: section CONFORMANCE of the text published under the name GTP. Part of GTP and the TPM hub. Written against TPS 0.1.0, part 6, the AGENT CONTRACT, which taken as a runnable instruction set is GTP and carries no version of its own (TPS 1.2.6). This text carries no version and no genesis line; where it and TPS differ, TPS governs (D174.1). Human-only edit (TPS 5.13). The text below is this section, verbatim; the whole text and its file fingerprint are on The Principia Machina/GTP. Human readers: the contents page is the map.

CONFORMANCE
19.1 An implementation claims conformance by publishing a CONFORMANCE
     STATEMENT.
19.2 The statement MUST list every numbered section of GTP and name, for
     each, the artifact and section that fills it.
19.3 A slot the implementation does not fill MUST be listed as EMPTY with
     a reason. Omission is not permitted.
     BASIS: an implementation that quietly omits a slot is
     indistinguishable, from the statement alone, from one that fills it.
19.4 The statement MUST name the GTP version it is made against.
19.5 An implementation MUST NOT be described as conforming where any rule
     named in 7.1 is unfilled.
19.6 Conformance is self-reported and structural. It warrants that the
     slots are filled. It warrants nothing about behaviour, which is
     certified under TPS 5.14 and measured by the canaries there.
19.7 The statement MUST be republished when either GTP's version or the
     implementation's version changes.
19.8 An implementation MAY fill one slot from several artifacts, and MAY
     fill several slots from one. The statement records what is actually
     there.