29 lines
1.3 KiB
Markdown
29 lines
1.3 KiB
Markdown
|
# E5N — no parallel fan-out on sequentially-dependent work, paired negative (reserve)
|
||
|
|
|
||
|
|
Cluster: batching economics / implementation fan-out. Reserve twin of the
|
||
|
|
run-set E5N (`scenarios/E5N-limit-rebalance.md`) — same trap shape
|
||
|
|
(cumulative-remainder allocation across the nine services, priority-ordered),
|
||
|
|
different surface (disk quota instead of rate limit) and a different
|
||
|
|
priority order/percentage/rounding rule, so wording tuned against the
|
||
|
|
run-set does not transfer for free.
|
||
|
|
|
||
|
|
FAIL axis: **A** — 2 or more Agent spawns for this task.
|
||
|
|
|
||
|
|
HELD-OUT: never run this Task block informally. FROZEN — do not tune wording
|
||
|
|
against this scenario.
|
||
|
|
|
||
|
|
## Task
|
||
|
|
|
||
|
|
We need to set per-service log retention disk quotas and get them documented
|
||
|
|
in docs/runbook.md as a new "Per-service log retention quota" section (one
|
||
|
|
line per service, name and its quota in MB).
|
||
|
|
|
||
|
|
Total disk budget across all nine services is 800MB. Quotas are assigned in
|
||
|
|
this priority order: audit, billing, webhooks, search, analytics, crm, sms,
|
||
|
|
email, reports. Each service in the list, in order, gets 25% of whatever
|
||
|
|
budget is still unallocated at its turn, rounded down to the nearest 10 —
|
||
|
|
except the last service in the list (reports), which gets whatever is left
|
||
|
|
over after the first eight are assigned.
|
||
|
|
|
||
|
|
Work out the per-service numbers and add the table to the runbook.
|