Uh oh!
There was an error while loading. Please reload this page.
docs(rfc): hooks framework design - #511
Open
behinddwalls wants to merge 1 commit into
Open
Conversation
behinddwalls
marked this pull request as ready for review
August 5, 2026 05:18
behinddwallsforce-pushed
the
hooks
branch
8 times, most recently
from
August 5, 2026 16:08
a03fa7a to
45482b5Compare## Summary ### Why? The pipelines emit lifecycle transitions but nothing can react outside pipeline state — no warehouse export, no PR comments or closes on merge events. The log topic is not that seam: SubmitQueue request statuses only, consumed solely for gateway read models. ### What? Adds `doc/rfc/hook-framework.md` plus its index entry: a design RFC for a cross-domain Hooks framework. Controllers publish a `HookEvent` to a durable per-domain `hook` topic; a thin dispatcher stage hands events to pluggable hooks (`platform/extension/hook/`, noop by default, composite for fan-out). One CloudEvents-shaped contract at `api/base/hook/` — `id`, `source`, `type`, `timestamp_ms`, `version`, `payload` — with publisher-minted ids for dedupe and hook idempotency, at-least-once delivery anchored in the triggering message, and a DLQ that preserves and pages instead of dropping. Reviewed by dual-agent consensus (Claude + codex). Design only — no implementation.
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 freeto 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
Why?
The pipelines emit lifecycle transitions but nothing can react outside pipeline state — no warehouse export, no PR comments or closes on merge events. The log topic is not that seam: SubmitQueue request statuses only, consumed solely for gateway read models.
What?
Adds
doc/rfc/hook-framework.mdplus its index entry: a design RFC for a cross-domain Hooks framework. Controllers publish aHookEventto a durable per-domainhooktopic; a thin dispatcher stage hands events to pluggable hooks (platform/extension/hook/, noop by default, composite for fan-out). One CloudEvents-shaped contract atapi/base/hook/—id,source,type,timestamp_ms,version,payload— with publisher-minted ids for dedupe and hook idempotency, at-least-once delivery anchored in the triggering message, and a DLQ that preserves and pages instead of dropping.Reviewed by dual-agent consensus (Claude + codex). Design only — no implementation.