cayu.tasks.base

Public Cayu API. Definitions are grouped by their public source module, and definitions from private implementation modules appear on their package’s page; adding a symbol does not move existing links. The import shown at each entry is a supported public namespace. Read the Python API overview and install the required extra.

Each definition in this module has its own page.

• CompletionDecisionApplicationReceipt: Immutable evidence that one verifier decision was applied to its task.
• InMemoryTaskStore: In-process task store for tests, local development, and examples.
• interrupted_task_handoff_request: Bind one running task snapshot to an exact interrupted-session handoff.
• InterruptedTaskContinuationClaimPage: One bounded continuation scan and its optional atomic task claim.
• new_interrupted_task_continuation_handoff_id: Create caller-owned authority for one replayable continuation claim.
• settle_task_retry_attempt_with_retry: Settle once, reconciling only acknowledgement-ambiguous store failures.
• task_create_with_execution_source: Classify work at a trusted direct-SDK host boundary.
• task_invocation_for_create
• TaskAggregateFilter: Current task attributes that may scope a store-native aggregate.
• TaskCancellationReconciliation: Durable positive evidence attached to an ordinary cancellation receipt.
• TaskCancellationReconciliationConflict: An ordinary reconciliation request lost an identity or settlement race.
• TaskCancellationReconciliationEvent: Secret-free event projection for one owner-lost ordinary cancellation.
• TaskCancellationReconciliationEventType: Stable bounded lifecycle evidence for ordinary-task cancellation recovery.
• TaskCancellationReconciliationEvidence: Ordinary-task evidence with the shared bounded validator schema.
• TaskCancellationReconciliationOutcome: Application-validated state of an ordinary task’s cancelled effect.
• TaskCancellationReconciliationRejected: Application evidence was non-positive, so the ordinary task remains fenced.
• TaskCancellationReconciliationRequest: Exact owner-lost ordinary cancellation plus application-validated evidence.
• TaskCancellationReconciliationResult: Immutable ordinary cancellation receipt plus positive recovery evidence.
• TaskClaimLost: A worker no longer owns the active lease required for a task mutation.
• TaskCreate
• TaskInterruptedHandoffConflict: An interrupted-task handoff conflicts with current durable authority.
• TaskInterruptedHandoffReceipt: Immutable commit evidence for one exact interrupted-task handoff.
• TaskInterruptedHandoffRequest: Exact authority for releasing one interrupted task’s worker ownership.
• TaskInvocationSnapshot: Bounded task identity and immutable provenance for delegation boundaries.
• TaskOperationalSnapshot: Exact current task counts captured by one store-local read snapshot.
• TaskOrder
• TaskQuery
• TaskRetryAttemptDisposition: Application-classified outcome for one retry-series attempt.
• TaskRetryAttemptReport: Application-owned classification and bounded accounting for one attempt.
• TaskRetryCancellationReconciliation: Durable positive evidence attached to the ordinary cancellation receipt.
• TaskRetryCancellationReconciliationConflict: A reconciliation request lost an exact identity or settlement race.
• TaskRetryCancellationReconciliationEvent: Secret-free event projection for one owner-lost cancellation transition.
• TaskRetryCancellationReconciliationEventType: Stable bounded lifecycle evidence for cancellation reconciliation.
• TaskRetryCancellationReconciliationEvidence: Bounded application-validated evidence; raw external payloads are excluded.
• TaskRetryCancellationReconciliationOutcome: Application-validated state of the cancelled attempt’s external effect.
• TaskRetryCancellationReconciliationRejected: Application evidence was non-positive, so the attempt remains fenced.
• TaskRetryCancellationReconciliationRequest: Exact owner-lost cancellation identity plus application-validated evidence.
• TaskRetryEvent: Bounded, failure-payload-free retry evidence committed by a task store.
• TaskRetryEventType: Stable task-level retry event types committed with a settlement.
• TaskRetrySettlementRequest: One typed, claim-fenced retry-attempt outcome.
• TaskRetrySettlementResult: Immutable settlement receipt for one attempt and optional successor.
• TaskSessionClosureClaim: Exact non-expiring authority for retiring one session’s task set.
• TaskStatusCounts: Complete current-task counts for every lifecycle status.
• TaskStore: Persistent store for durable work items.
• TaskTerminalizationConflict: An idempotency key is already bound to another terminalization intent.
• TaskTerminalizationReceipt: Immutable commit evidence for one task terminalization intent.
• TaskTerminalizationRequest: One claim-fenced, replay-safe completion, failure, or cancellation intent.
• TaskTerminalizationRetryPolicy: Finite retry and backoff bounds for acknowledgement-ambiguous writes.
• TaskTerminalizationRetryResult: Detached terminal task plus observable retry/reconciliation evidence.
• TaskTerminalizationUncertain: Bounded evidence that no exact terminalization receipt was observed.
• TaskTerminalKind
• terminalize_task_with_retry: Terminalize once, reconciling only acknowledgement-ambiguous failures.