Consortium starter pipeline — ceremony orchestrator + governance UI
CeremonyOrchestrator: GenServer providing a PubSub broadcast interface for ceremony status changes. LiveView subscribes to these broadcasts for real-time updates. A K8s CRD watcher will feed events into this in a future sprint; for now the init log makes the stub state explicit. Chronicle.Consumer: stub for the Ops DB projector that will consume Chronicle events and hydrate the Ecto tables. Projector design (idempotent, checkpointed, catch-up on restart) per DESIGN-OPS-DB-CHAIN-OF-CUSTODY-0001 §2.5. Both modules document the orchestrator/engine distinction: guildhall orchestrates, substrate decides. Both are now supervised by their respective application trees (Guildhall.Orchestrator.Supervisor, Guildhall.Chronicle.Supervisor). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Signed-off-by: Tyler J King <tking@guildhouse.dev> |
||
|---|---|---|
| apps | ||
| config | ||
| .formatter.exs | ||
| .gitignore | ||
| AGENTS.md | ||
| mix.exs | ||
| mix.lock | ||
| README.md | ||
Guildhall
TODO: Add description