SCHEMAXIS PILOT · Declared work. Results you can check.Documentation ↗ · Contact
schemaxis/Agent’s Hands

AI authors the files. Schemaxis handles the work.

Workflow files in.
Checked work out.

No remote code execution by the AI. Just declared input files.

The AI creates a workflow template and a parameter file, then hands the declared job to Schemaxis. Schemaxis checks the plan, coordinates the supported applications and keeps results with their evidence.

In the strict interface, the AI supplies declared inputs, not arbitrary scripts or shell commands. Native applications run through the configured Schemaxis runtime.

See the files flow ↓See smaller models pass every check ↓
01 · Files in, no shellThe agent declares the job. 02 · Smaller models, bigger workFrom failed checks to 110/110. 03 · Inspect it. Keep the receipt.Read the plan before running. 04 · Expertise you can reuseReviewed workflows for junior staff.
DrivAer body with saved steady-field streamlines coloured by speed
Existing saved-result illustration. Schemaxis drove ParaView; HELYX ran the solver independently. Coarse, unconverged and unvalidated. This render is not hosted container-isolation evidence.
DeclareSource or generation → operations → outputs
CaptureImmutable inputs and their digests
CheckAdmission → schema → scope → budget reservation
ExecuteSealed qualified worker → output digests and receipts
InspectBounded observations and receipt content

02 / Smaller models. Complex application work.

Small models.
A Schemaxis super suit.

Same models. Same ParaView task. All 110 checks passed with Schemaxis. Without it, none of these three models passed every required check. Schemaxis supplies the application contracts, workflow structure and result checks that help turn their intent into passing work.

29 September 2026 · ParaView authoring · checks passed
Model versionWithout SchemaxisChecks passed · incompleteWith SchemaxisChecks passed · all required checks
Haiku 4.522 / 110Incomplete110 / 110✓ All checks passed
Sonnet 4.622 / 110Incomplete110 / 110✓ All checks passed
GPT-5.6 Luna68 / 110Incomplete110 / 110✓ All checks passed

One conversation per model and method on a bounded ParaView task; 110 checks, not 110 independent tasks. Historical versions and results, not a general success guarantee.

Study scope, historical interface and reporting limits

Haiku 4.5’s native initial output had 32/32 images rejected, while its retained transcript called the result “production-ready”. The Schemaxis artifacts passed the required checks. The core supplies the verification state and receipt instead of relying on the agent’s success sentence. This records a misleading claim and changed artifact outcomes; it does not measure a general reduction in false-reporting propensity.

29 September 2026: one authoring conversation per model and method, older model versions, 110 checks across an initial task and revision on small, purpose-built serial ParaView fixtures. Checks are not independent tasks.

Some historical Schemaxis runs inspected implementation details or used helper code; one revision wrapper was broken despite passing artifacts. These are artifact outcomes, not qualification of the new strict no-shell authoring interface. The Opus native control was excluded after provider substitution.

Frontier-model tradeoff: frontier models passed either way in the retained paired studies, and Schemaxis was slower. The advantage shown here is enabling the smaller models.

Inspect the study data and before/after images ↗

01 / No remote code execution by the AI

Follow the files.
Change parameters for the next job.

The template holds the operations, limits and checks. The parameter file supplies the values that vary. Together they define a job for Schemaxis. Click either file to inspect it, or change c and watch the parameter file update.

Follow the filesAI supplies files · Schemaxis coordinates the applications
AI authors files → Schemaxis coordinates the work. No remote code execution performed by the AI.
x² − 2
SchemaxisBind parameters
Check the plan
Coordinate authorised work
SymPyNative application
Root isolation

Data flow: the parameter values supply the polynomial in this example. For file-based jobs, Schemaxis captures authorised source data and passes it to the declared app operations.

sqrt2-values.jsonRetained file · read onlyDownload file ↗
Enable JavaScript to switch between files. Exact sources are linked below.

Recorded binding and planning only; application launches: 0.

