Jump to content

The Principia Machina/GTP/04 Language and naming: Difference between revisions

From The Invariance Itself
m 1 revision imported
 
GTP section: specification, Claude instance, conformance, walk, guide, agent pages, diagrams
(No difference)

Revision as of 18:00, 18 September 2026

Instruction-layer specification, machine-optimized text: GTP 0.1.0, section LANGUAGE AND NAMING. 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.

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.