Last reviewed: 2026-10-25. F01 project-management verification passed for
commit d1f4402 in GitHub Actions.
This is the working overview of planned and implemented product features. The feature map defines the approved scope; the linked requirements define acceptance criteria. Update this overview when a feature's plan, implementation, or verification status changes.
- Not started: no product implementation exists; approved requirements may exist.
- Partial: usable behavior exists in the prototype, but required behavior is missing.
- Implemented: the selected scope is implemented and its acceptance criteria have been verified, with evidence linked here.
- Future candidate: outside the selected milestone; detailed requirements and an implementation plan are still needed before delivery.
Requirement approval, implementation-plan approval, code completion, and verification are separate states. An approved requirement does not mean that the feature is implemented or that its implementation plan is approved.
Browser backup/restore is implemented on feature/project-backup-restore.
The F07 verification report records
complete milestone roundtrip comparison, independent restored copies, invalid
archive rejection, all existing browser regressions, and fresh-container retention.
It closes the backup-dependent criteria in F01, F03, F05, F10/F11 and F19 for the
selected milestone scope. Local verification is separate from CI and live rollout.
F03/F19 panel/page lifecycle and F05 visual references (including F06 reference
access) are implemented on feature/panels-pages-and-references. See the
verification report,
panel/page plan, and
reference plan. F07 now closes backup-dependent criteria; see the completion record above. Historical verification below refers
to earlier increments unless explicitly updated.
The chapter plan and
asset/association plan were reviewed and implemented in
parallel on feature/chapters-and-assets. Local native/Wasm builds, linting,
unit/integration tests, Chromium workflows and fresh-container retention passed.
Evidence is recorded in the verification report.
This is local verification, not a new CI result or live deployment.
See the dependency and ownership review.
10 feature areas: 0 partial, 0 not started, 10 implemented for the selected first-milestone scope. F10 and F11 include only the selected image import, replacement, alternatives, and selection scope.
| ID / requirement | Requirement | Implementation plan | Delivery status | Available now | Remaining milestone work |
|---|---|---|---|---|---|
| F01 Project workspace and persistence | Approved | Project-management increment: Implemented; prototype storage plan implemented | Implemented | Create/open/switch independent projects, edit names/descriptions, autosave with save/failure status and guarded navigation; isolated images/revisions and restart retention verified in CI. | Selected milestone scope verified, including F07 roundtrip. Broader future features remain outside scope. |
| F02 Chapter management | Approved | Implemented | Implemented | Create/edit/order/open chapters; exact panel-count deletion confirmation, cancellation and retention verified locally. Shared library and other chapters remain intact. | Reference-image preservation will also be exercised when F05 exists. |
| F03 Panel planning | Approved | Implemented increment | Implemented | Full planning fields, blank drafts, chapter moves with preserved images/associations, confirmed deletion and layout-derived reading order. | Selected milestone scope verified, including F07 roundtrip. Broader future features remain outside scope. |
| F04 Reusable asset library | Approved | Implemented | Implemented | Characters, locations/equipment, names/descriptions/design notes, optional size, type browsing/search, shared identities and guarded deletion; persistence and browser flows verified locally. | No remaining F04 scope; reference images are F05. |
| F05 Visual references | Approved | Implemented increment | Implemented | Multiple labeled/described PNG/JPEG/WebP originals, thumbnail/larger views, validated import, confirmed removal and reopening. | Selected milestone scope verified, including F07 roundtrip. Broader future features remain outside scope. |
| F06 Panel–asset associations | Approved | Implemented | Implemented | Shared characters/equipment and optional location, independently removable associations, shared definitions and reference images from panels. | No remaining selected F06 scope. |
| F07 Project backup and restoration | Approved | Implemented | Implemented | Versioned self-contained browser export, validated restore into an independent copy, all structured data and original images, durable retry/cleanup and invalid-archive rejection. | No remaining selected F07 scope; scheduling and synchronization are excluded. |
| F10 Panel image import | Approved, selected scope | Full feature plan missing; prototype storage plan implemented | Implemented | PNG/JPEG/WebP imports up to 20,000,000 bytes, project-owned originals, validation and independent replacement. | Selected milestone scope verified, including F07 roundtrip. Broader future features remain outside scope. |
| F11 Image alternatives and selection | Approved, selected scope | Missing | Implemented | Retained image alternatives, visual/dropdown selection and return to an earlier image; server persistence. | Selected milestone scope verified, including F07 roundtrip. Broader future features remain outside scope. |
| F19 Page layouts | Approved | Implemented increment | Implemented | Multiple chapter-owned pages, creation/reordering/confirmed removal, all templates, cross-page placement, derived numbers, fitting and preserved unplaced panels. | Selected milestone scope verified, including F07 roundtrip. Broader future features remain outside scope. |
Projects start with four blank panels in their first chapter. Users can create additional chapters and panels; each chapter supports multiple composition pages. Removing the last page preserves editable, unplaced panels.
These nine features have no product implementation or dedicated implementation plan. They remain candidates outside the first milestone. F13 is explicitly desired, but its milestone and provider have not been selected.
| ID | Feature | Next requirement work |
|---|---|---|
| F08 | Extended story structure | Decide whether story days and scenes are needed. |
| F09 | Prompt construction | Define editable prompts derived from structured panels/assets/references. |
| F12 | Canon and continuity records | Define statuses, established facts and protection of canonical material. |
| F13 | Integrated image generation | Select milestone, service, credentials/cost handling and independent panel generation workflow. |
| F14 | Automatic reference selection | Define how suggestions are chosen and reviewed. |
| F15 | Consistency checks | Define which story/visual conflicts can be detected and how they are presented. |
| F16 | Chapter planning assistance | Define outline assistance and user control over generated suggestions. |
| F17 | Lettering and dialogue placement | Define editable lettering/captions on selected images. |
| F18 | Finished comic export | Define reader-facing output formats and export behavior. |
F10 generation provenance and F11 formal review/revision/approval also remain future scope; completing their selected milestone portions will not complete those broader capabilities. See the full inventory.
| Area | Repository implementation | Evidence / limits |
|---|---|---|
| Illustrated workspace design | Implemented: English Story Archive overview and editor using the same saved data. | Design plan and 2026-10-22 verification: native/Wasm checks, builds, Chromium desktop/phone and container retention. |
| Durable prototype storage | Implemented: PostgreSQL JSONB workspace/revisions, private S3-compatible images, upload recovery, personal access and same-origin writes. | Storage implementation record, architecture and persistence integration tests. This is the prototype data model, not complete milestone persistence. |
| Build and deployment pipeline | Implemented: Docker/CI verification and opt-in Render migration/deploy hook. | Deployment plan. Its recorded live activation/verification is pending; that is separate from code completion. |
The latest upload diagnostics record reports a live HTTP 503 whose provider cause remains unverified. Diagnostics are implemented; successful live image uploads still need confirmation. Historical live-activation notes do not establish the current provider state.
The F01 increment has fresh CI browser/integration verification linked above. Other feature statuses use code and existing records; this is not a live infrastructure audit. Implementation evidence: shared model, browser UI, HTTP routes, and browser smoke workflow.
The delivered steps have reviewed plans. Remaining steps still require their own implementation plans; the order below reflects current dependencies.
- F01 — real projects: define project boundaries, the durable data model, creation/opening/switching, and unsaved-change protection while preserving existing prototype work.
- F02 — chapters: add chapter ownership, editing, ordering and safe deletion.
- F03 + F19 — complete planning and composition: extend the chapter-owned panels/pages; add missing fields, panel lifecycle, page lifecycle and reading order. Preserve existing F10/F11 image behavior.
- F04 — reusable assets: add the library, search and stable shared identities.
- F05 + F06 — references and reuse: attach asset references and associate assets with panels, including access to definitions and safe deletion rules.
- F07 — recovery: implement and verify complete export/restore, including all images, relationships, page order and fitting settings. This closes the remaining backup criteria for F01, F05, F10, F11 and F19.
- Verify the complete first milestone: run the feature map's representative browser workflow, reopening and backup restoration; update each feature's status using its acceptance criteria and linked test results.
For each delivery step, create a focused plan under docs/plans/, review and
approve it using the development workflow, then
implement and verify. The F01 project-management increment is implemented and verified in CI. F02 and F04/structured F06 are now locally verified. F03/F19 and F05/F06 increments are now implemented; F07 backup and restoration is implemented and locally verified; future features need new scope/plans; F01's milestone persistence criterion is now covered by the combined F07 roundtrip verification.
Plan F02 chapters and F04 assets in parallel, then implement them after agreeing shared project-model and persistence contracts. Keep F03 panels and F19 layouts in one coordinated stream; it can run alongside F05 references after their respective chapter and asset foundations land. F06 associations needs stable panel/asset identities and can then proceed alongside F05. Plan F07 backup/versioning early, but complete its integration after the selected milestone data model is available. Dependent acceptance criteria remain open.
See parallel feature delivery for prerequisites, delivery waves, shared-file risks and agent ownership. This is a recommendation; focused implementation plans still require review/approval.
When work changes a feature, update its row with the plan link/status, available behavior, remaining acceptance criteria and verification evidence. Mark a milestone feature implemented only when its selected scope has been verified, including dependent backup/reopen criteria. Keep live operational verification separate from repository implementation and historical test results.