BRANCHWRITE

Problem

Desktop writing tools need clear persistence and recovery boundaries, while their public descriptions must stay aligned with the source being discussed.

Approach

This conservative entry identifies BRANCHWRITE as a version-persistence case study built around Vue, Tauri, and SQLite. It does not reproduce stale version labels, automatic-save language, deleted file maps, or a repository link.

Contribution

The publishable scope is limited to the persistence case-study framing. No state-of-the-art, release-version, performance, or automatic-save claim is made.

Evidence

The repository link remains withheld while licensing and documentation inconsistencies are remediated. With no public evidence link, this page makes no broader product claim.

Verification

The wording was checked against the locked publication audit on 2026-07-18. Linking requires remediation and a new audit.