For those who are interested in seeing all published works on one page here is the master index.
All Field Notes
- A Letter to Forest Service Colleagues: On the Clock That May Have Changed
- AI As an Agent of Agents: Federation’s New Middle Layer
- Architect as Translator: Earplugs in the off-site Data Hall, Briefing at HQ in DC
- Bay St. Louis: Trust Before Logos After Hurricane Katrina
- Business Analysis Center of Excellence – How To Stop Committing Project Malpractice
- Commitment Over Compliance: How Technical Teams Actually Deliver
- Culture As Invisible Spec: Training A Media Specialist For Wildland Fire
- Disaster Response Staging Areas Are The Wrong Time To Start Trust
- Disposable Pixels (UI) On A Durable Substrate
- Documentation as Credibility Infrastructure
- Don’t Build an Army of Conscripts When You Need a Coalition of Allies
- Federation Architecture for Coordination in Heterogeneous Digital Government Ecosystems
- Federation Cannot Anchor Itself – GRUAN and the Hidden Stewardship Layer in Global Observing Systems
- Federation Without Owners: The Slow Failure Mode
- Field Guide: Disconnected Editing Is Not a GIS Feature. It Is a Survival Pattern.
- Field Note: “I already know that” and “I disagree” are learning kill switches
- Field Note: Compass-X Recognition Patterns and Strategic Framing
- Field note: Conway’s law and the burden of federation
- Field Note: Defining “Operator”
- Field Note: Guided Sensemaking Interview
- Field Note: Integration Debt vs Temporal Arbitrage
- Field Note: Loosely Coupled Power Grabs
- Field Note: Rapid Goal Setting For Cross Functional Teams
- Field Note: Snake or Stick?!
- Field Note: Sorting the 20-Year Backpack
- Field Note: The 1790 Farmhouse and What It Taught Me About Stewardship
- Field Note: The Benchtop Fallacy: Why Inventory Is Not Capability
- Field Note: The Carthage Error (When Patience Becomes a Liability)
- Field Note: The Gift of Weaponized Compliance
- Field Note: The Human Cost of Interoperability (and the Legal Cost of Speed)
- Field Note: The Integration Confusion Stumbling Block
- Field Note: The Lab and the Line
- Field Note: The Stamp Fallacy at the Interface
- Field Note: The Symbol Is Not the Signal
- Field Note: The Wrong Tools for the Right Problem
- Field Note: When Everyone Uses the Same Words But Means Different Things: Why Integration Fails When Vocabulary Collapses
- Field Note: When You Call a Committee a Team
- Field Notes – The Pre-Shoot Ritual: How To Lower Friction For High-Stakes Video
- Field Notes: What I Learned Writing The Government Video Guide
- Field Notes: What The Katrina Book Was Really For
- Field Notes: What The Mobile Mapping Unit Taught Me About Forward-Deployed Systems
- Field Notes: Why Facts Don’t Change Minds: Motivation And Story Frameworks For Leaders
- Flying The Picture: What A Little Cessna Taught Me About Mission Systems
- Gates That Matter: Task Books, Checkrides And Real Safety
- Golden Datasets: The Tracks Everyone Trusts
- Guarding the Room: A Hubbard Brook Story About Science and Funding
- Guardrails, Not Gates: Designing Systems That Bend Without Breaking
- Hoover Dam Lessons: “Proudly Maintained By Mike E.”
- How Wildland Fire Actually Moves: A Guide To The Three Tier Dispatch System
- Human Contracts Under The Air Picture
- Interfaces Break First: Designing For Partial Truth
- Living With Incomplete Pictures: Notes From High Tempo Systems
- Model vs. Terrain: Bridging the Interface Void on the Merritt Parkway
- No Amount of Federation Saves a Broken Anchor Point
- Pattern-Matching as Operational Knowledge: Why Expertise Requires Documentation
- Proudly Maintained: Why Systems Need A Nameplate
- Reclaiming the Right to Orchestrate: Decision Altitudes and Why Your Chisel Doesn’t Give You the Right to Judge My Output
- Regime Recognition and the Cost of Asymmetric Errors: When Post-Hoc Learning Beats Theory-First
- Respect The Envelope: Why Legal Is Not Always Safe
- Roles As Protocols: Task Books And Swappability In Crisis
- Schema as Sovereignty Subtitle: Why Federated Systems Fail at the Seams
- Seeing the Dragon: The Magic Eye of Modern Governance
- Series Guide: Ground Truth, Federation, and the Anchor Point
- Session Hijacking in 1999: What A URL Bug Taught Me About Trust Models
- Sphere and Spikes: Building What You Need Without Becoming a Specialist
- Stranded in Vienna, Responsible in Kyiv
- Switching Costs Can Delay Departure, But They Cannot Manufacture Consent.
- Systems Built On Heroics Are Brittle
- The Audition Trap: Why Panel Interviews Create False Negatives in Hiring
- The Compass-X Protocol: Mapping the Unknown After the Grid Goes Down Category
- The Disconnected Oracle: Local Inference Patterns for DDIL
- The Loudest Listener: When Interviews Become Something Else
- The Lysine Contingency: How the Internet Stopped Being Meritocratic (And Which Game You’re Actually Playing Now)
- The New Guidance: On Waiting, Agency, and the Clock That May Have Changed
- The Repeat Oblique: When You Cannot Wait for a Golden Dataset
- The Scalpel vs. The Swiss Army Knife: When Solo Integration Beats Federation
- When Data And Applications Divorce: Separating The Two Without Tearing The System Apart
- When the Ground Moves: Why Institutions Misread Their Own Sensor Metrics
- When You Become The Interface: A System “Tell” In Disguise
- When You Cannot Force Compliance: iCAV, Hurricane Katrina, And Lessons In Federation
- When You Choose Integration over Federation On Purpose
- Who Are You to Speak? How Cultural Gatekeeping Silences Federal Expertise (Even When Legally Permitted)
- Why I Kept Quiet: A Field Note on the Stewardship of Operational Knowledge
- Why Ledger/Visibility Collapse is everywhere in 2026
- Why This Site Has Four Navigation Systems
- You Remember My Values, But Not Yours
All Doctrine Guides
- ANNEX A. Human Contracts
- ANNEX B. Data Contracts
- ANNEX C. Interface Ownership Model
- ANNEX D. Decision Altitudes Model
- ANNEX E. Prevention–Contingency Matrix
- ANNEX F. Pattern Library
- ANNEX G. Leadership Doctrine
- ANNEX H. Architecture Doctrine
- ANNEX I. High Visibility Workflows
- ANNEX J. System Evolution and Drift Management
- ANNEX K. System and Workflow Profiles (Case Studies)
- Annex L: The Rosetta Stone for Data Teams: Bridging the Gap Between Technicians and Executives
- Doctrine 01 Companion: Choosing Federation or Integration
- Doctrine 01 Companion: Federation and Integration as Endpoints, Not Destinations
- Doctrine 01: Federation vs Integration in Mission Networks
- Doctrine 02: Distributed Decisions Increase Alignment, Speed, and Resilience
- Doctrine 03 Companion: Constraints: bidirectional translation: Compression vs Construction
- Doctrine 03 Companion: ITIL 4 Foundation: A Practitioner Crosswalk
- Doctrine 03 Companion: Ledger/Visibility Collapse
- Doctrine 03 Companion: The FrameGate Check for Pre-Commitment Interface Integrity
- Doctrine 03 Companion: The Interface Void
- Doctrine 03 Companion: The RS-CAT Framework: Converting Raw Recall into Teachable Principle
- Doctrine 03 Companion. How important conversations get killed at the first correction (The Ackshually Gate)
- Doctrine 03: Interfaces Are Where Systems Break, So They Require Stewards, Contracts, and Ownership
- Doctrine 04: Useful Interoperability Is the Goal, Not Perfect Interoperability
- Doctrine 05: Innovation Must Live at the Edge, Not in the Center
- Doctrine 06: A Two-Lane System Protects Stability and Enables Evolution
- Doctrine 07: Clear Intent Matters More Than Perfect Data
- Doctrine 08: Clear Intent Compresses Ambiguity, Reduces Conflict, and Accelerates Action
- Doctrine 09 Companion: Artifacts Over Adjectives
- Doctrine 09: Decision Drag Is the Enemy of Mission Tempo. Architecture Is the Remedy
- Doctrine 10 Companion: Span of Control and Cross Training Are Load-Bearing Constraints
- Doctrine 10: Degraded Operations Are the Normal Mode, Not the Exception
- Doctrine 11 Companion: Agency vs. Outcome
- Doctrine 11: Preventive Action and Contingent Action Must Both Be Designed Intentionally
- Doctrine 12: Resilience Is an Emergent Property, Not a Feature
- Doctrine 13: Problem Solving Requires Finding the Real Deviation and the Relevant Change
- Doctrine 14: Technical Debt Is a Leadership Signal, Not a Coding Failure
- Doctrine 15 Companion: Activity vs. Outcome
- Doctrine 15: Architecture Must Accelerate Teams, Not Bottleneck Them
- Doctrine 16: Portfolio Thinking Ensures Effort Aligns With What Actually Matters
- Doctrine 17: Architects Translate Strategy Into Engineering and Engineering Into Strategy
- Doctrine 18: Commitment Outperforms Compliance in High Trust, High Tempo Environments
- Doctrine 19: Supervision, Management, and Leadership Are Three Different Jobs. Confusing Them Breaks Systems
- Doctrine 20: Golden Datasets: Putting Truth In One Place Without Pretending Everything Is Perfect
- Doctrine 21 Companion: Claims, Roles, and Entitlements in Microsoft 365
- Doctrine 21: Zero Trust Is A Trust Model, Not A Card “Type”
- Doctrine 22: When “It Depends” Is the Right Answer: How to Think in Probabilities Under Uncertainty
- Doctrine 23: Loop Closure as Load-Bearing System Infrastructure
- Doctrine 24 Companion: The Conflict Buffer
- Doctrine 24 Companion: The Eight Capture Mechanisms
- Doctrine 24: Stewardship Places the Burden on the Steward, Not the Parties
- Field Report: College Financing and the 5-Year Home Runway
All Site Pages
- Cart
- Checkout
- Contact
- Dashboard
- Diagnostics – Scenario-based Decision Exercises
- Doctrine: Patterns for Resilient Systems
- Encyclopedia
- Evaluators & Editors Start Here (2-minute read)
- FAQ
- Federation Without Owners: An Interface Stewardship Lab for Cross-Boundary Ecosystems
- Figure Library
- Global Library
- HOW I GOT HERE
- Interface Stewardship: The Audio Library
- Interpreter Kit
- Learner Registration
- Privacy Policy
- Route Finder
- Routes
- Start Here: Introductions
- Thanks
- The Interface Stewardship Newsletter
- The Next Guys: Field Notes on Operational Architecture
- The Sovereign Seam
- Tutor Certificate
- Workshops
Term list / Tags
- Academic conditioning
- After action review
- Agenda control
- AI agents
- Air operations
- Airborne collection
- Airspace management
- Aviation
- Bay St. Louis
- C4ISR
- Calibration validation
- Career
- Civil-military coordination
- Civil-military emergency preparedness
- climate-data-records
- Command and control
- Commitment over compliance
- Compass-X
- Complex systems
- Culture as spec
- Data architecture
- Data contracts
- Data integrity
- DDIL
- Decision altitudes
- Decision latency
- decision rooms
- Decision support
- DHS
- Disaster response
- Doctrine in practice
- Doctrine origins
- Earth observation
- Emergency management
- Emergency procedures
- Environmental science
- Experimental forest
- Failure modes
- Featured
- Federal workforce
- Federation
- Federation architecture
- Field notes
- Fire and aviation management
- Fire aviation
- Fit for purpose
- Forest Service
- Former Warsaw Pact
- Forward deployed architect
- Funding pitches
- Gates
- GIS
- Golden datasets
- Governance without authority
- Ground truth
- Guarding the room
- Guardrails
- Guardrails over heroics
- High consequence environments
- High tempo systems
- Hoover Dam
- Hubbard Brook
- Human contracts
- Hurricane Katrina
- iCAV
- Iceland ash cloud
- ICS
- Incident dispatch
- Infrastructure
- Institutional change
- Integration
- Interface stewardship
- Interfaces
- Knowledge management
- Kyiv
- Latency budgets
- Lead plane
- Leadership
- Limited slack
- Local government
- Long-term research
- Media tradecraft
- Meeting strategy
- Mission assurance
- Mission systems
- Mobile mapping unit
- Moldova
- Mutual aid
- Narrative infrastructure
- NWCG
- observing-systems
- Operational doctrine
- Operational resilience
- Operations
- Over-functioning
- Ownership
- Pattern matching
- Pattern-provisional
- Pilot training
- Portfolio thinking
- Positioning
- Procurement
- reference-networks
- Remote sensing
- research funding
- Resilience
- Resource coordination
- Responsibility
- Responsibility vs authority
- RF engineering
- Rhode Island USAR
- Risk management
- Safety culture
- Safety optics
- Science communication
- Science is mute
- Science storytelling
- Scientific continuity
- Situational awareness
- Sovereignty
- Stakeholder communication
- Stakeholder management
- Stewardship
- Strategy
- Switching Costs
- Systems architecture
- Systems Thinking
- Technical debt
- Time series
- Travel disruption
- Tribal partners
- Trust
- USACE
- Useful interoperability
- Values in practice
- Vienna
- VoIP
- Voluntary adoption
- Volunteer
- Wildland fire
- WiMAX
- Workflows