The research question
A collection stops exchanging data because its permission confirmation expired while the authority device is unavailable. The user can still read already authorized local documents and prepare drafts. If the application shows only a large disconnected error, the user may assume their files are lost or repeatedly retry an operation that cannot currently succeed. Local-first research connects collaboration with ownership and useful offline work. The design challenge is to specify which local operations remain meaningful when other participants or the authority for a business decision cannot be reached.
A concrete design choice
The proposed status separates local availability from exchange permission and peer reachability. It explains what remains possible, why synchronization is paused and what condition will allow it to resume. Pending work should be visible without generating a constant stream of identical warnings. A user can continue a permitted local task while the system avoids exporting new information under stale rights. When exchange resumes, the application reconciles the actual durable state rather than assuming every previously queued item was delivered. This makes the failure mode understandable and prevents a network condition from obscuring the state of local evidence.
What would demonstrate usefulness
Simulate an unavailable authority while retaining local documents. Check reading, draft persistence and the accuracy of pending-transfer counts. Then restore access and verify reconciliation. The acceptance question is whether users can continue appropriate work and understand the limitation without confusing paused exchange with lost or corrupted data.