docs(adr): ADR-0041 — flow trigger family: taxonomy, naming, open-source core set#1746
Merged
Conversation
…rce core set
Decides three things about the trigger layer:
1. Taxonomy: a trigger adapts one class of business event into flow
executions via the engine's FlowTrigger seam — distinct from kernel
hooks (in-process lifecycle) and IJobService (plugin-owned clocks).
Non-goals recorded: screen flows are launched not triggered, approval
outcomes ride out-edges, plugin clocks (SLA scanner) call jobs directly.
2. Naming: triggers become a first-class `trigger-*` package family
(matching driver-/connector-/embedder-/knowledge-), dropping the
plugin- prefix; migration via deprecation stubs.
3. Tiers: record-change + schedule (shipped) + trigger-api (the one gap
to build next — flow type 'api' is schema-reserved with no runtime,
a Studio trap) form the Apache-2.0 core set every project needs.
email-inbound / queue / lifecycle defer to on-demand open source;
connector-event / threshold / file / iot to marketplace distribution,
with a written promotion rule. Descriptors gain a maturity field
('ga'|'beta'|'reserved') so Studio greys out contract-ahead-of-runtime
surfaces; boundary triggers must ingest via the outbox/queue path.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
added
documentation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Writes down the trigger plan discussed during the approvals revamp follow-ups:
FlowTriggerseam) and what it is not (screen launches, approval out-edges, plugin-internal clocks →IJobService, cf. feat(approvals): SLA auto-escalation — scheduler pass executing escalation.action #1742).plugin-trigger-*→ first-classtrigger-*family, consistent withdriver-*/connector-*/embedder-*/knowledge-*.trigger-record-change✅,trigger-schedule✅, andtrigger-apias the single short-term build item — the flow schema already reservestype: 'api'with no runtime behind it (a Studio trap today). Acceptance criteria include HMAC-verified per-flow endpoints and queue-backed ingestion from day one.maturity: ga|beta|reservedso Studio renders pickers from the live registry and greys out reserved types instead of letting users author flows that never run.Current state verified against code (engine seam, the two shipped triggers,
serveauto-wiring, the reservedapienum) with file references throughout.🤖 Generated with Claude Code