NMD-VCellNeuromuscular Virtual Cell Research PlatformTrust Center · Evidence → perturbation → experiment → outcomeNMD = neuromuscular disorders
For Reviewers Evidence Status Claims

Evidence Release 2026.08DMD context observedDMD candidate-conditioned prediction locked

View scientific status
Evidence freeze: 3 August 2026 P59 hold · scorer failure retained · no target score NAR working package · 6 main + 31 supplementary figures Resource: v1.2.0-measured-dmd-evidence Schema: 1.1 Open platform state → Open Trust Center → Open evidence dashboard → Open claim registry → Open release status →

Trust Center · local V201 candidate

One governance surface for evidence, meaning, applicability, release and maintenance.

Trust is not a badge or a second facts layer. It is the route that connects current status, Claim Objects, domain limits, release identity and operational quality without changing any scientific state.

Inspect five trust domainsOpen navigation contract
Navigation contract, not scientific evidence. V199 changed how users reach governed objects; V200 added the Model Evaluation Gateway; V201 preserves both while adding the Digital Tissue hypothesis map. DMD remains 0/21 directly measured candidate outcomes; the ZNF133 Experiment Plan remains unauthorized; the Outcome Ledger remains empty; production authority remains Sites v193.

Five trust domains

Each question has one canonical inspection path.

Evidence asks what exists. Meaning asks what it supports. Applicability asks where it travels. Release asks which object is current. Maintenance asks whether the delivery surface remains healthy.

Open platform state →
01 · Evidence

Measured, contextual, failed and missing states with a canonical evidence boundary.

Open Evidence →
02 · Meaning

Versioned Claim Objects, evidence roles, negative implications and claim ceilings.

Open Meaning →
03 · Applicability

Disease, cell, perturbation, time, endpoint and OOD limits separated from technical availability.

Open Applicability →
04 · Release

Production identity, publication packages, checksums and formal-release gates.

Open Release →
05 · Maintenance

Site quality, API health, provenance, update discipline and current operational boundaries.

Open Maintenance →

Canonical route map

Seven top-level destinations, shared by static and dynamic pages.

Gene and comparison pages live under Explore. Reliability, meaning, applicability, release and maintenance live under Trust. Benchmarks remain separate from model identities.

DestinationPurposeCanonical path
ExploreexploreFrame a disease, cell-state, perturbation or gene question and discover the relevant evidence objects./resource/
Virtual CellvirtualInspect prediction eligibility, domain match, uncertainty and abstention boundaries./resource/virtual-cell/
ExperimentsexperimentsConvert the next experiment into explicit design, registration and execution gates./resource/experiment-os/
ModelsmodelsInspect released ModelRun identities, model families and current capability boundaries./resource/models/
BenchmarksbenchmarksCompare evaluation tasks, baselines, generalization gaps and validation readiness./resource/benchmarks.html
DatadataOpen dataset cards, governed inventories, downloads and machine-readable resources./resource/datasets/
TrusttrustInspect evidence, meaning, applicability, release and maintenance as one governance surface./resource/trust/

Legacy compatibility

Stable context routes remain addressable.

The IA does not force redirects or erase deep links. These pages retain their own content and are classified under Trust in the shared navigation.

Claim boundary

Better routing does not upgrade evidence.

Information architecture changes discovery and routing only. It does not change evidence, model eligibility, experiment authorization, measured outcomes, publication readiness or production deployment state.

Does not imply: a new scientific claim · a newly eligible model · an authorized experiment · a measured outcome · a production deployment.