This index separates current operating contracts from the design records that produced them.
- CURRENT describes supported behavior in the 0.6.x source tree.
- HISTORICAL preserves an audit, migration handoff, build plan, or earlier specification. It may contain removed API names and must not be used as a copy-and-paste guide.
- DESIGN ONLY explores a possible or deliberately unimplemented direction.
When documents disagree, use the installed package version, source, and tests first; then the current documents below.
| Document | Purpose |
|---|---|
| Package README | Requirements, runtime model, capabilities, storage, and quick start |
| This documentation map | Status vocabulary and navigation |
| Wiring a consumer | Complete top-level consumer, DI, middleware, table, and deployment contract |
| Consumer design interview | Adaptive questions for discovering invariants, transaction boundaries, orchestration, ownership, and proof before coding |
| Consumer modules | Host/module lifecycle, separate-container bridge, routing, and process overlay |
| Eventing lanes | The three raising lanes, reschedule-via-fact, the WorkflowHandler phase lock, and the replay-not-splice rule |
| DDDash v2 scope | Implemented unified trace, Aggregate Biography, consumer provenance, and explicit non-goals |
| Release and migration ledger | Version-by-version consumer changes; the old filename is retained for inbound links |
| Canonical agent skill | Current modeling decisions and source navigation for coding agents |
| Document | Status |
|---|---|
| TraceContext and correlation spec | Implemented beginning in 0.3 and subsequently evolved; appendices include shelved ideas |
| Dashboard v1 build outline | Build plan for the dashboard now under ddd-wordpress/Admin/Dashboard |
| DDD Drill inspector plan | Early dashboard direction |
| Framework issues from consumer review | Audit that drove later releases |
| Integration event evolution | 0.1-to-0.2 architecture handoff |
| Outbox pause design | Built design record; inspect current source before using its API details |
| Dashboard iterations | Dated design and reconstruction notes |
| Implementation plans and specs | Dated implementation evidence, not operational guidance |
| Document | Scope |
|---|---|
| Outbox transport payload strategies | Possible transport optimization; explicitly not a current change |
| Multi-item behaviour topology | Topology exploration rather than a shipped contract |
The directories under superpowers/ and dashboard/iterations/ are retained
as historical collections even when an individual plan describes behavior that
later shipped. Their dates and decision context remain useful; their examples
do not outrank current code.