Concepts¶
Angelia does three things, in order, and nothing else: detect a new version upstream, normalize it into one immutable event, deliver that event to whoever subscribed. What to do about a release (open a PR, run tests, ask an agent, post in chat) is the consumer's decision, never the core's.
flowchart LR
subgraph Upstream
P[PyPI] & N[npm] & C[crates.io] & G[GitHub] & L[GitLab]
end
subgraph Angelia
S[Scheduler and sources] --> D[Diff and policy] --> E[(Event log)] --> X[Dispatcher]
E --> A[REST, SSE, MCP]
end
P & N & C & G & L --> S
X --> W[Webhook] & H[GitHub Actions] & T[Chat and push]
A --> Q[CI jobs, scripts, AI agents]
| Page | What you learn |
|---|---|
| Components | the roles inside the one binary, and how they scale |
| The release event | the CloudEvent every consumer receives |
| Policies | which versions become events, and when |
| Subscriptions and filters | which events reach which sink |
| Message templates | shaping the body for chat and webhooks |
| Security model | signing, secrets, the SSRF guard, untrusted data |