Task Specs - Softcrum Suite

Execution order is a dependency chain, not a preference:

#	Task	Archetype	Depends on
TS-001	Foundational migration — schemas, parametric seeds, partitions, platform tables	synchronous command	—
TS-002	`QueuePort` + `NotificationChannelPort` and the F1 adapters	synchronous command	amendment A1 applied, TS-001
TS-003	Ingestion pipeline: `track`/`identify`/`batch` with fast-ack and processor	async event pipeline	TS-001, TS-002
TS-004	Canonical slice `trackEvent`: rules → ledger → notifications → webhook	async event pipeline (the reference)	TS-003
TS-005	CI extensions enforcing the new standards	—	TS-001…TS-004

TS-004 promotes ../slices/track-event.md from SPEC to WALKTHROUGH with real file paths — that is part of its acceptance criteria, not a follow-up.

Writing a new task spec

Objective (one sentence) · Archetype · Refs (DEC-*, ADRs, standards) · In scope · Out of scope (be explicit — this is what keeps agents from sprawling) · Acceptance criteria, each one mechanically verifiable, with latency budgets stated as numbers.

⌘I