Jump to content

13 Compatibility (GTP)

From The Invariance Itself
Revision as of 06:42, 18 September 2026 by BFP Rauch (talk | contribs) (1 revision imported)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Instruction-layer specification, machine-optimized text: GTP 0.1.0, section COMPATIBILITY. Part of GTP and the TPM hub. Implements TPS 0.1.0. PROPOSED and UNDECLARED: no implementation may cite it as normative until its genesis line is landed. Human-only edit (TPS 5.13). The text below is this section of the GTP 0.1.0 artifact, verbatim; the whole artifact and its file fingerprint are on The Principia Machina/GTP. Human readers: the contents page is the map.

COMPATIBILITY
13.1 Every artifact MUST declare a compatibility RANGE with an upper
     bound, never a floor.
     BASIS: a floor promises that every future version will still be
     compatible, which is a promise about work nobody has done.
13.2 The declared range MUST be compared against the version actually in
     force at the moment the artifact loads.
13.3 On mismatch, or where the declaration is absent, the artifact MUST
     NOT execute. The agent states it and stops.
13.4 A clause converting that halt into a warning is a disabled check for
     as long as it stands.
13.5 An implementation MUST NOT ship a transitional exemption to 13.3.
     Removing one is a required first action of the next revision.
13.6 A payload that edits a section named in any artifact's declared
     dependencies MUST name the affected artifacts.