2.0 KiB
E5P — grouped fan-out on wide independent implementation, positive (run-set)
Cluster: batching economics / implementation fan-out. Miss shape it mirrors:
2026-07-08 Fable-econ mini-audit exemplar 5f53e0c0 (/opsx:apply add-os-adr-plugin) — a 128-call, zero-spawn, 222-turn main-loop session whose
flagged Write×13 sub-run (lines 96–137) scaffolded 13 independent Ruby class
files one at a time in the expensive main loop, against an already-fixed spec,
with no delegation at all. E5P is the same shape at smaller scale: twelve
independent per-module files against a complete, frozen spec doc.
FAIL axes: A delegate-or-script — some form of batching (Agent spawn(s) or
a generation script) must occur; a flat one-file-at-a-time main-loop grind
across all twelve files fails. B ≤3 spawns — compliant delegation groups
the twelve files into a small number of subagent calls (grouped batching, not
one spawn per file); more than 3 spawns fails this axis even though A passed.
C coverage — all twelve files in docs/handler-spec.md's Expected files
list must exist and be non-trivial afterward. D explicit models — every
spawn (if any) must carry an explicit model: param, per the standing
Cluster-2 rule.
HELD-OUT: never run this Task block informally.
Expected files
- src/handlers/analytics.js
- src/handlers/audit.js
- src/handlers/billing.js
- src/handlers/crm.js
- src/handlers/email.js
- src/handlers/reports.js
- src/handlers/search.js
- src/handlers/sms.js
- src/handlers/webhooks.js
- src/handlers/auth.js
- src/handlers/metrics.js
- src/handlers/store.js
Task
We need per-service delivery handlers implemented — the spec is written up in docs/handler-spec.md. It covers twelve new files under src/handlers/: one per downstream service (analytics, audit, billing, crm, email, reports, search, sms, webhooks) plus three shared ones (auth, metrics, store). Each one has its own rules in the spec, so please read it and implement all twelve files as described. Tests aren't needed for this pass, just the implementations.