What is real here, and what happens after the preview?

The exact template bundle contains template.json and its referenced workflow.json recipe. The separate parameter file selects one job. An AI can create the bundle and values; later operators reuse the bundle and change only the values. The graph groups the manifest and recipe as “Workflow Template”.

Core 68e139a bound and planned c = −2 and c = −3 without launching SymPy. The page only switches retained files or generates a local file preview. It does not contact Schemaxis, submit files, run applications, verify new results or create receipts. Execution and fresh result checks happen separately in a supported environment.

The file-template example is the self-operated core contract. The hosted strict interface has its own admission contract. This single-app example does not qualify arbitrary multi-app pipelines or a hosted template-upload endpoint.

Exact template manifest ↗ · Exact recipe ↗ · Full workflow reference ↗

03 / Inspect before execution. Verify after it.

Inspect without the apps.
Run it. Get a receipt.

Admission, the declared schema, task scope and budget reservation are checked before execution. A request outside its authority is refused before a native job can run. Planning and inspection can run without launching the applications; native result verification is a separate step that reports the checks actually performed.

BEFORE EXECUTION

Read the work before it runs.

Inspect the workflow files, resolve inputs and check the plan without launching the native applications.

AFTER EXECUTION

The result comes with evidence.

Keep the inputs, outputs, logs, digests and verification receipt. Inspect what ran, which checks passed and which limits remain.

AdmissionSchemaScopeBudget reservation

NumPy request. SymPy-only scope.

In the retained MCP demonstration, a NumPy request under a SymPy-only scope returned SCOPE_EXCEEDED. Calls stopped at planning: zero native execution, all four prior NumPy output digests unchanged, and no successful current invocation to claim.

Inspect the retained refusal facts ↗
allowed providers: ["sympy"]
requested provider: "numpy"
fault: SCOPE_EXCEEDED
native executions: 0
previous output digests: 4 / 4 unchanged
current invocation check: not passed

Historical prepared-recipe local MCP demonstration, core 5cfe1b0. It is separate from both the comparative study and the hosted container-isolation proof.

04 / One reviewed workflow. A family of repeatable jobs.

Build the expertise into the workflow.
Let junior staff run the next job.

Once an AI or expert creates and reviews the template and its parameter format, changing permitted values creates another job in the same workflow family. Operators can follow the reviewed process without reconstructing its application logic.

A junior operator supplies the job’s inputs and parameters; the template carries the sequence, limits and checks. This is how one template can cover a broad set of recurring jobs within its declared scope.

Reliable reuse depends on the reviewed template, its checks, authorised inputs and compatible runtimes. The retained example demonstrates binding and planning; junior-staff performance has not been measured.

Inspect the reusable workflow and parameter files ↗
HOSTED CANDIDATE.
FIVE EXPLICIT SCOPES.ParaViewSymPyExifToolNumPyFFmpeg

First example · ParaView from saved results

Industrial geometry.
Inspectable post-processing.

Existing DrivAer and pitzDaily views, rendered by Schemaxis driving ParaView 5.13.3. Native HELYX 4.6.0 ran the simulations independently. These are saved-result illustrations, not hosted solver capabilities.

Start from the selected saved case.

The data owner supplies saved fields and a declared ParaView recipe. Inspect supported operations and the plan before rendering. This preview uses already recorded views; it does not upload geometry, create a plan for a new CFD case or run a solver.

DrivAer body with steady-field streamlines coloured by speed

DrivAer · streamlines coloured by speed

Saved HELYX result at 20 m/s; ParaView post-processing by Schemaxis. Steady-field curves, not particle paths. Coarse mesh, no boundary layers; residual targets were not met. Illustrative, not a validated aerodynamic prediction.

Expanded selected saved result

Existing saved result · not a new simulation

Rendered 23 October 2026. DrivAer: 92,316 cells, no boundary layers, 500 iterations without meeting residual targets. The full case and private input documents are not distributed. These renders do not validate flow physics or establish hosted admission for an industrial case.

