Prompt & Configuration Registry  ·  View 06 of 21  ·  Structure

Layered Architecture

Seven layers, and one of them lives inside somebody else's process.

Editable source SVG draw.io All views
Experience Registry Console React CLI Git sync Forgejo Config API Go Release control Gate engine Pointer controller Experiment controller Audit writer Build & seal Fragment resolver Schema & policy Secret scanner Signer OpenBao Distribution Artefact store OCI registry Object store MinIO Pointer store etcd, linearisable Change bus NATS JetStream Resolution Resolver SDK Go · Python · TS Resident bundle Targeting evaluator Assignment function Evidence Exposure collector OpenTelemetry Buffer Kafka Exposure store ClickHouse Audit ledger WORM Platform Kubernetes Keycloak SPIRE OpenBao key custody Prometheus promote pointer write change notice exposure Layered Architecture Application we own Interface / broker Decision point Security / platform Data store Queue / topic synchronous event / async Resolution sits inside the application process. Nothing in it calls anything above Distribution. v 1.0 · owner Platform Architecture · d 2026-09

The unusual layer

  • Resolution is not a tier of this platform. It is a library compiled into ~300 applications the platform does not own and cannot restart.
  • Everything about the design follows from that: resolution must be upgradeable slowly, must hold no state it cannot rebuild, and must never need anything above Distribution.
  • Evidence is drawn below Resolution rather than beside it, because exposures flow out of the application, not out of the registry.

Assumptions

  • Three SDK languages cover the estate — Go, Python and TypeScript (stated assumption). A fourth language changes the calculus in ADR-02 materially.
  • Bundle size stays under 2 MB compressed per environment, which is what makes a fully resident bundle affordable per pod.

Risks

  • SDK upgrade lag. A targeting-logic bug is fixed at the speed the slowest team redeploys, which may be months. ADR-02 records the sidecar alternative and the condition that would flip it.
  • Three implementations of the same resolution contract is three chances to diverge. Mitigated by a shared conformance suite, which is a cost this view does not show.
◀  Journey — Rolling Back at 3am All views Platform Components  ▶
Solution Architecture v1.0 · open source, self-hosted on Kubernetes · Platform Architecture · 2026-09 · 21 views · 17 architecture decision records06-layered-architecture