docs(events): a trigger can start a run (Rust §14.3 stage 9, D370) #356

wtclaude · 2026-10-16T06:52:54Z

wtclaude commented

2026-10-16 06:52:54 +00:00

The docs half of RunicGateway/website#216.

EVENTS.md §E, Starting a run from a trigger (new): covers starts, the emit path's third subscriber, the four rules (version is verified, one run at a time, cooldown, no event.*), the run's origin, and what is deliberately left out: a step cannot read the firing's variables, because that would be a MODULE_API change nothing has asked for yet.
EVENTS.md §D: adds event_runs.origin and a twelfth table, event_trigger_starts.
EVENTS.md API surface: adds triggerStarts on GET /admin/events/:id and origin on the run console.
BACKEND_DESIGN.md: adds event_runs.origin and event_trigger_starts.
PLAN_REDESIGNS §14.3.21: stage 9 as built, with eight settled-in-code points the org lead can overrule, the tests and the Module-uo proof. Adds pointers in §9, §14.3.11 and §14.3.12. This ends the §14.3 build; the end walk is next, and it still waits for RaidableBases (D359).

AI disclosure

This PR was written with an AI tool: Claude Code (Claude Opus 5.5).

🤖 Generated with Claude Code

https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

The docs half of RunicGateway/website#216. - **EVENTS.md §E, *Starting a run from a trigger*** (new): covers `starts`, the emit path's third subscriber, the four rules (version is verified, one run at a time, cooldown, no `event.*`), the run's `origin`, and what is deliberately left out: a step cannot read the firing's variables, because that would be a MODULE_API change nothing has asked for yet. - **EVENTS.md §D:** adds `event_runs.origin` and a twelfth table, `event_trigger_starts`. - **EVENTS.md API surface:** adds `triggerStarts` on `GET /admin/events/:id` and `origin` on the run console. - **BACKEND_DESIGN.md:** adds `event_runs.origin` and `event_trigger_starts`. - **PLAN_REDESIGNS §14.3.21:** stage 9 as built, with eight settled-in-code points the org lead can overrule, the tests and the Module-uo proof. Adds pointers in §9, §14.3.11 and §14.3.12. **This ends the §14.3 build**; the end walk is next, and it still waits for RaidableBases (D359). ## AI disclosure - [x] This PR was written with an AI tool: Claude Code (Claude Opus 5.5). 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

wtclaude added 1 commit 2026-10-16 06:52:56 +00:00

docs(events): a trigger can start a run (Rust §14.3 stage 9, D370) b846c0c6b4

- EVENTS.md §E "Starting a run from a trigger": `starts`, the third
  emit subscriber, the four rules (verified, one at a time, cooldown,
  no event.*), the run's origin, and what is deliberately not in it.
  §D: event_runs.origin and a twelfth table, event_trigger_starts.
  API surface: triggerStarts on GET /admin/events/:id, origin on the
  run console.
- BACKEND_DESIGN.md: event_runs.origin and event_trigger_starts.
- PLAN_REDESIGNS §14.3.21: stage 9 as built, eight settled-in-code
  points, tests and the Module-uo proof; pointers in §9, §14.3.11 and
  §14.3.12. This ends the §14.3 build.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

whitlocktech merged commit d3567dafe4 into main

2026-10-16 07:01:58 +00:00

whitlocktech deleted branch docs/event-trigger-starts

2026-10-16 07:01:59 +00:00

whitlocktech referenced this issue from a commit

2026-10-16 07:02:00 +00:00

Merge pull request 'docs(events): a trigger can start a run (Rust §14.3 stage 9, D370)' (#356) from docs/event-trigger-starts into main

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: RunicGateway/docs#356