Skip to content

trogonstack/trogonstack-eda

v0.3.0MIT

Event-driven architecture skills for designing event definitions, schemas, contracts, and catalogs following good practices for domain and integration events

eda-bound-process-lifetime

Design or review event-driven process managers, sagas, and multi-step workflows so every instance provably ends within a known maximum lifetime (T_max). Lists the waiting states, gives each one a deadline and a named exit, keeps loops counted, makes late timers and duplicates harmless, and computes T_max from the longest path. Produces a lifecycle table, findings for every unbounded wait or loop, and the T_max derivation. Use when designing a saga, process manager, approval flow, OAuth or payment flow, or any aggregate with pending or awaiting states; when reviewing a state table; when instances get stuck, need a reaper, or block a version cutover; and when asking 'how long can this run', 'when can we delete the old version', or 'how long must we keep these streams'. Do not use for long-lived entities that never finish (accounts, sessions, connections), periodic reconcilers, event naming or payload design (use event-definition), full event modeling workflows, or races (use concurrency-find-toctou).

Read SKILL.md at the source

Pinned to revision cee7253451a5, so it is the text this page describes rather than whatever the author pushed since.

Pre-approved tools experimental

Experimental field. Support varies between clients, so this list is what the author declared, not what your client will enforce.

  • AskUserQuestion
  • Read
  • Write
  • Bash

Files

Every link opens the file at its source, pinned to the revision this page describes.