In 2009, DevOps named something that had been bothering technologists for years: the wall between people who write software and people who run it. Development threw code over the wall. Operations caught it — or didn't. Incidents were blamed on the other side. Nobody owned the full picture.
DevOps demolished that wall. It introduced shared ownership, infrastructure as code, continuous integration, continuous delivery, and observability. It changed how software gets built and deployed. It's arguably the most impactful organizational transformation in technology history.
But it only broke one wall.
The Other Walls
Look at any enterprise and you'll find walls everywhere:
- IT and Finance — Budget cycles that don't match delivery cycles. Cost allocations that don't reflect actual consumption. FinOps tried to bridge this for cloud; the rest of the enterprise is still siloed.
- Operations and Compliance — Regulatory requirements documented in Word files that don't connect to the systems they regulate. Auditors who check point-in-time snapshots instead of continuous compliance.
- Strategy and Execution — OKRs in one system, project plans in another, delivery metrics in a third. The connection between "what we decided" and "what we did" is maintained in someone's head.
- Vendors and Institutional Knowledge — When a contract expires, the operational knowledge embedded in that vendor's platform goes with them. The organization loses memory every renewal cycle.
- Divisions and Business Units — Each division runs its own systems, defines its own terms, and reports its own metrics. The same concept — "customer," "policy," "case" — means different things in different parts of the organization.
The DevOps Playbook, Generalized
OACIS takes the DevOps playbook and applies it beyond software delivery:
If version control works for code, why not for organizational policy? If CI/CD works for software, why not for compliance? If observability works for servers, why not for the organization itself?
Version control — Every assertion in the knowledge graph is versioned. You can diff the organization at any two points in time. Who changed what, when, and why.
Continuous integration — Pipelines that continuously ingest data from across the enterprise, validate it, normalize it, enrich it with ontology terms, and merge it into the knowledge graph. New information is integrated automatically — not batch-processed quarterly.
Observability — Dashboards, alerts, and queries that show the state of the organization, not just the infrastructure. "Show me all contracts expiring in 90 days where the vendor provides more than three services and no knowledge transfer plan exists." That's organizational observability.
Infrastructure as Code — The organization's structure — roles, responsibilities, reporting lines, process dependencies, regulatory mappings — defined in machine-readable, version-controlled formats. Not PowerPoint. Not Visio. Not someone's mental model.
The Last Unmanaged System
We have monitoring for every server. Alerting for every application. Dashboards for every microservice. But the most complex, most expensive, most consequential system — the organization itself — has no observability at all.
DevOps fixed the dev/ops wall. OACIS fixes the rest.
This post draws from Part Two: The Discovery and Chapter 6: The DevOps of Everything of Organizations as Code: The Intelligent System Revolution.
← Back to Blog