The Missing Middleware for Physics AI

CAE evidence for humans and agents.

CaeReflex inspects solver folders, mesh files, VTK outputs, scripts, notes, and DOI metadata, then exports a provenance-aware ReflexCase record.

Read-only inspection
OpenFOAM-like, Gmsh, VTK, notes, scripts.
Agent-ready outputs
JSON, compact context, reports, REST/OpenAPI.
Clear boundaries
Evidence aid, not simulation validation.

Start locally Agent guide Schema

Fragmented evidence becomes one record.

Normalize the engineering file trail before it reaches notebooks, reports, APIs, or LLM tools.

Problem

Scattered artefacts

Geometry, dictionaries, outputs, scripts, notes, and DOI metadata often live apart.

Risk

Partial context

Agents can overstate results when they only see a hand-written summary.

Answer

ReflexCase JSON

A compact, provenance-aware record with warnings and exportable context.

Evidence-flow model.

Raw CAE artefacts are inspected first, then summarized with explicit provenance.

Input

CAE files

Solver folders, meshes, results, scripts, notes.

Inspect

Adapters

Fingerprint formats without running solvers.

Normalize

ReflexCase

Separate files, facts, inferences, flags.

Export

Outputs

JSON, reports, context, REST actions.

Review

Human + LLM

Summaries stay tied to evidence.

Trust boundary.

CaeReflex documents inspected evidence; qualified engineers still validate physics and decisions.

CaeReflex is

read-only inspection;
provenance-aware case records;
LLM-readable context;
local tool workflow support.

CaeReflex is not

a solver runner;
a validation system;
a convergence proof;
a design approval authority.

Built for technical reviewers.

Same record, different workflow entry points.

Agent engineers

Use REST/OpenAPI actions for structured local context.

Simulation engineers

Inspect common CAE folders without mutation.

Data scientists

Export reproducible JSON, reports, flags, and metadata.

Why it is different.

Engineering provenance stays visible instead of being flattened into generic text.

Read-only CAE inspection

Adapters inspect supported artefacts without solver execution.

Provenance records

Source files, detected facts, inferred context, and warnings remain separate.

Agent-native outputs

Export JSON, context, reports, BibTeX, and REST/OpenAPI actions.

Consolidate proof points.

Gmsh

Inspect `.geo` and fingerprint `.msh` workflows.

OpenFOAM

Read case folders and expected dictionaries.

VTK / ParaView

Inspect legacy `.vtk` and VTK-family artefacts.

CrossRef

Attach DOI metadata as explicit research context.

Quickstart now.

Run locally from the CLI, expose REST/OpenAPI, or connect an agent workflow.

CLI

Inspect and export

pip install -e ".[server]"
caereflex inspect examples/openfoam_cavity_minimal \
  --out caereflex.json \
  --agent-context agent_context.json \
  --report case_report.md

CLI docs

REST

Serve local actions

caereflex serve \
  --host 127.0.0.1 \
  --port 8765
open http://127.0.0.1:8765/openapi.yaml

REST docs

Agent

Import, context, flags

GET  /health
POST /cases/import
GET  /cases/{case_id}/agent-context
GET  /cases/{case_id}/inspection-flags

Agent guide

REST/OpenAPI workflow.

Import cases, retrieve context, inspect flags, and export reports.

GET  /health
GET  /openapi.yaml
POST /cases/import
GET  /cases/{case_id}/agent-context
GET  /cases/{case_id}/inspection-flags
POST /cases/{case_id}/crossref/attach