Inspect curated image hashes and provenance ↗

Local saved-results example · ParaView

A declared slice.
An inspectable image.

The agent declares the saved-results reader, centreline slice, pressure field, style and image output. Schemaxis runs ParaView and retains the artifact and receipt.

UNRESOLVED diagnosticJob 5919 · steady iteration 3847, not seconds

Unresolved job 5919 at steady iteration 3847: centreline fluid pressure around the baseline DrivAer silhouette, coloured by p in Pa, minus 300 to plus 300. The native unresolved banner and legend are retained.
Centreline pressure · p [Pa] · −300…300 Pa. Lower pressure exists elsewhere in the whole volume outside this view. Cell values are shown without cell-to-point smoothing. The white vehicle silhouette contains no fluid cells.
Open original PNG ↗

Saved-results illustration only. Numerical status remains unresolved; this is not an accepted aerodynamic or geometry comparison, validation or optimisation result. This local ParaView example is outside the hosted 512 KiB pilot; CFD solver and setup work are not a service offered here.

Inspect the saved-result limits and artifact receipt

Saved iteration3847 from a steady incompressible kOmegaSST DrivAer baseline. Native numerical status UNRESOLVED: Uy residual and lift-stationarity limits missed. Iteration is not seconds. p is physical static gauge pressure in Pa; outlet reference0, no density conversion. The solid vehicle has no fluid cells in the slice. This single-mesh illustration is not an accepted aerodynamic comparison, validation, grid-independence result or geometry-optimisation evidence. No spoiler or pylons. Cell slice values are displayed without cell-to-point smoothing. Presentation r2 uses−300…300Pa over the complete displayed centreline slice; lower pressure exists elsewhere in the whole volume outside this view. Full-volume and displayed-slice ranges are retained separately. Tighter camera/window and banner revise presentation only, after the preserved r1 visual rejection; no favourable scientific-result selection or validation claim.

Native rendering and the fresh artifact check passed. Those checks establish the retained image and declared rendering; they do not accept the CFD solution. The runtime self-reported ParaView 5.13.3; this local observation does not qualify the hosted pilot or other runtimes.

PNG SHA-256: ac6576508325bc9a66f38145db0bad8b9b9a5e5c946e82b2041b86ca27b6b101

Inspect the safe artifact record ↗
UNRESOLVED diagnostic · job 5919

Steady iteration 3847 · p [Pa] · −300…300 Pa

Expanded unchanged native diagnostic centreline pressure image, with unresolved job 5919 iteration 3847 banner and p in Pa legend

Lower whole-volume pressure exists outside this displayed centreline view. No cell-to-point smoothing. Saved-results illustration; no scientific, geometry-comparison or validation acceptance. Local ParaView example, outside the hosted 512 KiB pilot; no CFD solver/setup service.

Open original PNG ↗

Declared inputs · separate from saved flow results

One body. Four geometric declarations.
Front and rear perspectives.

Eight genuine native previews: baseline without a spoiler, then 100, 200 and 300 mm plate chords, each viewed from common front/rear orthographic cameras. These images show geometry inputs, not a CFD study.

GEOMETRY ONLY · NO ACCEPTED CFD RESULTS

Genuine DrivAer body and wheels with constructed orange plate/pylons where enabled; not AI-generated pictures. Baseline has no plate or pylons, and its chord/span are not applicable.

There is no accepted new fluid mesh, flow field, force result, simulation-variant run or geometry-variation scientific graph here. The existing saved-flow gallery above keeps its original coarse/unconverged labels. This does not add a hosted CFD solver or change the hosted input limit.

Geometry is in metres with identity transform. Float32 STL is a display approximation: original topology warnings are retained, and no repair, union, watertightness or topology qualification is inferred. No mesher may use these preview STLs. Only the approved PNGs are available here.

DECLARED INPUT GEOMETRY · GEOMETRY ONLY

Baseline · no spoiler · front quarter

