RFC 004 — Common Control Plane

Approved Normative Depends: RFC 001, RFC 002

• Tracking ticket: platform/kortex/backlog/done/004-rfc-common-control-plane.md
• Depends on: RFC 001 — Ecosystem Map (Approved), RFC 002 — Architecture (Approved)
• Companion: RFC 003 — Common Event Schema (in flight) — defines the koder.admin.action audit event emitted by every mutation
• Unblocks: RFC 006 — Auto-remediation Rules Engine
• Generalises: infra/jet RFC 001 §12.1 (Admin endpoint port — separate listener)

1. Summary

Kortex is the coordination layer above the Koder ecosystem (RFC 001). To coordinate, it must do two things: sense what the products are doing, and act on them when policy says so. RFC 003 standardises the sensing side by unifying the event schema. This RFC standardises the acting side.

The proposal is small but binding: *every Koder product that runs as a long-lived process MUST expose a [server.admin] listener bound to 127.0.0.1:9080 by default, serving a fixed set of REST/JSON endpoints under `/admin