Epics

Epics - index and decomposition

Epics group features that ship together. Each Epic links to its detail page (Epic-NN-Name) with task breakdown. Epics map to Use Cases (Use-Cases) and to releases (Roadmap).

ID	Title	Status	Target release	Detail
E-01	Ledger Foundation	Active	v0.1.0	Epic-01-Ledger
E-02	Payments + Idempotency + Outbox	Planned	v0.2.0	Epic-02-09-Briefs#epic-02
E-03	Event Bus (Kafka API + outbox dispatcher)	Planned	v0.2.0	Epic-02-09-Briefs#epic-03
E-04	Compliance (KYC orchestration + AML)	Planned	v0.3.0	Epic-02-09-Briefs#epic-04
E-05	Decision Engine (JSON DSL + standalone library)	Planned	v0.2.0	Epic-02-09-Briefs#epic-05
E-06	Sandbox (Bank, KYC, demo data)	Active	v0.1.0	Epic-02-09-Briefs#epic-06
E-07	Observability (metrics, logs, traces, dashboards)	Active	v0.1.0	Epic-02-09-Briefs#epic-07
E-08	Sandbox UI (React dashboard)	Planned	v0.4.0	Epic-02-09-Briefs#epic-08
E-09	Developer Experience (CLI, SDKs, docs site)	Planned	v0.4.0	Epic-02-09-Briefs#epic-09

Note: E-02..E-09 details live in single page Epic-02-09-Briefs (compact briefs). E-01 has its own page because it's the active v0.1.0 sprint. Future epics get own pages when promoted to Active.

Epic statuses

• Active - work in progress
• Planned - scope agreed, work not started
• Backlog - needs grooming
• Done - released

How an epic decomposes

Epic
 ├── Feature 1
 │   ├── Task 1.1 (issue)
 │   ├── Task 1.2
 │   └── Task 1.3
 ├── Feature 2
 │   └── Task 2.1
 └── Acceptance criteria (link to Use Cases)

Tasks are GitHub Issues. Features are tag groupings. Acceptance criteria come from Use Cases.

Sprint plan

See Sprint-01-Ledger-Foundation for the v0.1.0 plan.