01 Purpose and scope (GTP)

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

PURPOSE AND SCOPE
1.1 The specification guide's layer map names an H layer above the
    machine: the instructions an agent is given. GTP is the generic form
    of that layer.
1.2 An INSTRUCTION SET is one or more artifacts that fill GTP's slots for
    one agent on one platform.
1.3 An IMPLEMENTATION is a named instruction set publishing a conformance
    statement under section 19.
1.4 GTP states what each slot is for and what it MUST guarantee. It MUST
    NOT prescribe a mechanism that only one platform can supply.
1.5 GTP binds no agent. An agent is bound by its implementation, and the
    implementation is answerable to this document.
1.6 GTP is not a rule an agent follows at run time. It is the shape an
    implementation is audited against.