d02feee57f
A tick is fully sequential: one vision call per page, then each note's checks and promotion in turn. Claiming three batches of a 13-page scan can approach the route's 300s ceiling, and a tick that times out leaves its batch to be reclaimed and re-read, paying for those pages twice. One batch per tick also makes n8n's execution log directly readable — one run, one document, one outcome. DN_TICK_BATCH_SIZE still overrides it once the page-count distribution is known. 34 batches at a 1-minute schedule is ~34 minutes rather than ~12. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| handoffs | ||
| n8n | ||
| setup | ||
| superpowers | ||
| api-reference.md | ||
| architecture.md | ||
| cooler-env.template | ||
| data-flows.md | ||
| data-model.md | ||
| minimax-multi-site-audit-prompt.md | ||
| modules.md | ||
| multi-site-assessment.md | ||
| operations.md | ||
| pwa-install-verification.md | ||