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

Apply post-M1 corrections to the planning package

Browse Source
This commit is contained in:
JesseMarkowitz
2026-09-02 06:03:10 -04:00
parent 645f07f06d
commit 1a28a9a708
8 changed files with 304 additions and 35 deletions
Download Patch File Download Diff File Expand all files Collapse all files
planning/README.md
+29 -8
View File
@@ -1,7 +1,7 @@
# Adventure Storyteller Planning Package
**Status:** Phase 0 complete; architecture selected; planning revision ready for review.
**Production coding:** Not yet authorized. Review this package before preparing the first implementation prompt.
**Status:** Phase 0 complete; architecture selected; **Milestone M1 implemented and accepted (2026-09-02)**.
**Production coding:** Underway, milestone by milestone. M1 is done; M2 is the next milestone to brief.
This package contains the current product requirements, final Phase 0 architecture decisions, detailed subsystem designs, acceptance tests, research evidence, and the production milestone plan for the local-only interactive-story project.
@@ -153,14 +153,17 @@ Phase 0 research and spikes COMPLETE
Architecture/fork decision COMPLETE
|
v
Planning package revision CURRENT REVIEW
Planning package revision COMPLETE
|
v
Approve planning package
Approve planning package COMPLETE
|
v
Prepare one implementation prompt
for Production Milestone 1
Milestone M1 COMPLETE (2026-09-02)
fork + offline baseline see planning/reports/M1-*.md
|
v
Milestone M2 NEXT — brief not yet prepared
|
v
Implement and review milestone-by-milestone
@@ -168,6 +171,24 @@ Implement and review milestone-by-milestone
## Stop Rule
**Do not begin production coding from this package yet.**
**One milestone at a time. Do not begin a milestone before its brief exists.**
The current action is to review the planning changes. No replacement Codex prompt has been prepared in this revision.
M1 is complete and accepted; its evidence is in `reports/M1-BASELINE-REPORT.md`
and `reports/M1-IMPLEMENTATION-REPORT.md`. **No M2 brief has been prepared.**
The current action is to review the post-M1 planning corrections below before
writing one.
### Post-M1 corrections applied (2026-09-02)
Implementation evidence contradicted or under-specified six places in this
package, and a seventh was added on review. All seven are now corrected:
| Document | Correction |
| --- | --- |
| `DECISIONS/002-ollama-only-v1.md` | New section: a trusted-LAN Ollama may be HTTPS with a private CA; verify against the OS trust store; full certificate and hostname checking; no bypass option. |
| `DECISIONS/004-local-only-production.md` | New *Testing Consequence*: offline tests need a fresh cache and no route out. Vendored runtime artifacts should be integrity-verifiable. |
| `V1-ACCEPTANCE-TESTS.md` A05 | Pass conditions reworded around *accepted* history; explicit note that the user's submitted text is deliberately retained. |
| `V1-ACCEPTANCE-TESTS.md` A06 | Now requires a real second machine and an HTTPS endpoint with a locally issued certificate; a plain-HTTP LAN test is no longer sufficient evidence. |
| `V1-ACCEPTANCE-TESTS.md` §3 | Record CPU/GPU/RAM: cold model load on a CPU-only host exceeded the inherited 120 s timeout. |
| `BUILD-MILESTONES.md` | M1 marked COMPLETE with the capabilities it delivered; M2's endpoint-policy line reframed from inventing trusted-LAN support to narrowing it. |
| `TECHNICAL-DESIGN.md` §5 | Runtime boundary restated: the storyteller is loopback-only, inference may be same-host *or* trusted-LAN, and the two are independent. Adds the TLS/private-CA rule. |