# Programme

## Hierarchy (§43)

```
Initiative → Epic → Capability → Story → Engineering task/subtask
```

## Initiatives

| ID | Initiative | Outcome |
|---|---|---|
| I-01 | Publishing Core | Owner can publish a real site |
| I-02 | Extensibility Platform | Themes/features add cleanly |
| I-03 | Administration | Meaningful site behaviour is editable |
| I-04 | Visitor Personalisation | Owner-controlled visitor preferences |
| I-05 | Operational Simplicity | Install/upgrade/backup are predictable |
| I-06 | Extension Ecosystem | Reading, RSS, themes and later capabilities |

## Initiative → epic map (editorial primary mapping)

- **I-01** — E02, E03, E04, E06, E07, E08, E09, E10, E29, E30, E31
- **I-02** — E11, E12, E13, E14, E15, E16
- **I-03** — E05, E19
- **I-04** — E17, E18
- **I-05** — E00, E01, E20, E21, E22, E23, E24, E25, E26
- **I-06** — (future v0.2/v0.3 scope; no v1 epics)

## Numbering scheme

```
Initiative  I-01 … I-06
Epic        E00 … E31
Story       E<epic>-S<story>         e.g. E00-S01
Task/Card   E<epic>-S<story>-T<nn>   e.g. E00-S01-T01
Epic-level task (no stories)  E<epic>-T<nn>   (only E26)
```

### Numbering reconciliation (v1.1)

v1.0 uses epic IDs `E00`–`E26`. The v1.1 amendment (§52-A) reused `E26`–`E28` for the new Sprint M epics, colliding with Sprint 7's `E26`. Because v1.1 is additive ("adds, does not delete"), v1.0 IDs stay unchanged and Sprint M epics receive fresh IDs:

- Sprint M "media pipeline" (§52-A `E26`) → **E29**
- Sprint M "embeds" (§52-A `E27`) → **E30**
- Sprint M "native charts and diagrams" (§52-A `E28`) → **E31**

Their stories renumber accordingly (e.g. `E26-S01` → `E29-S01`). `E27`/`E28` are retired.

## Requirements treated as confirmed (§2.1)

Home + individual posts; Amber ("Node") initial appearance; everything meaningful editable; plugin/extension-oriented; themes as extensions; owner may later permit visitor theme choice; visitor choice remembered in browser/session; deployment extremely simple; Docker Compose preferred; delivery in epics/stories/sprints/acceptance criteria; fast demo without irreversible shortcuts. **v1.1 restored:** Markdown authoring (13.1); rich media (29.1–29.4); external graph/diagram embeds (29-A); page metadata (34-A).

## Proposed defaults requiring sign-off (§2.2)

OD-01 two-week sprints after Sprint 0 · OD-02 Sprint 0 = one week · OD-03 one site per installation · OD-04 one administrator · OD-05 admin idle timeout 12h / absolute 7d · OD-06 anonymous preference retention 365d · OD-07 local filesystem media storage · OD-08 `/posts/:slug` canonical route · OD-09 soft delete · OD-10 build-time trusted extensions · OD-11 Vite modern-browser baseline · OD-12 amd64+arm64 · OD-13 (v1.1) Markdown via `core.markdown` · OD-14 (v1.1) seed embed allowlist. OD-03/04/08/09 need explicit product sign-off before semantics freeze.

## Definition of Ready / Done

See [engineering-standards.md](engineering-standards.md) (§44/§45).