This week, five organizations in New Zealand and Australia posted jobs titled "AI Governance" — not AI Strategy, not Enterprise Architecture. Here is what those job descriptions are missing, and how AIDRA fills the gap.
AI-native team redesigns keep adding new job titles and calling it done. The actual failure mode sits at the decision boundary. Here is what changes when you apply AIDRA to team design instead of headcount.
Decision rights models assume human decision-makers. AI agents breach that assumption silently. Here is how to extend decision rights to cover autonomous actors before the first ungoverned decision becomes a production incident.
Security is treated as a gate at the end of delivery. It should be an architecture property designed into three distinct boundaries. Here is the model that fixes the friction between security and delivery.
The architecture fitness function literature solved code-level governance. It never made the claim that the board itself becomes optional. Here is the missing argument — and the economics that prove the board is the slower and more expensive option.
Most platform teams build internal products their engineering teams never chose. Platform adoption is not a marketing problem. It is a product governance problem. Here is the model that fixes it.
Most organizations evaluate private cloud and HCI platforms by running a technical POC. The POC passes. The platform fails. The reason is structural — and fixable. The Platform Fitness Evaluation Model (PFEM) tells you what to measure instead.
Enterprise architecture maturity is not a feeling. It is a score. Organizations that cannot measure their architecture maturity cannot improve it. The EAMS model gives you the score.
One ADR template does not fit every architectural context. Five purpose-built variations — for standard decisions, agentic AI, cross-domain impact, fast delivery, and high-risk reversals — plus governance automation to make the system run without manual follow-up.
Most enterprises build data architectures one layer at a time. Business, logical, and physical layers exist as separate artefacts owned by separate teams. That separation is the structural gap that makes data estates ungovernable.