Appearance
CONTROL FRONTIER · WORKFORCE API PLANNED
Same intent. Same key.
Derive a key from source, dataset hash, adapter version and chunk identity.
Idempotency & retries
Persist the key before sending. After timeout, retry the exact request or query its known import/job identifier. A key reused with a different body is a conflict. Use exponential backoff with jitter for eligible failures. Never mint a fresh key simply because delivery status is uncertain.
Release status
The guides and API reference describe the reviewed design. Workforce API operations and complete integration remain proposed. Existing application capabilities are source-verified, not a public availability guarantee.