Operational Knowledge vs Architectural Knowledge

Observation: Architecture documentation describes how a system was designed. It rarely captures how that system behaves under load, partial failure or prolonged operational pressure. Implication: The gap between designed and observed behavior grows as systems age. Teams that rely on documentation alone inherit risk that has no name in any diagram. Part of the Field Notes series documenting operational patterns observed in real-world platform architectures.

March 7, 2026 · 1 min · 65 words · Andre Rocha
FN-0003
Capybara resting calmly in water

Platform Governance as a Control System in Multi-Cluster Kubernetes

Governance in multi-cluster Kubernetes is treated as a set of policies. Policies are not governance. The control system that propagates, enforces, and reports them is. Policies that are defined but not propagated, propagated but not enforced, or enforced but not reported back are documentation. The system has many ways to fail silently, and each silence accumulates as risk that becomes visible only during audits or incidents. Where Governance Fails Quietly Organizations operating multi-cluster Kubernetes fleets face a structural risk that is rarely discussed in architectural reviews: governance gaps that remain invisible until an audit fails or an incident escalates. ...

February 26, 2026 · 8 min · 1648 words · Andre Rocha