Beth 2.0 · collection reliability · 7 October 2026
Collect expertise without losing the work.
The local collection engine has been strengthened and checked with fictional accounts. Specialists, managers and experts can record structured contributions, return to saved studies and submit versions for human review.
35 account and collection checks · 63 validation, concurrency and role checks · 17 draft recovery checks · 8 database backup and restore checks.
Browser checks also covered registration, saving, two-tab conflicts, server interruption, sign-in recovery, page refresh recovery, submission and a downloaded JSON review pack.
What now works
| Safeguard | What it does for the contributor |
|---|---|
| Account separation | Studies belong to the signed-in account. A change of account cannot silently receive another account’s pending answers. Test accounts use a separate cookie and database. |
| Reliable saving | Pending saves retain their request identity. A lost response can be retried without creating another revision. Answers typed while a save is running are saved afterwards. |
| Conflicting edits | A stale tab cannot overwrite a newer saved study, including when its upload arrives late. Download the recovery draft and compare it with the saved copy. |
| Recovery in the same tab | Unsaved answers are retained in tab storage across a refresh. Resume them after signing in to the original account. An unavailable browser store produces an explicit warning. |
| Useful quality checks | Missing fields, missing evidence, honest unknowns, invalid values and contradictory source dates stay visible. Filled topics and format-complete topics are counted separately. |
| Stable submissions | One saved revision creates one review submission. Repeated clicks or retries do not duplicate it. Later edits form a draft while the submitted snapshot and its question definitions remain unchanged. |
| Review handoff | The saved JSON pack includes the respondent, context, typed answers, unresolved items, topic-to-engine links, earlier submissions and any preserved legacy workshop answers. A direct authenticated download link is available. |
| Private database copies | A verified backup is created at startup when no current backup exists, then checked hourly and refreshed when it is more than 24 hours old while the full backend is running. Copies include committed database changes and use restricted file permissions. |
Use it for a supervised local collection
- Create your own collection account or sign in.
- Choose one role, service and anonymised founder situation.
- Answer the relevant topics. Label estimates and unknowns honestly.
- Wait for “Saved”, then check the review pack and its gaps.
- Record a submission and download the saved review pack.
- Give the pack to the named reviewer. Retain a private copy away from this computer.
Still needed for a shared team launch
- Hosted HTTPS access and verified identity with password recovery.
- Named reviewer accounts, permissions, review assignments and return-for-correction workflow.
- Off-device backup, storage retention policy and periodic recovery drills.
- Approved rule publication, evidence verification, evaluation and rollback.
- Operational monitoring and capacity testing against the intended number of users.
These are production requirements. They are not claimed as completed by this local reliability check.
If saving is interrupted
The server is unavailable or sign-in has expired
Keep the tab open. Choose Retry saving after the full server is back, or Sign in and recover with the original account. You can download the unsaved recovery draft. Reload and recover retains a recovery copy before refreshing; reopen the study and choose Resume recovered answers.
Another tab changed this study
Download the recovery draft first. Choose Review saved copy to see the newer saved data. Re-enter the changes you want to keep after comparing the copies. No automatic merge guesses which conflicting answer is correct.
The tab or computer may be closed
Save and check the acknowledgement first. Tab recovery is session storage, not an off-device backup: closing the tab or clearing browser data can remove it. A downloaded recovery draft is a reference copy; automatic re-import is not implemented.
Restoring a database backup
The maintainer must stop the backend, preserve the current database and its journal files, and restore the chosen verified private backup as a complete database. Test restoration in isolation first. Do not copy an active database file on its own; committed answers may still be in its journal.
Automatic checks verify structure and obvious inconsistencies. They do not prove a tax interpretation, citation, measured effort, quoted price or specialist qualification. Contributions remain candidate inputs until qualified reviewers approve them. This form does not retrain an LLM or change live Beth rules.
