Account for a multi-request AI task

What It Does

The wrapper creates a task before work and supplies the context needed to associate its requests. A replay key returns the original execution without rerunning its body.

The Flow

Each request settlement increments totals inside its own transaction. The wrapper closes after work returns or throws.

When Something Fails

Close failure can leave completed work marked running; the hourly sweep later abandons it. Failed-body close errors are logged without replacing the original exception.

Open Design Questions

Consumers must choose replay keys and avoid inferring domain completion from task status alone.

Show evidence (sources, provenance, origins, pinned commits)

Controls

26 controls apply, from the corpus control catalogue.

TC-AI-006 TC-AI-007 TC-AVL-001 TC-AVL-005 TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-IAM-001 TC-IAM-002 TC-IAM-004 TC-IAM-005 TC-IAM-006 TC-LOG-004 TC-LOG-005 TC-MON-001 TC-PI-001 TC-PI-002 TC-PI-003 TC-PI-005 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-VEN-001 TC-VEN-002 TC-VEN-003

Planning

Account for a multi-request AI task ​

What It Does ​

The Flow ​

When Something Fails ​

Open Design Questions ​