Control Center

Purpose

A self-hosted estate accumulates services faster than it accumulates any coherent way to operate them. Control Center is an attempt to give that estate one operating surface without turning it into one monolith.

The intended operator is the person who has to keep the estate running.

Operating model

Each capability is a module with a declared interface. The platform knows what a module claims to provide and what authority it needs; it does not know how the module works internally, and it does not need to.

State is read from the services themselves rather than from a configuration file describing what they were supposed to be. The difference between intended state and live state is treated as information, not as an error to be smoothed over.

Practices

Observe is the live-state read that keeps the surface honest.

Model is the module interface — an explicit statement of what each part is and what it is responsible for.

Control is where authority is granted. A module receives what its declared interface requires and nothing beyond it.

Protect is the consequence: a compromised or misbehaving module is bounded by what it was granted rather than by what it could reach.

Architecture

Modules, a platform that composes them, and an authority model between the two. That is as much as is published, and deliberately so.

The rejected shortcut was a single privileged process that could reach every service. It is easier to build and it removes the only boundary worth having.

Evidence

The repositories are private and the infrastructure is not published. This record describes the module and authority model; it is not an inventory of what is running or where.