Pillar · reference · v1.2 · updated July 2026
Agent infrastructure and coordination
What an agent may commit, under whose approval, against which limit, and how the action is unwound. The reference for putting agents inside a control environment rather than beside one.
Written and reviewed by practitioners who have delivered these systems. Ungated, citable, and versioned — the changelog records what changed and why.
- Hubs
- 7
- Articles & tutorials
- 0
- Glossary terms
- 0
- Capability page
- Agent infrastructure & coordination
7 hubs
- 01
The authority model
Propose, commit, escalate — and the limit that separates them.
- 02
Signing and thresholds
Where the key sits, and what the policy does when an approver is unavailable.
- 03
Coordination and shared state
Ordering, idempotency, and arbitration when two proposals conflict.
- 04
Reversibility
Which actions can be unwound, which cannot, and how the distinction is enforced.
- 05
Evidence
Reconstructing why an action was taken, two years later.
- 06
Bounding a run
Cost ceilings, loop detection, and failing closed on stale data.
- 07
Enterprise integration
Identity, workflow and the systems that already have owners.
Changelog
- v1.2Reversibility promoted to its own hub.
- v1.1Bounding a run added after a pilot post-mortem.
- v1.0Separated from the AI transformation pillar at its v2.0.
For machine readers
TechArticle and DefinedTermSet markup, a stable citation block, and /llms.txt. Nothing here is gated or paywalled.
Other pillars
The term contract: The build — 91 terms here · The capital — gda.group · The coordination — flashygroup.com. One term, one home.