The eight rules, the fast and slow layers, the reasons behind the rules, and the acronyms the chapter uses.
The KTP mechanism
A spec that cannot be read the same way twice cannot be enforced the same way twice.
The RFC series is written to a controlled vocabulary for the same reason the workbook is: an envelope, a veto or a ceiling has to mean one thing to every reader and every machine. These are the rules the contract tabs are linted against, and the reasons each rule exists, so a reader can hold the chapter to them.
The working form, from the workbook
Three tab jobs. Eight rules with what each means and how it is enforced. Two layers, slow (why, at human speed) and fast (rules, at machine speed). The why behind each rule, with its status. The acronyms that recur across the chapter.
Acequia, Inc. is an invented organization. These pages present a working design, not deployment results; its contracted stages and change freezes are illustrative. The sections below mirror the Governed Autonomy workbook (v0.50): its columns, rules, invariants and catalogs, as written, with the worked example's organization named as it is there. The deployment's own rows, parties, contract identifiers and configuration stay with the deployment; where a table's rows stay, its columns are shown.
01Tab jobsworkbook tab 35 · Writing rules
What this is for. How the contract tabs are written so a test can fail them.
Advice cannot fail a test. A duty can. Each rule carries the reason it exists. How to use it. Read the why first. Then write only words a test can fail.
Adapted from the principles of ASD-STE100 Simplified Technical English (STE); this is not a compliance claim. Acequia keeps its own dictionary. Exec Overview and Vision argue at human speed. The contract tabs state rules a test can fail. The full guide is ontology/WRITING.md.
must / shall = duty. must not = ban. should / ought = advice (not a test). may = permission without obligation. can / cannot = ability. might / could = hedge. Machine-speed rules use must, must not, can, cannot. Keep may when it means permission. Do not use should, ought, might, could, or may not.
Procedure (spine steps, falsifier tests, break-glass) is capped at 20 words. Descriptive machine-speed rules are capped at 25. Trim. Do not split an OR or AND test.
05Acronyms the chapter usesworkbook tab 34 · Acronyms
The acronyms that are generic to the chapter; the deployment's own stay with it.
38 of 38
ADJ
Adjudicated — Acequia evidence class: exists because a named authority recorded it.
Not KTP-CLASS:A (Agentic).
APO
Application Operations — Semantic Join seat.
Not a Party register row.
ARQ
Availability, Retainability, Quality — independent verification of service consequence
ASM
Assumption identifier on Claims & boundaries; each carries a falsifier (FAL).
CAD
Computer-aided dispatch — public-safety system; observe-only on the join
CMP
Compliance — Semantic Join seat.
Not a Party register row.
COP
Competition Operations / competition venue class used in a playbook
CSIRT
Computer Security Incident Response Team
CYB
Cyber Security — Semantic Join seat.
Not a Party register row.
DER
Derived state — Acequia evidence class: read from a calendar, config, or table with as-of + validity.
Not KTP-CLASS:S (Subjective).
DIR
Direct — Acequia evidence class: one instrument samples a quantity.
Not KTP-CLASS:D (Determined).
EDR
Endpoint detection and response
ENU
Enumerated — Acequia evidence class: computed over a counted set inside a boundary.
Not KTP-CLASS:N (Narrative).
FAL
Falsifier identifier on Claims & boundaries: the observable test that fails a claim.
GOV
Governance — Semantic Join seat.
Not a Party register row.
GRC
Governance, Regulatory, and Compliance — three distinct join parties on the shared case
ITIL
Information Technology Infrastructure Library — ITIL 4 practice taxonomy as shared service-management vocabulary; not joint version or certification evidence
ITO
IT Operations — Semantic Join seat.
Not a Party register row.
ITSM
IT service management / ticketing system of record for security incidents
KAG
Kinetic Action Gateway — a KTP implementation that binds one signed decision to one exact operation and holds it to that decision at release.
KG
Knowledge graph — invariant prefix KG-1 to KG-26 for the join graph specified on the Knowledge graph tab.
KIL
Kinetic Infrastructure Layer — a KTP implementation at the infrastructure boundary: signed-state verification and per-action authorization between authoritative refreshes.
KPI
Key performance indicator — a measured service metric. Evidence, never a verdict.
KTP
Kinetic Trust Protocol — the governance protocol whose Zeroth Law, , this workbook adopts in its testable form (ASM-27).
MCP
Model Context Protocol — SIEM platform on MCP is context only
NCOP
Non-competition operations / non-competition venue class
NOC
Network Operations Center — IT Operations operating center
PACS
Physical access control system — DIR/ENU evidence, not a safety declaration
PQC
Production Quality Control (Media Provider).
Not ARQ.
PUB
Published — Acequia evidence class: a third party's number, read.
Not KTP-CLASS:P (Policy).
REG
Regulatory — Semantic Join seat.
Not a Party register row.
RTOC
Regional Technical Operations Center
SIEM
Security information and event management
SLA
Service level agreement — a contracted service target.
SLO
Service level objective — the declared target a workload class must meet.
SOC
Security Operations Center
STE
Simplified Technical English — ASD-STE100 principles this workbook adapts.
Not a compliance claim.
TOC
Do not use bare TOC. Use TechnologyTOC (Acequia venue technical authority) or BroadcastTOC (Media Provider venue signal hub).
