Read a saved answer offline
Read a saved answer offline
In Evidence, open a saved selected-evidence question or manual structured briefing
and choose Export HTML. Save the .html file, then open it in a browser. The
file remains readable after resmon closes. The existing Export this answer and
selected text action still produces the three-member ZIP.
Each answer citation links to its exact quote and codepoint range beside the corresponding frozen source. Return to this answer citation goes back to that specific citation, including when the same quote appears more than once. The document’s section links, ordinary keyboard Tab/Enter navigation and native details control require no script. The system-font layout wraps long text and identities. Expand the identity disclosure before printing if you collapsed it.
The document includes only saved selected excerpts and selected local note bodies. Notes retain their saved IDs, revisions and anchors as owner commentary; they are not authenticated provenance or document evidence. Known, selected, anchor-checked and unexamined page counts use the saved selection basis. Missing values remain unknown. Requested connection/model/effort, literal model observations and reported token counts are separate. Reported tokens are not a bill; billing stays unknown.
An admitted or running export is a snapshot, and may be incomplete. Refused, failed, cancelled and interrupted results retain their state, available text, saved errors and cleanup limits. Export does not resume or stop the answer, invoke a model, re-extract pages or read current originals. Later note or membership changes do not update a saved answer. Missing originals do not prevent reading the frozen selection. Corrupt saved data is refused without repair or fallback.
Citation checks establish text identity only. They do not establish semantic support, research quality, truth or live-model quality. Unselected pages and files are unexamined. The file is not a full-paper archive, embedded PDF, encrypted backup, restore format or automatically updated report. Sharing it shares its saved text, which may contain private material.
Text remains literal, including HTML-looking strings and URLs. The app supplies the markup and bounded CSS; the file has no executable scripts, remote fonts, images, forms or external links. Only generated document fragments navigate. A restrictive CSP adds browser-enforced protection where supported; escaping and the absence of active surfaces do not depend on CSP support. No universal browser confinement is claimed.
The final escaped UTF-8 document has a 4 MiB ceiling and is refused rather than truncated if that ceiling is exceeded. The download checks the saved vault/project/answer/request and format identities, length, SHA256, UTF-8 and cancellation before offering the file to the browser. Check the browser’s chosen destination: delivery to the download flow is not proof of a human Save or Cancel. Synthetic Chromium checks do not establish physical Android, other browser engines or a native file chooser’s behavior.