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
Platform Governance

Platform Governance as a Control System in Multi-Cluster Kubernetes

Does it really matter? Let’s explore five items and try to answer that question. 1. Multi Clusters 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. The cost is measurable. Undetected configuration drift increases incident blast radius. Inconsistent RBAC baselines extend audit preparation from days to weeks. Clusters onboarded without active policy enforcement create compliance blind spots that accumulate silently. ...

February 26, 2026 · 5 min · 1036 words · Andre Rocha