Repository navigation
AI: Powered Document (standalone / from list / from document / research URL) #9
Description
Part of #3 — AI Writing Assistance is entirely missing from the Android app
Web behaviour: a Powered Document button on the Documents page drafts a full document
in one of four modes:
- Standalone article from a topic the user describes.
- Derived From List — a write-up based on one of the user's lists.
- Derived From Article — a new document based on an existing one.
- Research URL — a document based on a web page the user points at.
For the derived and research modes the user picks the source list / document / URL. The draft is
always previewed before it is saved.
- Source pickers should reuse the existing lists and documents pickers rather than new ones.
POST /api/ai/suggest→ preview;POST /api/ai/generate→ saved document.
Tests: one ViewModel test per mode (source selection → suggest → confirm); preview is not
persisted if the user backs out.
Filed from the parity review of feature/parity-wip @ 14d7795 against interlinedlist.com (OpenAPI /api/openapi.json, 233 paths) and the public help centre.
Activity
Adron commentedon Sep 16, 2026
Implemented in the PR above (branch
issue/9-ai-powered-document). Closing here — review and any follow-up happens on the PR.One architectural decision needs your ruling, and it is better settled now than after four more AI issues: this PR introduces the repo's first feature→feature dependency,
:feature:documents→:feature:ai. There is no way to consume #4'sAiRepository/AiGate/ConfirmedPreviewwithout it.The case for it:
:feature:aiis a leaf capability module — only:core:*dependencies, no navigation, no screens — and #4 built it explicitly to be consumed. The case against: the no-feature→feature convention is what has kept the parallel work conflict-free.If you would rather it were
:core:ai, say so and I will move it before #5, #6, #7 and #8 each add the same edge.On the issue itself: the four modes are sent as
context.mode(article/from_list/from_article/research_url) and only a reference is ever sent — the server resolves the source. Backing out of a preview is structurally incapable of writing, since/generateonly accepts aConfirmedPreviewthat an on-screen preview must mint.The list source picker does not import
:feature:lists;:feature:documentsowns a one-endpoint read-only/api/listsclient instead — so no documents→lists edge was created.merge: #9 AI Powered Document (PR)