Ceremony orchestrator + governance UI layer over substrate CRDs. guildhall presents and coordinates; substrate decides and enforces. Apps: - guildhall_web: Phoenix LiveView UI for ceremony workflows, Forge visualization, posture dashboards - guildhall_orchestrator: watches CeremonyRequest CRDs, notifies witnesses, collects signatures, tracks ceremony lifecycle - guildhall_ops_db: Ecto schemas for the five Ops DB tables (per DESIGN-OPS-DB-CHAIN-OF-CUSTODY-0001) - guildhall_graph_bridge: Microsoft Graph API reconciler (stub) - guildhall_chronicle: Chronicle event consumer + Ops DB projector (stub) Naming: guildhall components are orchestrators (workflow), NOT engines (enforcement). The ceremony engine is a substrate K8s operator. guildhall coordinates humans around CRDs. Elixir 1.17.3 / OTP 27 / Phoenix 1.8.5. SHA-256 git repo. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Signed-off-by: Tyler J King <tking@guildhouse.dev> |
||
|---|---|---|
| .. | ||
| assets | ||
| lib | ||
| priv | ||
| test | ||
| .formatter.exs | ||
| .gitignore | ||
| mix.exs | ||
| README.md | ||
Guildhall
To start your Phoenix server:
- Run
mix setupto install and setup dependencies - Start Phoenix endpoint with
mix phx.serveror inside IEx withiex -S mix phx.server
Now you can visit localhost:4000 from your browser.
Ready to run in production? Please check our deployment guides.
Learn more
- Official website: https://www.phoenixframework.org/
- Guides: https://hexdocs.pm/phoenix/overview.html
- Docs: https://hexdocs.pm/phoenix
- Forum: https://elixirforum.com/c/phoenix-forum
- Source: https://github.com/phoenixframework/phoenix