Introduced by a trusted connector?
The Practitioner Archive is live. Explore the ungated framework for fixing broken systems and operational architecture.
Introduced by a trusted connector?
Throughout this doctrine, I've presented federation and integration as distinct approaches. This binary framing is pedagogical, not absolute. Real coordination exists in messy middle, shifting across temporal, spatial, and organizational dimensions.
Federation and integration aren't architectural preferences or style choices. They're structural requirements determined by authority (can you compel compliance?) and value distribution (does standardization serve entities as well as local optimization?). Choosing the wrong model creates predictable coordination failures regardless of implementation quality.
When Coordination Offices Absorb Unresolved Tensions Rather Than Clarify Ownership Companion to: Educational Diagnostic #5 (The Conflict Buffer), Doctrine 24: Stewardship Places the Burden on the Steward, and Doctrine 03: Interfaces Are Where Systems Break. Core insight: Coordination offices are often positioned to absorb blame for coordination failures that stem from stakeholder unwillingness to engage,...
Coordination offices measure activity (meetings held, attendance rates, documents produced) while decision latency increases and stakeholder satisfaction decreases. The coordination infrastructure looks busy but doesn't improve coordination outcomes.
Coordination offices require structural independence to coordinate neutrally across stakeholders. But multiple dependencies on one dominant stakeholder create compound capture that makes neutral coordination impossible.
How reciprocal relationships appear one-sided when contributions become invisible Ledger/Visibility Collapse is when selective accounting makes reciprocal relationships appear one-sided by making some contributions visible while others become structurally invisible. This is not about one party being ungrateful or exploitative (though it can become that). This is about which items appear on the ledger and which items disappear into baseline.
The "Ackshually" Gate is the moment a conversation gets diverted from the real question to a technically correct but strategically useless correction. It is not necessarily lying. It is not necessarily bad faith. It is a conversational choke point that reliably prevents people from reaching the higher-resolution model they actually need. It shows up everywhere: economics, medicine, policy, risk, and governance.
Most downstream failures are frame entry failures, not execution failures. FrameGate enforces five minimal capture tags before commitment: Decision Owner, Objective, Evaluation Mode, Risk Posture, and Time Horizon. If two or more tags are undefined, the only valid action is frame clarification. This prevents helpful people from getting trapped in obligations they never consented to, and it creates instrumented action that RS-CAT can extract patterns from. FrameGate doesn't slow action. It prevents misaligned action
Organizations optimize for efficiency. Leaders optimize for performance. Stewards optimize for preservation of mission-critical capability.
Doctrine Companion to Decision Altitude There is a quiet lie that shows up in a lot of org charts and LinkedIn profiles. We act like skills live in adjectives. These words float near job titles and performance reviews. They are rarely tied to anything you can point at. If your skill only exists as an...
Anthony Veltri · Enterprise Architect (Interoperability + Governance) · Designing decision infrastructure for cross-boundary ecosystems. · Introductions