04 Language and naming (GTP)

Documentation, non-normative; machine-optimized text: section LANGUAGE AND NAMING 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.

LANGUAGE AND NAMING
4.1 Normative keywords per RFC 2119 and RFC 8174, binding in capitals
    only.
4.2 Dates in ISO 8601 extended format.
4.3 One name per object. An implementation MUST NOT carry synonyms for a
    defined term.
4.4 An implementation MUST publish its defined names where a reader can
    find them without reading the rules.
4.5 A retired name MUST NOT be reused for anything else, and the retired
    list MUST be kept.
4.6 Terms of art belonging to the project rather than to the instruction
    layer are domain content. GTP requires that they be declared, not
    what they are.