Prompt & Configuration Registry  ·  View 02 of 21  ·  Context and scope

High-Level Architecture

Six stages from a person editing a sentence to an answer that carries the digest that produced it.

Editable source SVG draw.io All views
Author Registry Console React CLI & Git sync Forgejo Review & rationale Build Flatten fragments Schema & policy Digest & sign SHA-256 Release Gates & approvals Environment pointer etcd Rollout & experiment Distribute Artefact store OCI registry Change bus NATS JetStream Poll backstop 30 s Resolve Resolver SDK in the app process Resident bundle verified, ≤ 2 MB Assignment function pure, no lookup Prove Exposure pipeline Kafka → ClickHouse Experiment readout Audit ledger WORM, 7 years exposure every verdict Prompt & Configuration Registry — High-Level Architecture Application we own Security / platform Decision point Data store Queue / topic event / async The only thing crossing from Release to Resolve is an immutable signed bundle and a pointer to it. v 1.0 · owner Platform Architecture · d 2026-09

The shape

  • Author → Build → Release → Distribute → Resolve → Prove. The first three are human-paced and transactional; the last three are machine-paced and eventually consistent.
  • The join between Release and Distribute is the only place state crosses planes, and it carries exactly two things: a content-addressed bundle and a pointer naming which bundle is current.
  • Prove is not an afterthought stage. Without the digest recorded on the answer, nothing earlier in the chain can be verified after the fact.

Why it is drawn this way

  • Validation sits in Build, never in Resolve. A resolver able to reject a malformed bundle is a resolver able to fail a request.
  • The poll backstop appears beside the change bus deliberately: the poll is what guarantees convergence, the notice only makes it fast (ADR-05).
  • Assignment sits inside Resolve, not beside the experiment controller, because it is a pure function and reads nothing (ADR-09).

Deliberate omissions

  • The evaluation service, the identity providers and the secret store are drawn on views 01, 07 and 20 rather than here — this view is about the path a change takes, not the estate.
  • Rollback is not a seventh stage. It re-enters at Release with an older digest and takes the same path (ADR-04).
◀  System Context All views Actors and Their Core Journeys  ▶
Solution Architecture v1.0 · open source, self-hosted on Kubernetes · Platform Architecture · 2026-09 · 21 views · 17 architecture decision records02-high-level-architecture