MATHEMATICAL SYSTEM DETECTOR · WEB LABORATORY
Measure signals. Preserve uncertainty.
Run the BenchEWS 2.0 scientific modules in a bounded server-side laboratory. The interface reports what was measured, what remains experimental, and how the result was produced.
Numerical outputs and provenance originate from the verified Scientific Core and bounded worker execution.
Interpretation is module-specific. No global BenchEWS score is calculated or displayed.
CRTI is always labelled Experimental · Not scientifically validated.
00
Scientific Cockpit
Four separate instruments expose the currently available Scientific Modules. The smoke test uses deterministic module-matched reference inputs; it does not interpret a research dataset or calculate a global score.
01–12
Studio 2.0 Panels
The panel names and order mirror Desktop Studio 2.0. Web-only implementation differences must never change scientific meaning.
PANEL 01 · CANONICAL V43 REFERENCE
Scientific Reference Benchmark
Run the fixed deterministic scientific smoke test through the same Scientific Core used by Panel 12. The four readings are demonstration outputs only; no threshold or real-system diagnosis is implied.
Not yet run.
PANEL 02 · CANONICAL V43 WORKFLOW
Idea
This stage precedes object creation. It is intentionally a scratch notepad only: nothing entered here is persisted and there is no Idea object in the v43 object model.
Formalization Status: NOT AVAILABLE · No Project is created from these notes automatically.
PANEL 03 · CANONICAL V43 WORKFLOW
Project
Create the same Draft Project object used by Desktop Studio 2.0. The object is stored through the canonical v43 RegistryService.
No project created in this session.
PANEL 04 · CANONICAL V43 WORKFLOW
Configuration
Create the four traceable Desktop objects required by a Benchmark, then bind them into the canonical v43 Benchmark configuration.
No benchmark configured in this session.
PANEL 05 · CANONICAL V43 WORKFLOW
Validation
Run the original v43 SchemaService against the current Benchmark configuration. A successful check advances Draft → Configured → Validated and records both transitions in the audit trail.
Create a configuration first.
PANEL 06 · CANONICAL V43 WORKFLOW
Execution
Advance the current validated Benchmark through the original Desktop lifecycle. This controls workflow state only; scientific computation remains in the Scientific Modules panel.
Validate a benchmark first.
PANEL 07 · CANONICAL V43 WORKFLOW
Verification
Apply the original v43 verification transition to a completed Benchmark. Verification remains separate from interpretation.
Complete execution first.
PANEL 08 · CANONICAL V43 WORKFLOW
Interpretation
Advance a verified Benchmark into the original v43 Interpreted state. This lifecycle transition does not generate a global BenchEWS score or add Web-only scientific meaning.
Verify the benchmark first.
PANEL 09 · CANONICAL V43 WORKFLOW
Publication
Create a canonical v43 Publication object, generate its manifest and RO-Crate package, and verify package integrity locally. External publication remains a separate explicit action.
No publication object created in this session.
PANEL 10 · CANONICAL V43 WORKFLOW
Reuse
Lists only Publications whose registry state is Published, matching Desktop v43. Compatibility is not tracked by the object model and is therefore shown as NOT VERIFIED.
Compatibility: NOT VERIFIED
PANEL 11 · CANONICAL V43 WORKFLOW
Object Browser
Lists the same four browsable registry types as Desktop v43. Filtering is client-side over already-fetched id and state; it adds no persistence capability.
01
Web Laboratory
Up to 100,000 observations and up to 64 channels, subject to the request-size limits of 4 MiB JSON and 2 MiB CSV.
Input
0 B
No file selected.
Use a deterministic reference-style dataset matched automatically to the selected scientific module.
Scientific module
The service may queue or reject work when capacity is full. Queue position is not available.
02