ZNF133
Use this first to see the full evidence-to-experiment route for a muscle-assay draft.
Reviewer guided tour
Review the Workbench in one bounded path.
This page gives reviewers a short route through the productized surfaces added around the frozen database resource: gene profile, comparison dashboard, Planner builder, visual Study Card and validation/registry gates.
Reviewer guided tour
Search gene → Compare candidates → Build Study Card → Inspect visual card → Validate/register
This pipeline-style tour tells a first-time reviewer what to open, what visual result to expect and which boundary must remain intact.
Do not overclaimNo ranking, no therapeutic efficacy, no clinical decision support and no P1/P2 disease-prediction unlock.
1 · Search gene
Start with one typed gene record
Gene visual profile
A single gene view reorganizes frozen fields only; it does not create a new rank.
2 · Compare candidates
Contrast a small candidate set
Comparison visual dashboard
Input order is preserved; no winner, score, cluster or therapeutic priority is computed.
3 · Build Study Card
Generate the next-experiment route
Planner visual builder
The Planner is a pipeline-style route, not an intervention recommender.
4 · Inspect visual card
Read the stable Study Card object
Study Card visual summary
Cards remain DRAFT until required fields are registered and checksummed.
5 · Validate/register
Confirm gates before any claim expansion
Validation and registry gates
P1/P2 prediction claims remain locked; formal v1.0 still requires external gates.
Three example entrypoints
A reviewer can inspect three different branches immediately
CPEB1
Use this to inspect the expression-feasibility branch before perturbation escalation.
GFOD2
Use this to confirm that provisional external evidence is not silently promoted without provenance.
What this tour demonstrates
A governed evidence-to-experiment product path
The tour links existing visual surfaces: gene profile, comparison dashboard, Planner builder, Study Card visual summary and registry/validation gates.
What it does not demonstrate
No disease-prediction or therapeutic claim
The guided tour is a reading path through frozen objects. It does not change evidence levels, infer missing approvals, mint a DOI or authorize formal v1.0.
What visual result should I see?
Each stop has one primary visual check
| Stop | Expected visual result | Boundary check |
|---|---|---|
| 1 · Search gene Start with one typed gene record | Gene visual profile | A single gene view reorganizes frozen fields only; it does not create a new rank. |
| 2 · Compare candidates Contrast a small candidate set | Comparison visual dashboard | Input order is preserved; no winner, score, cluster or therapeutic priority is computed. |
| 3 · Build Study Card Generate the next-experiment route | Planner visual builder | The Planner is a pipeline-style route, not an intervention recommender. |
| 4 · Inspect visual card Read the stable Study Card object | Study Card visual summary | Cards remain DRAFT until required fields are registered and checksummed. |
| 5 · Validate/register Confirm gates before any claim expansion | Validation and registry gates | P1/P2 prediction claims remain locked; formal v1.0 still requires external gates. |
Identity and citation anchors
Files a reviewer should cite or checksum
| Object | Path | Purpose |
|---|---|---|
| Release manifest | api/v1.1/release_manifest.json | Current database-resource identity and archive pointers. |
| Overlay identity | api/v1.1/overlay_archive_identity.json | Current Workbench overlay filename, size and SHA-256. |
| Reviewer entrypoints | api/v1.1/reviewer_entrypoints.json | Machine-readable guided-tour path used by this page. |
| Deposit manifest | downloads/v1_deposit_manifest.json | Current DOI deposit candidate file set and supporting objects. |
| QA status | api/v1.1/site_quality_status.json | Machine-readable website quality and lock status. |
| External gate handoff | downloads/V1_EXTERNAL_GATE_HANDOFF.md | Human/institution inputs required before formal v1.0. |
External gate reminder
Formal v1.0 remains locked until DOI, institution-approved data licence, institution-approved code licence, and author/institution-approved maintainer/contact metadata are supplied and validated through the strict external gate validator.
Open external authorization dossier · Download external gate handoff