Search across everything I write and publish.
This page pulls together doctrine, guides, blog posts, field notes, and other artifacts into one place. Use the search bar to look up a phrase or idea, and the content-type filter to toggle between deep-dive doctrine, shorter reflections, and more informal notes. If you’re trying to connect dots across topics – portfolio, architecture, family, training, systems – this is the fastest way to see how it all fits together.
Visual language
Pages use a small colored bar under the header as a quick orientation cue.
- Gold is for doctrine – the core principles and patterns.
- Green is for Field Notes – stories, experiments, and examples from the field.
- Blue is for services – capability statements and ways we can work together.
- Red is for Routes – guided paths when you are under pressure and need traction
The goal is to make it easy to see whether you are reading philosophy, practice, or an offer.
The Next Guys: Field Notes on Operational Architecture
FIXING BROKEN SYSTEMS A practitioner archive on surviving technical debt The archive is ungated. No email required. On a construction site or a factory floor, leaving a mess for “the next guys” is an obvious…
Field Note: The Wrong Tools for the Right Problem
Why Your PM Toolkit Breaks Down in Federated Environments, and What to Use Instead Domain: Federation Architecture / Interface Stewardship Author: Anthony Veltri | anthonyveltri.com Related Doctrine: Doctrine 24: Stewardship Places the Burden on the…
Interface Stewardship: The Audio Library
Operational knowledge in spoken format. Comprehensive narration of the Federation Architecture Doctrine: 25 volumes, 76+ field notes, and companion pieces covering multi-jurisdictional coordination, federation architecture, and decision infrastructure. Subscribe to receive new pieces automatically as…
Don’t Build an Army of Conscripts When You Need a Coalition of Allies
Stakeholder Engagement Architecture for Federated SystemsAudience: Enterprise architects facing impossible stakeholder roles, and leaders trying to understand why “leaning harder” destroys the relationships they’re trying to build Scene You’re the stakeholder coordinator for a federal…
Who Are You to Speak? How Cultural Gatekeeping Silences Federal Expertise (Even When Legally Permitted)
This note covers the internal silencing mechanisms: cultural gatekeeping, legal confusion, organizational centralization, and more. In federal service, you take the king’s coin and you become the king’s man. The salary, the benefits, the pension…
The Lysine Contingency: How the Internet Stopped Being Meritocratic (And Which Game You’re Actually Playing Now)
The modern internet is a lysine contingency. You can build something real; you can do excellent work; you can publish it openly; and it can still die outside the park unless you receive the required…
Federation Without Owners: An Interface Stewardship Lab for Cross-Boundary Ecosystems
Reduce or eliminate decision drag at cross-boundary seams when you cannot compel partners to align.This lab surfaces the seam risk you are currently paying for invisibly, then crystallizes it into decision rights, pause authority, and…
Doctrine 01 Companion: Federation and Integration as Endpoints, Not Destinations
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.
Badge-Function Mismatch – When the badge is bigger than the job, the badge is doing work
Here’s a quick way to spot an early escalation pattern without getting sucked into politics. Sometimes the job is basically “support” work: vetting, analysis, coordination, ops-room help, liaison. That kind of work can be done…
Doctrine 01 Companion: Choosing Federation or Integration
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…
Diagnostic #6 Exercise: Federation or Integration
Testing ability to choose the right coordination model for your structural reality Overview This diagnostic tests whether you can determine when federation (loose coupling, strong interfaces) versus integration (tight coupling, shared standards) is appropriate for…
Diagnostic #5 Exercise: The Conflict Buffer
Testing recognition when you’re absorbing blame for stakeholder failures Overview This diagnostic tests whether you can recognize when you’re being used to absorb unresolved tension rather than clarify ownership. You’ll see 10 scenarios where coordination…
Diagnostic #4 Exercise: The Budget Proximity Trap
Testing recognition of coordination capture by dominant stakeholders Overview This diagnostic tests whether you can recognize when your coordination office is becoming aligned with one powerful entity rather than maintaining independence across all stakeholders. You’ll…
Diagnostic #3 Exercise: The Meeting Proliferation Problem
Testing recognition when coordination infrastructure slows decisions instead of enabling them Overview This diagnostic tests whether you can recognize when coordination infrastructure is slowing decisions rather than enabling them. You’ll see 10 scenarios where meetings…
Diagnostic #2 Exercise: The Escalation Sink (Deputization Without Authority)
Testing recognition of deputization without authority to compel compliance Overview This diagnostic tests whether you can recognize when you’re being deputized without the authority to compel compliance or make binding decisions. You’ll see 10 scenarios…
Diagnostic #1 Exercise: The Template Trap
Testing recognition when pre-packaged solutions prevent custom coordination architectures Overview This diagnostic tests whether you can recognize when pre-packaged coordination solutions (templates, frameworks, playbooks) force integration thinking on federation problems. You’ll see 10 scenarios where…
Doctrine 24 Companion: The Conflict Buffer
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….
Doctrine 15 Companion: Activity vs. Outcome
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.
Doctrine 24 Companion: The Eight Capture Mechanisms
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.
Diagnostics – Scenario-based Decision Exercises
Scenario-Based Decision Exercises for Governance & Coordination Roles These diagnostics test your ability to recognize common coordination failure modes before they become structural problems. Each diagnostic presents scenarios drawn from NATO, federal agencies, corporate governance,…
Field Note: The Stamp Fallacy at the Interface
Approval predicts compliance. It does not certify legitimacy. “It had legal clearance.” Someone says it with finality. Higher headquarters approved it. The lawyers signed off. There’s a memo. A stamp. Closure. You feel relief. A…
Why Ledger/Visibility Collapse is everywhere in 2026
Field note on a pattern showing up in geopolitics, consulting, and personal relationships simultaneously
Doctrine 03 Companion: Ledger/Visibility Collapse
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…
Doctrine 03 Companion. How important conversations get killed at the first correction (The Ackshually Gate)
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…
Doctrine 03 Companion: The FrameGate Check for Pre-Commitment Interface Integrity
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,…
Schema as Sovereignty Subtitle: Why Federated Systems Fail at the Seams
Interoperability is not about connecting wires. It is about Semantic Sovereignty. It is the boring, difficult work of agreeing on what words mean before you write a single line of code. Most federation projects fail…
The Disconnected Oracle: Local Inference Patterns for DDIL
The Observation: Intelligence Without the Pipe We currently treat Artificial Intelligence as if it were a utility, like water or electricity. We assume the “brain” lives in a data center in Virginia and that our…
The Compass-X Protocol: Mapping the Unknown After the Grid Goes Down Category
In stable environments, we navigate by “Instrument Flight Rules.” We trust the dashboard. We trust the map. We trust that the blue line on the screen matches the road on the ground. In a crisis,…
Field Note: Loosely Coupled Power Grabs
There is a structural gap in how we analyze power. People demand a single coordinating memo, a single smoking gun, a single mastermind. If they cannot prove centralized orchestration, they treat patterns as coincidence or…
Route Finder
Navigate 24+ Doctrine volumes, 60+ Field Notes, and 500+ diagrams withhelp from an AI guide trained on the complete corpus. Every answer includes links to the exact sources I’m citing. How To Use This: Tell…
Field Note: When Everyone Uses the Same Words But Means Different Things: Why Integration Fails When Vocabulary Collapses
When you need to federate across sovereignty boundaries, these distinctions stop being academic and become mission-critical. Without this vocabulary, it is almost impossible to diagnose why integration keeps failing even when the connectors work.