Tyler J King
4e22729bef
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>
21 lines
424 B
Elixir
21 lines
424 B
Elixir
defmodule Guildhall.MixProject do
|
|
use Mix.Project
|
|
|
|
def project do
|
|
[
|
|
apps_path: "apps",
|
|
version: "0.1.0",
|
|
start_permanent: Mix.env() == :prod,
|
|
deps: deps()
|
|
]
|
|
end
|
|
|
|
# Dependencies listed here are available only for this
|
|
# project and cannot be accessed from applications inside
|
|
# the apps folder.
|
|
#
|
|
# Run "mix help deps" for examples and options.
|
|
defp deps do
|
|
[]
|
|
end
|
|
end
|