Jesse.Markowitz/interactive-story
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Planning v4.1: record the v1.0.0 release, and plan v1.1

Browse Source 
Documentation only. No product code, requirement, acceptance test or
schema changes.

Post-release correction. v4.0 was written before the closeout commit was
signed (432f041), main was fast-forwarded to it, and the signed v1.0.0 tag
was pushed. Current-state wording now says so in README.md,
planning/README.md, BUILD-MILESTONES.md and VERSION.md. BUILD-MILESTONES.md's
header had been stale since M8. The M11 report is not edited: its §T
records the state at closeout.

v1.1 plan. planning/V1.1-PLAN.md triages the post-v1 backlog and the other
recorded v1 residual risks, and orders them into work packages, not
milestones:
- A1: a context-window safety reserve, plus reporting a turn the server
  truncated
- A2: removing protocol echoes from stored narration, and a genre-neutral
  state rule
- B: long-term memory retention that holds without help from state
- C: browser coverage of Retry, Save Points, correction, length, failure
  and export download
- D: integrity_check on backups, and a warning when an export exceeds the
  import limit
- E: WCAG 1.4.11 control-boundary contrast

Scheduled backups, the import limit, identity detectors and duplication
suppression move to v1.2; media adapters are future work. The first brief
to write is A1.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VvegagkhuCZoFPdv4M1egY
This commit is contained in:
JesseMarkowitz
2026-09-14 08:19:31 -04:00
co-authored by Claude Opus 5
parent 432f04100b
commit ac465ed867
5 changed files with 983 additions and 33 deletions
Download Patch File Download Diff File Expand all files Collapse all files
planning/README.md
+42 -27
View File
@@ -2,11 +2,14 @@
**This file is the index. Start here.**
**Current state:** Phase 0 complete; AI-DnD forked as the production base;
**milestones M1 through M11 complete**. **M11 was accepted at its closeout
(2026-09-14), and the v1 release gate passed** on the release-candidate tree.
There is no further planned milestone. The signed closeout commit and any
`v1.0.0` tag are separate events and the repository owner's to perform. M1-M6 were accepted on the dates below (M3 and M4: 2026-09-03;
**Current state:** **v1.0.0 released on 2026-09-14. v1.1 planning has begun.**
Phase 0 complete; AI-DnD forked as the production base; **milestones M1
through M11 complete and closed**. M11 was accepted at its closeout
(2026-09-14), the v1 release gate passed on the release-candidate tree, and the
owner then signed the closeout commit (`432f041`), fast-forwarded `main` to it,
and created and pushed the signed tag `v1.0.0` pointing at it. v1.1 development
is on the `v1.1-development` branch, from that commit, and is planned in
`V1.1-PLAN.md` as work packages, not milestones. M1-M6 were accepted on the dates below (M3 and M4: 2026-09-03;
M5: 2026-09-04; M6: 2026-09-06). M5 and M6 were each accepted only after an
independent review found a real defect and a corrective pass fixed it.
@@ -46,13 +49,18 @@ The closeout repeated the browser, offline and identity runs on the exact
release-candidate tree (`3652dc6`), and recorded the acceptance (report §S and
§T). **The v1 release gate passed.**
**Not yet happened**, and each a separate event:
- the owner signing the closeout commit;
- merging to `main`, which still points at M10;
- any `v1.0.0` tag.
**The release, 2026-09-14.** The three events the closeout left to the owner
have all happened:
- the closeout commit is signed, as `432f041`;
- `main` was fast-forwarded to `432f041`;
- the signed tag `v1.0.0` points at `432f041`, and is pushed.
**There is no further planned milestone and no M12.** Post-v1 work is backlog
(`BUILD-MILESTONES.md`, *Post-v1 backlog*).
The M11 report's §T still lists the last two as not done. That table records the
state at closeout and is deliberately left as written.
**There is no M12.** Post-v1 work is organised as **v1.1 work packages** in
`V1.1-PLAN.md`, which triages the *Post-v1 backlog* recorded in
`BUILD-MILESTONES.md`.
**Package version:** see `VERSION.md`, which records what each revision changed
and why.
@@ -122,7 +130,8 @@ Two standing qualifications:
| `SECURITY-THREAT-MODEL.md` | The trust boundary, and the inference endpoint policy as implemented. |
| `MEDIA-EXTENSION-CONTRACT.md` | The contract future image/video/audio/TTS/STT work must fit. |
| `BROWSER-UX-SPEC.md` | The browser surface, and what is deliberately not in it. |
| `BUILD-MILESTONES.md` | M1-M11, what each delivers, what is done, and the notes each milestone leaves its successors. |
| `BUILD-MILESTONES.md` | M1-M11, what each delivers, what is done, and the notes each milestone leaves its successors. Closed history; not extended. |
| `V1.1-PLAN.md` | **Post-v1 work.** The triaged backlog, the ordered v1.1 work packages with acceptance criteria, the v1.1 release criteria, and what is deferred. |
| `V1-ACCEPTANCE-TESTS.md` | The pass/fail contract v1 is measured against. |
| `TEST-CAMPAIGN-FIXTURE.md` | The standard campaign the acceptance tests are run on. |
| `VERSION.md` | Package revision history: what each closeout changed. |
@@ -133,7 +142,8 @@ Two standing qualifications:
1. This file.
2. `SPECIFICATION.md`
3. `TECHNICAL-DESIGN.md`
4. `BUILD-MILESTONES.md` — find the milestone you are being asked to do.
4. `V1.1-PLAN.md` — find the work package you are being asked to do.
`BUILD-MILESTONES.md` is the v1 history behind it.
5. `STORY-BRANCH-SEMANTICS.md`
6. `DATA-MODEL.md`
7. `CONTEXT-AND-MEMORY.md`
@@ -185,7 +195,9 @@ that is the one the next milestone's planning has to consult:
It stays in `reports/` after acceptance. The rotation moves a report to the
archive when the next milestone's report is written, and after M11 there is no
next milestone. Nothing here calls for moving it, so no new convention was
invented to do so.
invented to do so. `V1.1-PLAN.md` asks each v1.1 work package for a report of
its own; when the first is written, it joins this one in `reports/` and the
rotation is decided then.
M9's and M10's reports both moved to `archive/milestone-reports/` when this one
was written. M9's had been kept here past its turn because M9 was unaccepted;
@@ -337,27 +349,30 @@ Milestone M11 COMPLETE / ACCEPTED (2026-09-14)
|
v
v1 release gate PASSED (2026-09-14)
signed release commit and v1.0.0 tag:
the repository owner's, not yet done
|
v
Post-v1 backlog only; no milestone planned
v1.0.0 RELEASED (2026-09-14)
signed tag on signed commit 432f041;
main points at the same commit
|
v
v1.1 PLANNING (from 2026-09-14)
branch v1.1-development; V1.1-PLAN.md
work packages, not milestones
```
## Stop Rule
**One milestone at a time. Do not begin a milestone before its brief exists.**
**One work package at a time. Do not begin a work package before its brief
exists.**
**Every planned milestone is complete, and M11 is accepted.** The v1 release gate
passed on 2026-09-14 (M11 report §T).
**Every v1 milestone is complete, M11 is accepted, and v1.0.0 is released**
(2026-09-14, tag `v1.0.0` on `432f041`).
The next actions are the owner's:
1. sign the closeout commit;
2. decide on the `v1.0.0` tag, pointed at that signed commit.
Neither is a milestone. **Do not begin post-v1 work as though it were a v1
milestone.** Anything after v1 starts from the *Post-v1 backlog* in
`BUILD-MILESTONES.md`, with a brief of its own.
**Do not begin post-v1 work as though it were a v1 milestone, and do not create
M12.** v1.1 work is the ordered work packages in `V1.1-PLAN.md`. Each starts
only from a coding brief of its own, and stops at its own boundary for review.
The plan names the brief to write first.
All three questions the M8 debt raised against M9 are settled and recorded:
the bundle carries historical context snapshots (`DATA-MODEL.md` §29); story