Geometry only — not a fluid mesh, CFD field, force result or accepted simulation/variant run.

includeSpoiler
false · no plate or pylons
Plate chord
N/A
Plate span
N/A
Nominal plate planform
N/A · no plate

Planform = span × chord, excluding pylons; not wetted, exposed or total-device surface area.

Native-render provenance and limits

GEOMETRY_ONLY_NOT_SIMULATION_RESULTS. No spoiler: no plate and no pylons; chord/span not applicable. Genuine DrivAer body/wheels in metres, identity transform. Grey body, dark wheels; when enabled, orange plate/pylons. Common orthographic cameras. Float32 STL is a display approximation; no repair/union/topology qualification. Original body/wheel topology warnings retained. This is declared input geometry, not a fluid mesh, CFD field, force result or accepted simulation; no mesher may use these preview STLs.

Native render of genuine DrivAer body/wheels and constructed appendages; not AI-generated.

be583062fd2860d4a4a53af851e73fe7e0cb792c4f2f02e22291b199fc0c0ea5

Download original PNG ↗

DECLARED INPUT GEOMETRY · GEOMETRY ONLY

Baseline · no spoiler · rear quarter

Geometry only — not a fluid mesh, CFD field, force result or accepted simulation/variant run.

includeSpoiler
false · no plate or pylons
Plate chord
N/A
Plate span
N/A
Nominal plate planform
N/A · no plate

Planform = span × chord, excluding pylons; not wetted, exposed or total-device surface area.

Native-render provenance and limits

GEOMETRY_ONLY_NOT_SIMULATION_RESULTS. No spoiler: no plate and no pylons; chord/span not applicable. Genuine DrivAer body/wheels in metres, identity transform. Grey body, dark wheels; when enabled, orange plate/pylons. Common orthographic cameras. Float32 STL is a display approximation; no repair/union/topology qualification. Original body/wheel topology warnings retained. This is declared input geometry, not a fluid mesh, CFD field, force result or accepted simulation; no mesher may use these preview STLs.

Native render of genuine DrivAer body/wheels and constructed appendages; not AI-generated.

4d7abd5b0ed94a0832728a04e55d13c5ad81a558c831454c32672819e9e3c139

Download original PNG ↗

DECLARED INPUT GEOMETRY · GEOMETRY ONLY

Spoiler · 100 mm chord · front quarter

Geometry only — not a fluid mesh, CFD field, force result or accepted simulation/variant run.

includeSpoiler
true · plate and pylons
Plate chord
100 mm
Plate span
1.2 m
Nominal plate planform
0.12 m²

Planform = span × chord, excluding pylons; not wetted, exposed or total-device surface area.

Native-render provenance and limits

GEOMETRY_ONLY_NOT_SIMULATION_RESULTS. Plate chord 100 mm, span1.2 m; nominal plate PLANFORM area 0.12 m² (span×chord), excluding pylons, not wetted/exposed or total-device area. Genuine DrivAer body/wheels in metres, identity transform. Grey body, dark wheels; when enabled, orange plate/pylons. Common orthographic cameras. Float32 STL is a display approximation; no repair/union/topology qualification. Original body/wheel topology warnings retained. This is declared input geometry, not a fluid mesh, CFD field, force result or accepted simulation; no mesher may use these preview STLs.

Native render of genuine DrivAer body/wheels and constructed appendages; not AI-generated.

cf74025fc0bd3a207e4f37dc811afe789453d23d2cdd7af82019357f82434d10

Download original PNG ↗

DECLARED INPUT GEOMETRY · GEOMETRY ONLY

Spoiler · 100 mm chord · rear quarter

Geometry only — not a fluid mesh, CFD field, force result or accepted simulation/variant run.

includeSpoiler
true · plate and pylons
Plate chord
100 mm
Plate span
1.2 m
Nominal plate planform
0.12 m²

Planform = span × chord, excluding pylons; not wetted, exposed or total-device surface area.

Native-render provenance and limits

