Synthetic readiness workspace · browser-local · 2.0.30-wip
Practice the review path.
Collect no real reviewer data.
Inspect consent, private verification, source routing, redaction, public candidates, adjudication handoff, correction, withdrawal, deletion requests, and appeals using eight deterministic synthetic fixtures.
No submission service exists. This page has no account, upload endpoint, analytics, external model, database, or remote storage. Work stays in browser memory until you explicitly download it.
Every example is fabricated for interface testing, unsuitable for publication, and incapable of establishing identity, expertise, local relationship, community representation, consent, independent review, or approval.
Direct answer
What does this workspace do?
It demonstrates a fail-closed reviewer-evidence workflow without accepting real submissions. A local user can inspect synthetic states, import files into browser memory, preserve original bytes, review nine consent choices, preview redactions, separate private and public records, queue source verification, prepare an adjudication handoff, and export local bundles.
- Storage
- Browser memory + explicit downloads only
- Fixture states
- 8 synthetic examples
- Private/public split
- Required
- Publication state
- Blocked
How to use this page
Keep the evidence lifecycle separated.
Imported bytes, reviewer-owned fields, source verification, editorial adjudication, public disclosure, and append-only history are different records. The workspace never promotes one layer into another by inference.
-
01
Import without rewritingOriginal bytes, names, media types, unknown extensions, and invalid files remain downloadable.
-
02
Review private provenanceIdentity, contact, qualification, language, conflicts, and safety material stay private by default.
-
03
Resolve consent explicitlyParticipation, quotation, paraphrase, attribution, retention, anonymization, publication, withdrawal contact, and deletion handling remain separate.
-
04
Verify sources separatelyA reviewer response is not current truth; public sources receive their own verification outcome.
-
05
Handoff without approvalAn adjudication bundle records open questions but does not invent an accountable adjudicator or decision.
Local-only workbench
See exactly what stays private.
See exactly what may leave.
Choose a synthetic state or import a local file. The interface fails closed when consent is missing, contradictory, confidential, non-public, or withdrawn.
Private partition
Reviewer-owned and verification material
Inspect complete private synthetic JSON
Nine separate permissions
Consent matrix
Change a synthetic selection locally to see the gate and preview update. The workspace never guesses unresolved intent.
Before export
Redaction and disclosure preview
Consent-bounded candidate
Public partition
Contact details, precise location, employer details, immigration status, protected characteristics, and private verification material remain excluded.
Separate evidence check
Source-verification queue
A reviewer response is preserved as that reviewer’s claim. A verifier must separately record what the supplied source supports, contradicts, or leaves unresolved.
Editorial handoff
No adjudicator is implied
Append-only lifecycle
Correction, withdrawal, deletion, and appeal
Original artifacts
Preserved bytes and quarantine
Invalid JSON, unsupported records, and unknown extensions remain unchanged and downloadable. The workspace does not silently repair, merge, or discard them.
Publication and privacy boundary
A valid record can still be unusable.
Structural validity means only that a record can be reviewed. It does not prove the person, relationship, evidence, consent, legal basis, local acceptance, neutrality, or editorial decision.
Protect identity and eligibility
Identity, contact, employer, precise location, immigration status, protected characteristics, and private verification do not enter public candidates.
Export only within scope
Quote, paraphrase, attribution, anonymity, and publication choices are evaluated separately and unresolved permissions block export.
Do not erase the record silently
Corrections, supersession, withdrawal, deletion requests, and appeals receive new dated events while earlier records remain addressable where retention rules permit.