Event taxonomy
Reloqui uses typed canonical events — there is no catch-all event type. Each is versioned in the event schema registry (GET /api/v1/admin/event-schemas).
Source evidence (ingested)
Section titled “Source evidence (ingested)”| Event | Meaning |
|---|---|
scm.pr.merged |
A pull/merge request merged. |
scm.branch.created |
A branch was created. |
scm.tag.created |
A tag was created. |
scm.push.force |
A force-push (triggers evidence invalidation). |
tracker.issue.updated |
An issue changed state / fix version. |
tracker.version.created |
A tracker version/release was created. |
build.completed |
A CI build finished. |
artifact.published |
An artifact/image was published (digest, tag, registry). |
deployment.completed |
A deployment succeeded. |
deployment.rolled_back |
A deployment was rolled back. |
infra.plan.applied |
A Terraform plan/apply ran (with a change summary). |
infra.drift.detected |
Infrastructure drift was detected. |
incident.triggered / incident.resolved |
Incident lifecycle (correlated, never scored). |
Internal / lifecycle (emitted)
Section titled “Internal / lifecycle (emitted)”| Event | Meaning |
|---|---|
release.created / release.reconciled / release.published / release.rolled_back |
Release lifecycle. |
release.approval.requested / approved / rejected / suspended |
Approval lifecycle (incl. G3 suspension). |
evidence.classified |
Emitted at reconcile with the classification breakdown. |
note.generated |
Release notes regenerated. |
catalog.entity.changed |
A catalog entity was created/updated. |
ops.dlq.alert / ops.delivery.failures / ops.connector.silent |
Operational alerts. |
digest.daily |
Daily activity digest. |
Delivery
Section titled “Delivery”Events are written to a transactional outbox in the same transaction as the business change, then a relay publishes them and fans them out to your notification subscriptions with HMAC signing and retries.