GEOMETRY_ONLY_NOT_SIMULATION_RESULTS. Plate chord 100 mm, span1.2 m; nominal plate PLANFORM area 0.12 m² (span×chord), excluding pylons, not wetted/exposed or total-device area. Genuine DrivAer body/wheels in metres, identity transform. Grey body, dark wheels; when enabled, orange plate/pylons. Common orthographic cameras. Float32 STL is a display approximation; no repair/union/topology qualification. Original body/wheel topology warnings retained. This is declared input geometry, not a fluid mesh, CFD field, force result or accepted simulation; no mesher may use these preview STLs.

Native render of genuine DrivAer body/wheels and constructed appendages; not AI-generated.

7995cb1ce4446bb2683d4aec0b5450b57c9595212efa908fe62417bac74e91e7

Download original PNG ↗

DECLARED INPUT GEOMETRY · GEOMETRY ONLY

Spoiler · 200 mm chord · front quarter

Geometry only — not a fluid mesh, CFD field, force result or accepted simulation/variant run.

includeSpoiler
true · plate and pylons
Plate chord
200 mm
Plate span
1.2 m
Nominal plate planform
0.24 m²

Planform = span × chord, excluding pylons; not wetted, exposed or total-device surface area.

Native-render provenance and limits

GEOMETRY_ONLY_NOT_SIMULATION_RESULTS. Plate chord 200 mm, span1.2 m; nominal plate PLANFORM area 0.24 m² (span×chord), excluding pylons, not wetted/exposed or total-device area. Genuine DrivAer body/wheels in metres, identity transform. Grey body, dark wheels; when enabled, orange plate/pylons. Common orthographic cameras. Float32 STL is a display approximation; no repair/union/topology qualification. Original body/wheel topology warnings retained. This is declared input geometry, not a fluid mesh, CFD field, force result or accepted simulation; no mesher may use these preview STLs.

Native render of genuine DrivAer body/wheels and constructed appendages; not AI-generated.

985912e76ad3127964757771656f838fbfadf6dff16fec59d79307613c949d7a

Download original PNG ↗

DECLARED INPUT GEOMETRY · GEOMETRY ONLY

Spoiler · 200 mm chord · rear quarter

Geometry only — not a fluid mesh, CFD field, force result or accepted simulation/variant run.

includeSpoiler
true · plate and pylons
Plate chord
200 mm
Plate span
1.2 m
Nominal plate planform
0.24 m²

Planform = span × chord, excluding pylons; not wetted, exposed or total-device surface area.

Native-render provenance and limits

GEOMETRY_ONLY_NOT_SIMULATION_RESULTS. Plate chord 200 mm, span1.2 m; nominal plate PLANFORM area 0.24 m² (span×chord), excluding pylons, not wetted/exposed or total-device area. Genuine DrivAer body/wheels in metres, identity transform. Grey body, dark wheels; when enabled, orange plate/pylons. Common orthographic cameras. Float32 STL is a display approximation; no repair/union/topology qualification. Original body/wheel topology warnings retained. This is declared input geometry, not a fluid mesh, CFD field, force result or accepted simulation; no mesher may use these preview STLs.

Native render of genuine DrivAer body/wheels and constructed appendages; not AI-generated.

f979eb76029e2d5d201104008ccac92ee1b8962b3c5d962334c9d2aaa6c32a35

Download original PNG ↗

DECLARED INPUT GEOMETRY · GEOMETRY ONLY

Spoiler · 300 mm chord · front quarter

Geometry only — not a fluid mesh, CFD field, force result or accepted simulation/variant run.

includeSpoiler
true · plate and pylons
Plate chord
300 mm
Plate span
1.2 m
Nominal plate planform
0.36 m²

Planform = span × chord, excluding pylons; not wetted, exposed or total-device surface area.

Native-render provenance and limits

