Intent is accepted
The API authenticates, validates, and records the command with an idempotency key.
Intent survives. Execution continues with context.
FaithAPI separates what your product requested, what the platform accepted, and what the channel confirmed. That distinction makes failures and recovery understandable.
Work is distributed
Processing happens outside the request without confusing acceptance with external delivery.
The connector executes
Channel integration remains isolated behind a contract controlled by FaithAPI.
Operations receive evidence
Normalized states and events update context and feed webhooks.
A boundary for every responsibility.
PostgreSQL is the source of truth. Temporary coordination and distributed transport do not replace the durable operational record.
What the contract guarantees—and what it does not assume.
A 202 response confirms that intent was recorded; it does not confirm sending or channel delivery. Webhooks use at-least-once semantics, so consumers must deduplicate events.