A Bookmark Can Keep More of the Evidence

A bookmark usually remembers an address. Research often needs more: what the capture recovered, whether it was complete, and which evidence was available when you read it.

Arivu now keeps that trail closer to the bookmark. Reader pages show capture-attempt history and retained source evidence, including provenance and quality details when available. They also remember scroll progress, so returning to a long source does not mean starting over.

See What Happened During Capture

Web capture is not always all or nothing. A page can return useful text with incomplete metadata, or a later attempt can recover more than an earlier one. Capture history makes those states visible instead of flattening them into a single unexplained result.

Source evidence stays distinct from generated material. A summary can help you orient, but it is not the source itself. When the retained evidence is incomplete, Arivu can correctly keep a short summary or no summary rather than expanding beyond support.

Preserve a Rendered Artifact Selectively

Some research depends on presentation. A screenshot can retain a visible arrangement, and a PDF can keep a longer rendered document together. Arivu can now accept those artifacts from an operator-configured browser preservation helper after a successful direct capture.

The helper is disabled by default. Operators decide whether preservation is enabled, which artifact types are permitted, and the time and size bounds. Ordinary capture does not require it.

That boundary matters. Screenshot and PDF preservation is not a claim that every page can or should be reproduced. It does not make weak evidence authoritative, and it should not be used to bypass access controls. It is an optional tool for cases where a rendered record adds legitimate research value.

Keep Artifacts with the Data

Retained artifacts live in a private asset store adjacent to SQLite and remain owner-authenticated. Installer-managed backups now copy the adjacent asset store except staging with the database snapshot and write a versioned size/hash manifest. Restore verifies a present manifest and treats those parts as a pair.

Account-level JSON export remains portable, but it is a different boundary from a complete host recovery. If preservation artifacts matter to you, keep and test the installer backup.

Existing bookmarks, imports, exports, browser extension capture, CLI behavior, and ordinary provider-optional processing remain compatible. The new evidence layers add context without making browser preservation or AI a capture prerequisite.

Read Preservation and Sharing for the current workflow and boundaries.