# Research: Radius Platform on Kubernetes

> For the complete documentation index, see [llms.txt](https://deploy-preview-472--lucky-concha-f3599f.netlify.app/llms.txt).

## Objective

Define the transition from state `012` to `013` by layering Radius platform capabilities on Kubernetes.

## Inputs Reviewed

*   `spec.md`
*   `plan.md`
*   `tasks.md`
*   `system/architecture.md`
*   `system/runtime-topology.md`

## Key Decisions

1.  Preserve Kubernetes runtime semantics from state `012`.
2.  Introduce Radius as a platform abstraction without changing core business flows.
3.  Keep generated state publishability and compareability with predecessor state.