application capa

application-triggers

Forge triggers module — event-driven trigger system for automating workflows.

Forge triggers module — event-driven trigger system for automating workflows.

Tierapplication
Roleunclassified (baselined)
Pathcrates/application/triggers
Edition2024
Targetsapplication_triggers, pg_forge_triggers
Public items20 across 4 modules
Tests2

What it is for

application-triggers — event-driven trigger system.

B-009: before this, migrations() returned Vec::new() and migrate_pending returned Ok(0) while ignoring the pool, so triggers and trigger_executions were never created by anything that actually called this module's own migration path.

Real gap found at Gate 0.5, not solved here: the central application-engine platform set already vendors this exact schema verbatim (crates/application/engine/migrations/048_primitives_triggers.sql, whose own header says it is copied from operations-triggers/migrations/001_triggers.sql), but adds IF NOT EXISTS to every CREATE TABLE/CREATE INDEX and DROP TRIGGER IF unlike that mirror, uses plain CREATE TABLE triggers / CREATE TABLE trigger_executions with no IF NOT EXISTS. So on a DB where the central set has already run, calling this module's own migrate_pending() errors with "relation already exists" instead of the no-op the central mirror was written to guarantee. Same root cause and same shape as application-tenant`'s documented gap (two independent copies of one library crate's schema, one idempotent and one not); flagged per B-009's own Risk Assessment rather than guessed around.

Capabilities

TriggersModule

application-triggers — event-driven trigger system.

Item
pub struct TriggersModule
TriggersModule :: fn new() -> Self
TriggersModule :: fn name(& self) -> & 'static str
TriggersModule :: fn version(& self) -> & 'static str
TriggersModule :: fn migrations(& self) -> Vec <MigrationSet>
TriggersModule :: async fn migrate_pending(& self, pool : & PgPool) -> std::result::Result <u32, MigrationError>
TriggersModule :: fn permission_codes(& self) -> Vec <String>

api (other)

HTTP API routers for application-triggers.

Item
fn admin_router <S>() -> Router <S> where S : Clone + Send + Sync + 'static, PgPool : FromRef <S>,

api::triggers_admin (other)

Triggers admin REST router.

Item
fn router <S>() -> Router <S> where S : Clone + Send + Sync + 'static, PgPool : FromRef <S>,

ExecutionsQuery

Triggers admin REST router.

Item
pub struct ExecutionsQuery

ListQuery

Triggers admin REST router.

Item
pub struct ListQuery

services::triggers (other)

Triggers service — thin wrapper around

Item
async fn list(pool : & PgPool, tenant_id : Option <Uuid>, include_inactive : bool,) -> Result <Vec <Trigger>, TriggerError>
async fn get(pool : & PgPool, id : Uuid) -> Result <Option <Trigger>, TriggerError>
async fn create(pool : & PgPool, req : CreateTriggerRequest) -> Result <Trigger, TriggerError>
async fn update(pool : & PgPool, id : Uuid, req : UpdateTriggerRequest,) -> Result <Trigger, TriggerError>
async fn delete(pool : & PgPool, id : Uuid) -> Result <(), TriggerError>
async fn enable(pool : & PgPool, id : Uuid) -> Result <Trigger, TriggerError>
async fn disable(pool : & PgPool, id : Uuid) -> Result <Trigger, TriggerError>
async fn list_executions(pool : & PgPool, trigger_id : Uuid, limit : i64,) -> Result <Vec <TriggerExecution>, TriggerError>
async fn get_execution(pool : & PgPool, id : Uuid,) -> Result <Option <TriggerExecution>, TriggerError>

How to use it

No examples/ target and no doctest in this crate's rustdoc. The tests listed under Verification are the closest executable usage.

Module structure

application_triggers

flowchart TD
  n_application_triggers["application_triggers"]
  n_application_triggers --> n_api["api"]
  n_api --> n_api__triggers_admin["triggers_admin"]
  n_application_triggers --> n_services["services"]
  n_services --> n_services__triggers["triggers"]

Public surface

`crate root`

ItemWhat it is
pub struct TriggersModule
TriggersModule :: fn new() -> Self
TriggersModule :: fn name(& self) -> & 'static str
TriggersModule :: fn version(& self) -> & 'static str
TriggersModule :: fn migrations(& self) -> Vec <MigrationSet>
TriggersModule :: async fn migrate_pending(& self, pool : & PgPool) -> std::result::Result <u32, MigrationError>
TriggersModule :: fn permission_codes(& self) -> Vec <String>

`api`

ItemWhat it is
fn admin_router <S>() -> Router <S> where S : Clone + Send + Sync + 'static, PgPool : FromRef <S>,Compose the triggers admin router, generic over the consumer state S.

`api::triggers_admin`

ItemWhat it is
pub struct ListQuery
pub struct ExecutionsQuery
fn router <S>() -> Router <S> where S : Clone + Send + Sync + 'static, PgPool : FromRef <S>,

`services::triggers`

ItemWhat it is
async fn list(pool : & PgPool, tenant_id : Option <Uuid>, include_inactive : bool,) -> Result <Vec <Trigger>, TriggerError>
async fn get(pool : & PgPool, id : Uuid) -> Result <Option <Trigger>, TriggerError>
async fn create(pool : & PgPool, req : CreateTriggerRequest) -> Result <Trigger, TriggerError>
async fn update(pool : & PgPool, id : Uuid, req : UpdateTriggerRequest,) -> Result <Trigger, TriggerError>
async fn delete(pool : & PgPool, id : Uuid) -> Result <(), TriggerError>
async fn enable(pool : & PgPool, id : Uuid) -> Result <Trigger, TriggerError>
async fn disable(pool : & PgPool, id : Uuid) -> Result <Trigger, TriggerError>
async fn list_executions(pool : & PgPool, trigger_id : Uuid, limit : i64,) -> Result <Vec <TriggerExecution>, TriggerError>
async fn get_execution(pool : & PgPool, id : Uuid,) -> Result <Option <TriggerExecution>, TriggerError>

No pub use re-exports: every item above is declared in this crate.

Boundary

Reaches into operations, platform.

Shares tier application with 120 other crates: application-agreements, application-ai, application-analytics, application-approvals, application-assessments, application-audit-log, application-auth, application-billing, … (120 total).

_What this crate deliberately does NOT own is a judgment. No committed registry records one for it, so none is stated here._

Where it sits

Tier (ontology)application
Architectural role (taxonomy)unclassified (baselined)
Locationcrates/application/triggers
Vocabulary in force (lexicon)current

Tier flow. Which tiers this crate's own edges cross.

flowchart LR
  n_application["application"] --> n_operations["operations"]
  n_application["application"] --> n_platform["platform"]

Dependencies

Runtime, in this workspace.

CrateTierOptionalOnly on
`application-core`applicationnoalways
`operations-triggers`operationsnoalways
`platform-dto`platformnoalways

Runtime, from outside the workspace.

CrateRequirementFeaturesOptionalOnly on
async-trait^0.1noalways
axum^0.7multipartnoalways
chrono^0.4serdenoalways
serde^1derivenoalways
serde_json^1noalways
sqlx^0.8runtime-tokio, postgres, chrono, uuid, jsonnoalways
thiserror^2noalways
tokio^1fullnoalways
tracing^0.1noalways
uuid^1v4, v7, serde, jsnoalways

Development. None.

Build. None.

Depended on by. Nothing in this workspace.

Signal flow — what reaches this crate, and what it reaches.

flowchart LR
  SELF["application-triggers"]
  SELF -->|runtime| n_application_core["application-core"]
  SELF -->|runtime| n_operations_triggers["operations-triggers"]
  SELF -->|runtime| n_platform_dto["platform-dto"]
  classDef self fill:#1f883d,stroke:#1f883d,color:#fff;
  class SELF self;

Feature flags

No Cargo features are defined: every capability is unconditional, so no consumer can receive a half-wired crate.

Targets

KindNameSource
libapplication_triggers`src/lib.rs`
testpg_forge_triggers`tests/pg_forge_triggers.rs`

Error model

No public error type was detected: no public item declares a type named *Error, and no public signature returns one.

Operational characteristics

PropertyEvidence
async public surfaceyes
async runtimeyes
database accessyes
network I/Oyes
unsafe codenone detected
environment variablesyes

No unsafe block, unsafe fn, unsafe impl or unsafe trait was found by the parser anywhere in this crate's source.

Configuration

VariableRead in
CARGO_PKG_VERSIONsrc/lib.rs

No workspace crate depends on this one.

Verification

KindCount
Unit tests1
Integration tests1
Examples0
Doctests0

Evidence by module. How often each public module is named by something executable.

ModuleTestsExamplesConsumers
crate root100
api100
api::triggers_admin300
services::triggers900

What the tests establish, by name:

Documentation coverage

MeasureDocumentedTotal
Public items with rustdoc120
Public modules with a //! block34
pie showData
    title Public items with rustdoc
    "Documented" : 1
    "No rustdoc detected" : 19

Metrics

MetricValue
Rust source files5
Source lines385
Code lines281
Public API items20
Public modules4
Tests2
Examples0
Cargo features0
Direct runtime dependencies13
Workspace reverse dependencies0
pie showData
    title Public API by kind
    "function" : 11
    "method" : 6
    "struct" : 3
pie showData
    title Rust source composition
    "Code" : 281
    "Blank or comment" : 104

Generation

Rendered by tools-corpus corpus readme from repository evidence alone, renderer schema 2, lexicon current. No model, network service or database was consulted. Regenerate with tools-corpus corpus readme --write; verify with --check.

Todas las application · Manual