Skip to content

Coordinate Session State

Coordinator owns governed Sessions, service leases, invocations, Delegations, graph epochs, and their durable outbox.

Applications use Caracal SDK Session and Delegation APIs or the documented Coordinator API. The console BFF uses an operator credential to inspect and intervene. Top-level runtime commands do not manage Coordinator state.

Do not place the operator Coordinator token in workload code. Do not write Coordinator tables or Redis lifecycle topics directly.

ItemLocal value
Port4000
LivenessGET /health
ReadinessGET /ready
MetricsGET /metrics

Use Use Coordinator API for routes and SDK contracts. Service environment variables are cataloged in Configure Service Environment.

Session and Delegation writes commit to Postgres with outbox rows. Publishers relay lifecycle, invocation, delegation-invalidation, and revocation events through Redis. STS consults authoritative state before issuing authority tied to that lineage.

Task Sessions expire by TTL. Service Sessions require heartbeat renewal. Sweepers mark stale leases, enforce invocation deadlines, expire Delegations, and clean terminal records according to retention settings.

FailureUser impact
Postgres unavailableSession/Delegation operations and readiness fail.
Redis/outbox delayedDownstream lifecycle and invalidation views lag; durable state remains available for retry.
Service heartbeat stopsThe Session becomes unhealthy or expires even if its process still exists.
Sweeper unavailableStale state remains longer; alert on job/readiness metrics.
Operator credential missingConsole Session and Delegation views fail; workload SDK credentials are a separate path.

Issue Mandates for the authority path, Coordinate Sessions for the cross-service flow, or Manage Runtime Authority for the operator workflow.