Event-Based Workflow Triggers - Integration

​

Overview

​

Integration Points (from Spec)

​

Platform Layer Contract

• Event publication: publishEvent({ event_name, payload, organization_id, site_id? }) in src/platform/events/publishEvent.ts
• Event types: src/platform/events/types.ts; event names aligned with fw_workflow_events.event_name
• Documentation: src/platform/events/README.md for cores integrating with FW-16

​

Event Contracts

• Event payloads must conform to the JSON Schema in fw_workflow_events.payload_schema for the given event_name.
• New events are registered via seed migrations (insert into fw_workflow_events). See EVENT_CONTRACTS.md for planned and existing event names.
• Idempotency and retry semantics are documented in EVENT_CONTRACTS.md; FW-16 logs events in fw_domain_events and marks them processed via fw_process_domain_event().

​

Security and Tenant Isolation

• Event registry (fw_workflow_events) is global and read-only for authenticated users.
• Event log (fw_domain_events) is scoped by organization_id; RLS uses has_org_access(auth.uid(), organization_id) (or platform equivalent). Insert allowed for authenticated users in org.
• Event publication requires organization context; payloads must not contain PHI beyond what is necessary for workflow context.

​

Phase 2: Event Schema Registry Expansion

​

Phase 2 Integration Additions

​

Updated Platform Layer Contract

publishEvent({
  event_name: string;
  payload: Record<string, unknown>;
  organization_id: string;
  site_id?: string;
  correlation_id?: string; // Phase 2: optional; generated if not provided
}): Promise<{ event_id: string; correlation_id: string }>

​

Related Docs

• FW-16 Spec
• FW-16 Phase 2 Spec
• PLATFORM_INTEGRATION_LAYERS.md — FW-16 Event Publishing Integration Layer
• EVENT_CONTRACTS.md
• CROSS_CORE_INTEGRATIONS.md