Steward
The estate operator
StatusBuildIn build
Where it stands. In build: its estate-event recorder runs today; the acting-operator tier that writes is still ahead.
01What it does
01
Holds the infrastructure the suite runs on
Steward provisions, patches, backs up and keeps healthy the infrastructure the suite runs on, the standing operational job nothing else owns.
02
Its own tool, so Helm need not carry it
Kept separate from Helm on purpose: Helm dispatches the work, Steward keeps the ground it runs on standing.
02Its place on the control plane
Actuate is the only plane that writes, and Steward shares it with Helm. Helm reaches out to dispatch governed work; Steward turns inward to keep the estate that work depends on healthy. Neither carries the other’s job.
03Who it works with
A pairing here means two tools actually exchange something, and the thing they exchange is named.
- ConsoleFeedsReports estate health/activity through the same telemetry contract
- HelmGates (raises repo changes to)An estate need requiring a repo commit is raised by Steward and dispatched by Helm under policy
- WardOperates (module of)Ward is the credential-custody module living inside Steward's own repo
- GimbalOperates (sibling optimiser)Same tooling-tier posture (autonomous, focused, reporting to Console), different estate
- FathomConsumesDesigned consumer for estate-health reads over the live databases
- ConcordGatesSteward's own spec↔code pairing is Axis-A scope like any other tool
04Where it does the work
Others on the actuate plane