# ChatGPT Project Sources — what to upload

This file exists for one purpose: to tell the repository owner which files
belong in the **InteractiveStory** ChatGPT project's Sources. It is not a
documentation index — `planning/README.md` is that.

`planning/project-sources.txt` is the same list as bare paths, one per line, for
gathering the files.

The rule behind the list: **upload what is authoritative now.** A project source
is treated as current fact by whatever reads it, so a superseded document
uploaded alongside a current one does not add context — it manufactures a
conflict.

Refresh the Sources whenever the planning package is revised (`VERSION.md`
records each revision) and whenever a milestone completes.

## REQUIRED PROJECT SOURCES

Twenty-eight files.

**Repository orientation**

```text
README.md
DEVELOPMENT.md
PROVENANCE.md
```

**The planning index and its version**

```text
planning/README.md
planning/VERSION.md
```

**Product requirements and design**

```text
planning/SPECIFICATION.md
planning/TECHNICAL-DESIGN.md
planning/DATA-MODEL.md
planning/STORY-BRANCH-SEMANTICS.md
planning/CONTEXT-AND-MEMORY.md
planning/IMPORTED-KNOWLEDGE-DESIGN.md
planning/SECURITY-THREAT-MODEL.md
planning/MEDIA-EXTENSION-CONTRACT.md
planning/BROWSER-UX-SPEC.md
```

**Implementation plan and acceptance contract**

```text
planning/BUILD-MILESTONES.md
planning/V1-ACCEPTANCE-TESTS.md
planning/TEST-CAMPAIGN-FIXTURE.md
```

**The active ADRs** — all eleven. They are short, and each one closes a question
that will otherwise be reopened.

```text
planning/DECISIONS/001-browser-first.md
planning/DECISIONS/002-ollama-only-v1.md
planning/DECISIONS/003-authoritative-local-state.md
planning/DECISIONS/004-local-only-production.md
planning/DECISIONS/005-branch-preserving-history.md
planning/DECISIONS/006-genre-agnostic-core.md
planning/DECISIONS/007-future-media-extension.md
planning/DECISIONS/009-ai-dnd-production-base.md
planning/DECISIONS/010-explicit-typed-narrative-state-events.md
planning/DECISIONS/011-local-inference-endpoint-policy.md
planning/DECISIONS/012-active-head-non-destructive-history.md
```

ADR **008** is deliberately absent: it was the process gate requiring Phase 0 to
close before production work began, Phase 0 closed on 2026-09-01, and it is now
in `planning/archive/decisions/`.

## CURRENT-MILESTONE SOURCE

One file, and it changes as development progresses:

```text
planning/reports/M11-IMPLEMENTATION-REPORT.md
```

M11 is the most recently completed milestone, and there is no next one to brief:
what follows is independent review and the v1 acceptance decision. This report is
the release-validation evidence package — its §F is the acceptance matrix, its §G
the 100-turn campaign, its §O every defect found, and its §R the release-readiness
answers. It is **not** an acceptance record.

**Replace it, do not accumulate.** When a later report lands, remove this one
from the project Sources and upload that one instead. The repository does the same thing:
`planning/reports/` holds the current milestone's report and
`planning/archive/milestone-reports/` holds the rest.

## DO NOT UPLOAD AS PROJECT SOURCES

Not because these are worthless — because a source is read as current fact, and
these are not current.

- **Everything under `planning/archive/`.** The Phase 0 research reports, the
  Phase 0B recommendation and spikes, the completed M1 and M2 milestone reports,
  and archived ADR 008. Every conclusion they reached that still matters has
  already been applied to the active documents; what is left is superseded
  reasoning that will contradict the current package if uploaded beside it.
- **Older milestone reports**, once their successor exists. Uploading M1, M2 and
  M3 together produces three descriptions of the same subsystem at three
  different stages.
- **Source code.** `backend/`, `frontend/`, tests, migrations. The planning
  package describes the system; the code is read in the repository, where it can
  be searched and run.
- **Inherited upstream documentation.** Upstream AI-DnD's `plan/` build log and
  `docs/` guides, generated HTML and screenshots were deleted from this
  repository on 2026-09-03 for exactly this reason: they describe a hosted,
  scripted, multi-user product this fork removed. Do not re-upload them from
  upstream or from Git history.
- **Generated HTML, images and screenshots.** They add tokens, not facts.
- **`repo-inventory.txt` or any other local scratch output.** Not tracked, not
  authoritative, stale the moment it is written.