feat(dogfood): ADR-0060 D5 — flow trigger-type conformance ledger (4th surface)#2110
Merged
Merged
Conversation
…h surface) The fourth instance of the reusable conformance-ledger pattern, on the same checkLedger helper. A `Flow.type` declares HOW a flow is triggered; a declared trigger type with no runtime that fires it is authorable-but-inert — the flow-shaped #1887, and flows are heavily AI-authored. One row per Flow.type enum value (record_change / api / schedule / autolaunched / screen), all enforced with their runtime trigger/executor + a proof. The ratchet re-discovers the enum from flow.zod.ts and fails the build if a new flow type is added with no runtime. Proves the ADR-0060 pattern extends to a fourth surface as a filled-in table. dogfood-private, no changeset. Full build 75/75, dogfood 137; ratchet verified. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
📓 Docs Drift CheckNo hand-written docs reference the 1 changed package(s). ✅ |
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
2 participants
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.
ADR-0060 (#2103) D5 in action — extend the conformance-ledger pattern to a fourth surface, on the same
checkLedgerhelper.Why flow triggers
A
Flow.typedeclares how a flow is triggered. A declared trigger type with no runtime that fires it = a flow that's authorable but never runs — the flow-shaped #1887, and flows are heavily AI-authored.What
One row per
Flow.typeenum value, all enforced with their runtime + a proof:record_change→ trigger-record-change ·api→ trigger-api ·schedule→ trigger-scheduleautolaunched→ engine subflow/programmatic start ·screen→ builtin screen executor + suspended-run store (server runs, resumes on UI input)The ratchet re-discovers the
Flow.typeenum fromflow.zod.tsand fails the build if a new flow type is added with no runtime. Verified to bite.The pattern holds
Four surfaces now share one helper — authz / expression / validation-rule / flow-trigger — proving ADR-0060 D5: a new surface is a filled-in table, not a re-derived discipline. Full build 75/75 · dogfood 137. dogfood-private → no changeset.
🤖 Generated with Claude Code