Theseus and Cells: separation of concerns

A new strategy page, Separation of Concerns Between Theseus and Cells, draws the line between the two efforts explicitly:

• Theseus owns how a modular feature is built, packaged, instrumented, and shipped — ending at a self-describing Helm chart.
• Cells owns where that chart runs and the values it runs with — the tenant model, ring rollouts, routing, and per-cell configuration delivery.
• The platform bindings model is the contract between them, with two rules keeping it honest: application code never knows which cell it is in, and services are designed for absence.

The page also lists the anti-responsibilities on both sides and the open ownership questions still being settled. If you have ever asked “is this a Theseus problem or a Cells problem?”, this is the page to bookmark.