> ## Documentation Index
> Fetch the complete documentation index at: https://internal.softcrum.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Task Specs

> Executable units of work. Each declares its canonical slice archetype (DEC-I5), its scope, what is explicitly out of scope, and acceptance criteria that include the p95 budgets.

Execution order is a dependency chain, not a preference:

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

TS-004 promotes [`../slices/track-event.md`](/slices/track-event) 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.