20 Bases (GTP)

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

BASES
20.1 RFC 2119 and RFC 8174, normative keywords.
20.2 ISO 8601, dates. ISO 24495-1, plain language. ASD-STE100, technical
     register.
20.3 Semantic Versioning 2.0.0, version semantics and public interface.
20.4 OWASP Top 10 for LLM Applications 2025: LLM01 prompt injection for
     section 8, LLM02 sensitive information disclosure for the egress
     gate, LLM05 improper output handling for 8.11, LLM06 excessive
     agency for the destructive gate.
20.5 The rule that a defence must not be load-gated, 7.3, follows from
     the same source: the injection that disables a load is the injection
     the defence exists to catch.
20.6 The layer map placing this document at H is the specification
     guide's.
20.7 Sections 3, 6, 10, 13, 14, 15 and 16 are generalised from one
     working implementation, the PMP family, and from nothing else. A
     second independent implementation would be the first real test of
     whether they are generic, and none exists.
     OWED: a second implementation. Kind of block: absence.