Cells
Theseus and Cells: separation of concerns
A new strategy page draws the line between the developer platform and the infrastructure architecture — what each owns, and the contract between them.
Platform bindings
One declarative interface, resolved per deployment target — and the rules for the Enterprise Platform Binding.
Pass application configuration via Fairway
Declare app config once in your Fairway manifest and let every environment deliver it — a ConfigMap in-cluster, a baked profile on Runway, per-cell values on Cells.
Feature Flag Strategy in Theseus
An overview of how feature flags will operate in Theseus for application developers
Modular feature test isolation
Test every modular feature against its contracts: fakes for service dependencies, real infrastructure from Caproni, and no spun-up world.
Co-located Grafana dashboards
Dashboards are part of the service: jsonnet in the service repo, compiled in CI, shipped in the Helm chart, and discovered by whatever Grafana lives in the cell.
Separation of Concerns Between Theseus and Cells
Where the developer platform ends and the infrastructure architecture begins: what Theseus owns, what Cells owns, and the contract between them.