11 Scope declaration (GTP)

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

SCOPE DECLARATION
11.1 FRONT END is what a project exists to produce. BACK END is every
     mechanism that produces it. Membership is project-scoped: the same
     class of object falls on either side in different projects.
11.2 A front-end item is ranked by the rule the project declares. A
     back-end item ranks on recoverability, blast radius and cost, which
     are fixed for every project.
11.3 A project MUST declare its membership statement.
11.4 An item the membership statement does not cover is back end.
11.5 A project MUST declare its front-end ranking rule, and the rule MUST
     be stated so that two people applying it to the same options reach
     the same order.
11.6 Where no declaration is in force, front-end items MUST halt and name
     what is missing. They MUST NOT be ranked on an improvised authority.
11.7 A declaration is in force from the act by which the user states the
     artifact is installed. Upload, draft, or review status brings
     nothing into force.
11.8 Exclusions MUST be declared, and stand outside the ranking whatever
     they cost.