Dependencies

Module boundaries

Enforced at compile time by boundary — a violation fails the build. The macro view (each context is additionally its own sub-boundary inside Relay; see domain.md for the list):

flowchart LR
    App["Relay.Application"] --> Web["RelayWeb"]
    App --> Domain["Relay"]
    Web --> Domain
    Web --> Schemas
    Web --> Dagre["dagre_ex (vendored OTP app)"]
    Domain --> Schemas["Schemas (peer)"]
    Storybook["Storybook"] --> Web

Inside Relay, cross-context deps are declared per sub-boundary (e.g. Events depends on BoardWatch; contexts that notify depend on Events). When adding a context: use Boundary, add it to Relay's exports, and update domain.md.

The graph below is generated from the boundary compiler by mix relay.deps_graph — don't hand-edit between the markers; regenerate instead (mix relay.deps_graph --check verifies it's current).

flowchart LR
    Markdown
    Presence
    Accounts --> Billing
    Accounts --> Config
    Accounts --> Repo
    Activity --> Events
    Activity --> Repo
    AgentLog --> Activity
    Agents --> Repo
    ApiKeys --> Repo
    Attachments --> Boards
    Attachments --> Repo
    Billing --> Config
    Billing --> Mailer
    Billing --> Repo
    Boards --> Activity
    Boards --> Agents
    Boards --> Events
    Boards --> Flows
    Boards --> Repo
    Boards --> Setup
    Cards --> Activity
    Cards --> Boards
    Cards --> Events
    Cards --> Flows
    Cards --> Members
    Cards --> Push
    Cards --> Repo
    Cards --> Setup
    Cards --> Votes
    Events --> BoardWatch
    Events --> Repo
    Examples --> Boards
    Examples --> Cards
    Examples --> Repo
    Flows --> Agents
    Flows --> Repo
    Flows --> Setup
    Members --> Events
    Members --> Repo
    Push --> Members
    Push --> Repo
    Runs --> Activity
    Runs --> Agents
    Runs --> Billing
    Runs --> Boards
    Runs --> Cards
    Runs --> Config
    Runs --> Events
    Runs --> Flows
    Runs --> Repo
    Runs --> Scaffold
    Runs --> Setup
    Setup --> Agents
    Setup --> ApiKeys
    Setup --> Events
    Setup --> Repo
    Setup --> Scaffold
    StoryMap --> Cards
    StoryMap --> Events
    StoryMap --> Repo
    Talk --> Cards
    Talk --> Repo
    Talk --> Runs
    ValueStream --> Boards
    ValueStream --> Cards
    ValueStream --> Flows
    ValueStream --> Repo
    ValueStream --> Runs
    Votes --> Events
    Votes --> Repo

Load-bearing hex deps

Vendored libraries

dagre_ex is a separate OTP app, not a context: its own mix.exs, LICENSE, tests, .formatter.exs and precommit alias, which the root mix precommit runs (cmd --cd vendor/dagre_ex env MIX_ENV=test mix do deps.get + precommit). It is dependency-free and bound for extraction as a hex package, so it must never reference a Relay module or concept. It sits outside the boundary graph — boundary governs modules inside this project — so it has no use Boundary and is not in Relay's exports. If boundary ever flags a RelayWeb call into Dagre, the fix is a deps entry on RelayWeb, not a change to the library.

External services

Sources of truth: mix.exs, vendor/dagre_ex/mix.exs, lib/relay.ex / lib/relay_web.ex / lib/schemas.ex (use Boundary declarations), fly.toml, assets/css/app.css.