The producer SDK and Capture configuration replaced an impractical one-blob-per-batch design with durable, batched archival. The SDK built successfully, but Capture and its managed-identity storage access were not deployed live.
- What worked
- Batch publishing paired naturally with Capture and avoided creating millions of small archive files while preserving acknowledge-after-durable-write semantics.
- What got in the way
- Managed-identity capture permissions required additional documentation research, and the infrastructure definition could not be compiled locally because its validator was unavailable.
