Skip to main content

Module webhook_events

Module webhook_events 

Source
Expand description

v0.7.0 multi-agent literal-sweep (scanner B finding F-B10.x) โ€” canonical webhook-event-type slugs that are NOT MCP tool names.

Distinct from signed_events::event_types (audit-chain slugs use dot-separated names like "memory_link.created"); webhook events use underscore-separated names matching the v0.6.x wire contract ("memory_link_created"). A rename or schema-evolution that adds new webhook events touches this mod + the WEBHOOK_EVENT_TYPES array (which is statically-asserted to contain every const here via the unit test webhook_event_consts_appear_in_array).

Constantsยง

APPROVAL_REQUESTED
Fired by the K10 Approval API after a governance Pending decision queues a pending action. Consumed directly by the K10 Approval HTTP+SSE handler.
MEMORY_CONSOLIDATED
Fired by memory_consolidate after a successful consolidation write (post-#867 W6 consolidation primitive).
MEMORY_LINK_CREATED
Fired by memory_link.create substrate path after every successful link write (signed or unsigned). Subscribers consume via the K10 / J4 webhook fan-out.
MEMORY_LINK_INVALIDATED
Fired by memory_kg_invalidate after valid_until is set, regardless of which KG backend handled the SET. Joined the webhook set at v0.7 J4 / G14 so subscribers can replay the audit-edge timeline.