Runtime

Parent: Agentic.

Runtime is a thin subcategory for embeddable execution kernels other stacks sit on — cluster orchestration and workload placement rather than full agent frameworks or model servers. Under Agentic it currently currently centers on Kubernetes as the cluster orchestrator many agent and serving stacks assume — the shared execution substrate rather than an agent SDK.

Compare to Frameworks (agent DX) and Serving (token generation): runtime is the cluster fabric. Failure modes: treating the cluster as an agent product, or hiding business state only inside ephemeral actors with no ledger projection.

Prefer this cell when the pack’s primary job is scalable execution substrate. Prefer frameworks when the job is tool-using agents; sandboxes when the job is isolating untrusted code; serving when the job is LLM inference.

Features such as 05-agent-infrastructure-os and Agent Lifecycle Management signal infrastructure under the workforce — measure utilization and failure recovery, not chat demos.

Inline members for audit: Kubernetes. Features: 05-agent-infrastructure-os Agent Lifecycle Management Deployment & Data Residency. Related terms referenced: Frameworks, Code Sandbox, Serving.

For this research catalog the acceptance test is boring and strict: after wiring the pack, can a second person replay the same scenario and get the same measurable outcome? If not, the page is still a brochure. Document the scenario, the expected number, and the log line that proves it. That habit is what separates a deepened taxonomy cell from a landscape screenshot.

Also record what you refused: tools not connected, corpora not ingested, metrics not collected. Refusals keep the cell honest when marketing pages claim universality. A taxonomy essay that only lists winners teaches less than one that names the skip conditions next to the install path.

Keep the essay technical enough that an engineer can argue install order — and short enough that a reader finishes it before opening the right-rail member list. Prefer primary docs and repo evidence over landscape blurbs when the right-rail packs disagree.

Operational discipline for this cell: name the install artifact, the health check, and the rollback. Prefer one golden path documented against a member pack in the right rail over five half-wired demos. When packs disagree, believe the primary repository README and a failing test you can re-run — not the landscape one-liner. Measure latency, cost, and error rate on a frozen scenario before declaring the subcategory “covered.” If you cannot point at a log line that proves the scenario, the essay is unfinished even when the word count clears the audit floor.

Cross-link greedily but honestly: every taxonomy wikilink should change a reader’s next click, and every pack slug should resolve to a real pack. Do not invent members to decorate the prose. Prefer fewer true links over many decorative ones. Keep Monday-shaped typing out of the runtime story; observation and ledger remain senior to any agent UI that retypes reality.