Start with the scientific workflow. Build reusable private workflows, review r34 provenance and access controls, then choose your deployment and research tools.
ISAES turns retained scientific results into eligible analyses, traceable findings, linked exploration and consistent reports. The dedicated page explains that machinery and the new autonomous investigations: contextual research, permitted computation and claim assessment under an explicit standing policy. The retained walkthrough covers the earlier reporting and reviewed-discussion modes.
From a research question to Python and a saved workflow.
Learn what the scientific Python program must contain, how to build it from the development guide, and how the workflow assistant can help implement a mathematical specification. Then follow the custom Qiskit study through validation, repeated runs, private versions and B2/B3 controls.
Follow the r34 SaaS workflow and examine how private layers can override equation implementations, with a recorded Bell study and retained equation-level test evidence. Use the chapters to find a step, or read the complete transcript.
Inside the research workbench5:42
r34 SaaS walkthrough · Narrated · English captions
A walkthrough of the research workflow with scripted AI replies and real numerical execution. Storage setup is shown.
Watch the B2 and B3 walkthrough for project sharing, viewer and editor grants, revocation, institutional AI policy and disclosure consent. Follow the GUI steps and the corresponding server enforcement checks.
Try the live hosted workbench, run PF Simulation locally or deploy your own service. For an introduction, watch the narrated r34 SaaS demo .
Live hosted trial / demo
Try PF Simulation in your browser.
Explore the PF Simulation hosted solution before choosing a deployment for your research. Open the workbench, sign up for a PF Simulation user account, then sign in to try its scientific workflows and research tools.
The hosted workbench opens in a new browser tab or window. Create your account and sign in there.
Prefer your own environment? Choose standalone use or host a service for your research group.
Standalone
Run the PF application in your own environment. Install the dependencies for your scientific workflows and open the local research workbench. Direct scenario CLI runs now retain execution provenance, with optional source export for replay.
Control local execution and retained data
Use the supplied application launchers
Retain source and input identities for CLI studies
Deploy on Hugging Face or use the complete Linux reference for PostgreSQL, durable state and rootless execution. Configure project membership, approved providers and disclosure policy, then qualify the deployment on its actual host.
The hosted trial provides access to the PF Simulation application. Standalone use and your own hosted deployment require the application package; this website provides the supporting documentation and examples.
Guides from the r34 package
From the first question to the next private layer.
Select a guide to read it here. Each guide includes a table of contents, a formatted download and a print-friendly view.
Start with the integration catalogue to understand applicability and required runtimes. Use the recorded satellite, Aer and ISAES Floquet Gallery bundles to inspect saved inputs, numerical outputs and exact reproduction steps.
The retained 239-page end-user manual, Edition 1.19.0, covers established workflows, configuration, interpretation and reports. Read the current workbench and maintenance guides alongside it for the October configuration, execution, tracking, cache, workflow and Assistant corrections. Chapter 32 adds an illustrated ISAES walkthrough: user choices and automatic processing, evidence and status interpretation, linked figures, saved views, exports, literature management, optional report discussion and autonomous investigations. The dedicated guides provide additional SDK, AI, BYOK, BYOS and access-control detail.
The headline reconciles passing test identities across retained release records from r9 through r34. Repeated runs and copied evidence do not add a new identity. Earlier release totals without surviving identity-level records are not invented. This is cumulative recorded coverage, not a claim that every test ran against the current source.
See which release groups contribute new test identities
Release group
Additional distinct passing identities
Earlier retained releases (r9–r33)
3,266
r34 core, BYOK/BYOS, qualification and access controls
1,157
Private workflows, startup and lifecycle
254
Reporting and literature management
73
ISAES analysis, evidence and assistant tests
516
ISAES documentation and navigation
31
Autonomous ISAES investigations
158
Attachment and upload maintenance
90
Save controls and feedback maintenance
50
HF gateway and deployment budget
226
Native HF runtime and recovery
346
HF isolation and immutable payload compatibility
195
HF deployment documentation
22
Execution lifecycle and artifact publication
343
Runtime lease and heartbeat consolidation
53
Configurable runtime scaling and reliability
233
HF and shared deployment consolidation
560
Public service, SMTP readiness and Micius/Refresh fixes
613
Refresh and authentication controls
20
Execution, live logs and Orbit Viewer recovery
123
Tracking preparation and controller connectivity recovery
114
Consistent configuration and live comparison controls
50
HF Astropy reference-cache initialization
26
Workflow page reliability and personal AI controls
53
Assistant recovery, loading and opening consolidation
85
Each identity is attributed to its first appearance in the retained ledger. Later executions of that same identity do not increase these additions.
Current corrections and retained acceptance
The latest Assistant consolidation records 305 passing Python tests (293 backend and 12 HTTP/BYOS), 232 UI fixture cases, 70 subtests and 49 assertion checks across 14 commands. These are separate counting units. Seven PostgreSQL-dependent cases were skipped and one scientific-worker case was deselected. The preceding workflow-reliability scope records 136 Python tests, 152 UI case/test executions (133 fixture cases and 19 focused input tests) and 39 separate assertion checks. Earlier configuration, tracking, execution and Astropy records retain their original source scopes. The autonomous release records 1,495 parent tests, 130 successful subtests and 4 JavaScript commands. Upload maintenance adds a recorded 293-test scope; save-control maintenance records 237 tests and 10 JavaScript commands. These overlapping executions are reconciled by identity, never added again to the distinct headline.
Scientific and platform regression
The retained 1,822-test full regression remains included in the cumulative identity union. Its 454 successful subtests are a different unit. Coverage spans numerical physics, quantum models, workflow lifecycle, authorization, disclosure controls, reporting, presentation and release integrity.
The operator supplied a successful consolidated HF deployment and startup record on 16 October 2026. That later observation adds no test identities and does not change the frozen package qualification flags. Browser responsiveness, live provider behavior and production capacity require their own evidence.
Numerical benchmark highlights
6,823audited benchmark and verification checks
46declared numerical studies
Numerical assertions and executed model runs have their own ledger. These checks are not added to the automated-test headline, and study coverage remains specific to declared models and references.
Retained study group
Checked evidence
Independent QuTiP quantum comparisons
3,829 checks. 748 cases across eight model families; repeated comparison receipts counted once.
535 checks. 27 completed numerical/reference-data preset studies; MATLAB and registration-only records excluded.
Portable numerical relativity
143 checks. Minkowski, gauge-wave and link studies plus independent portable-solver verification.
Orbit and clock comparisons
63 checks. 37 orbit checks and 26 published clock checks.
Qiskit phase-correlation study
210 checks. The existing website study, retained once.
These groups reconcile to the 6,823-check total. Floquet demonstration runs and other records with different counting units remain separate. This is a reproducible count of retained declared evidence, not every exploratory calculation ever performed.
Acceptance evidence remains tied to its original source and workload. The autonomous and maintenance releases did not rerun the full scientific benchmark campaign. Website checks remain separate from the application totals. Native Windows, representative researcher usability, applicable production/BYOS deployment and live-model scientific accuracy remain separate qualification gates.