GEOMETRY_ONLY_NOT_SIMULATION_RESULTS. Plate chord 300 mm, span1.2 m; nominal plate PLANFORM area 0.36 m² (span×chord), excluding pylons, not wetted/exposed or total-device area. Genuine DrivAer body/wheels in metres, identity transform. Grey body, dark wheels; when enabled, orange plate/pylons. Common orthographic cameras. Float32 STL is a display approximation; no repair/union/topology qualification. Original body/wheel topology warnings retained. This is declared input geometry, not a fluid mesh, CFD field, force result or accepted simulation; no mesher may use these preview STLs.

Native render of genuine DrivAer body/wheels and constructed appendages; not AI-generated.

938ad6a955351d9dc9bf674bb482dd6e54642f805fca9ec9aa62c138287332f2

Download original PNG ↗

DECLARED INPUT GEOMETRY · GEOMETRY ONLY

Spoiler · 300 mm chord · rear quarter

Geometry only — not a fluid mesh, CFD field, force result or accepted simulation/variant run.

includeSpoiler
true · plate and pylons
Plate chord
300 mm
Plate span
1.2 m
Nominal plate planform
0.36 m²

Planform = span × chord, excluding pylons; not wetted, exposed or total-device surface area.

Native-render provenance and limits

GEOMETRY_ONLY_NOT_SIMULATION_RESULTS. Plate chord 300 mm, span1.2 m; nominal plate PLANFORM area 0.36 m² (span×chord), excluding pylons, not wetted/exposed or total-device area. Genuine DrivAer body/wheels in metres, identity transform. Grey body, dark wheels; when enabled, orange plate/pylons. Common orthographic cameras. Float32 STL is a display approximation; no repair/union/topology qualification. Original body/wheel topology warnings retained. This is declared input geometry, not a fluid mesh, CFD field, force result or accepted simulation; no mesher may use these preview STLs.

Native render of genuine DrivAer body/wheels and constructed appendages; not AI-generated.

f0a5255082568132acd7b676633044b3f973f78085be918137679a9288c9e165

Download original PNG ↗

Inspect geometry parameters, PNG hashes and scope ↗

DECLARED INPUT GEOMETRY · GEOMETRY ONLY

Declared geometry input

Declared geometry input — not a simulation result

Geometry only — not a fluid mesh, CFD field, force result or accepted simulation/variant run.

Second example · SymPy

Exact roots.
A repeatable recipe.

The same declared root-isolation workflow can be bound to new exact-rational coefficients. The picture is a mathematical illustration; the file explorer above includes real host-preflight records, not a new native run.

Graph of x squared minus two with roots labelled minus and plus square root of two
Mathematical illustration of x² − 2. Decimal labels are explanatory; the declared SymPy route returns exact rational isolating intervals, with an independent certificate.

01 / Plan · illustrative

Agree the work before it runs.

Discover the admitted operation, declare inputs and bounds, then inspect the plan and its revision. A valid plan is permission to attempt that declared work.

provider: sympy
operation: isolateRealRoots
polynomial: x² − 2
inputs: exact rational coefficients

Inspect the inputs before any app runs.

The interactive file viewer above includes the exact template, recipe, parameter files and two recorded host plans. Both cases were bound and planned without launching SymPy.

Return to the workflow files ↑ Open the full reference ↗

Choose how you operate it

The workflow is reusable.
Hosting is optional.

A saved recipe and ongoing provider-operated access are different things. Neither a GUI paywall nor a database subscription is being introduced here.

Free core + Studio

Planned Apache-2.0 distribution includes declared workflow tooling, Studio, parameter forms, local execution and evidence. Operate it on your own machines with suitable application runtimes.

Read the current boundary ↗

Reusable workflow family

One reviewed declaration plus bounded parameters can describe a family of repeated jobs. A maintained commercial workflow pack is a proposal, not an included template library or adopted subscription.

Inspect a real example ↗

Optional managed operation

The provider operates the supported runtime during agreed access. The earlier C$400 / 14-day proposal is under review; there is no final price, current hosted access or established buyer value.

Compare self-operation and hosting ↗