KTP is written in public and changed in public. What each person changed is on the record, issue by issue, under the name they use there. The invitation at the end is the same one they took.
Tamed Autonomy, the SHOULD layer above KTP, eleven proposals for v3.0.0, and a public Python reference library.
KTP asks whether the environment CAN support an action. Tamed Autonomy, Robin’s work, asks whether the purpose SHOULD be pursued at all. He studied v2.1.0 by building against it, filed eleven proposals from that study with the RFC pull requests to carry them, and published the Python reference library that pins to the v2.1.0 tag.
KIL and KAG, the two implementations at the infrastructure boundary, and the execution profile that binds one decision to one exact action.
Before KTP had a name, Mike stretched the ideas and asked the questions that made them click. He built KIL, the Kinetic Infrastructure Layer, and KAG, the Kinetic Action Gateway, both maintained by him and hosted by the project, and he brought the software-substrate execution profile and the consequential-action evidence work to the RFC, with the supplier-neutral editorial that landed first.
Induced Conservatism: the adversary who wants denial, and uses KTP’s own fail-closed rules as the weapon.
The threat model had adversaries who want permission. Kimberly named the one who wants denial: manufacture uncertainty, dispute or stress until the protocol’s conservative rules deny, deautomate or hibernate legitimate work, and the attack succeeds when KTP behaves exactly as specified. TM-D-005 gives it an ID and a bound; the two proposals that follow it target v3.0.0.
Five rules keep a contribution from stalling. They are the whole of the contributor rails, and every person above worked inside them.