Open a recurring stream's first batch on create or reactivation

What It Does

First-batch work makes intake available immediately on activation rather than waiting for a future occurrence. Configuration saving is allowed to succeed when first-batch planning is refused, and the refusal belongs only to that response.

The Flow

When Something Fails

Only recognized planning refusal is isolated by the savepoint. Other failure can abort saving. The editor omits the refusal field, so the current interface can report saved configuration without explaining absent intake.

Open Design Questions

Product needs visible first-batch recovery and a decision on posting any predecessor retired by reactivation.

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

Controls

30 controls apply, from the corpus control catalogue.

TC-IAM-001 TC-IAM-002 TC-IAM-004 TC-IAM-005 TC-IAM-006 TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-AZ-005 TC-AZ-006 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-DAT-001 TC-LOG-001 TC-LOG-002 TC-LOG-003 TC-LOG-004 TC-LOG-005 TC-AVL-001 TC-AVL-004 TC-MON-001 TC-MON-002 TC-MON-004 TC-PI-001 TC-PI-002 TC-PI-003 TC-PI-004 TC-PI-005

Planning

Open a recurring stream's first batch on create or reactivation ​

What It Does ​

The Flow ​

When Something Fails ​

Open Design Questions ​