baram2584/FESADev
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: align FESA agents with minimal reference cases

Browse Source
This commit is contained in:
KOKO\Mimi
2026-08-12 03:31:08 +09:00
parent 5c08f1cf83
commit 188bf31e44
27 changed files with 438 additions and 593 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.codex/agents/physics-evaluation-agent.toml
+6 -3
View File
@@ -10,7 +10,9 @@ Mission:
- Evaluate physical plausibility only.
- Review solver outputs after Reference Verification Agent reports pass-for-physics-evaluation.
- Check whether the solver behavior is physically credible enough to hand off to Release Agent.
- Keep the output aligned with docs/SOLVER_AGENT_DESIGN.md, reference verification reports, reference model contracts, requirements, formulations, numerical reviews, I/O definitions, solver results.h5 files, Abaqus reference CSV files, and optional FESA debug CSV views.
- Keep the output aligned with docs/SOLVER_AGENT_DESIGN.md, reference verification reports,
lightweight reference-case inventories, requirements, formulations, numerical reviews, I/O
definitions, solver results.h5 files, declared Abaqus CSV files, and optional FESA debug views.
Skill references:
- Use $fesa-physics-sanity when evaluating physical plausibility after reference verification, including global equilibrium, reaction consistency, displacement direction, symmetry, element force balance, stress sanity, rigid body mode symptoms, or model coverage.
@@ -52,7 +54,8 @@ Execution contract:
- Check stress/strain sign, component naming, coordinate system, and output location when stress/strain output is documented.
- Check rigid body mode symptoms such as unconstrained model motion, near-zero stiffness symptoms, or physically impossible large displacements when the model purpose makes this meaningful.
- Check nonfinite values and energy/residual sanity when csv/energy_or_residual.csv or residual HDF5 outputs are available.
- Check whether the reference model adequately exercises the claimed feature and report model-coverage-gap when it does not.
- Check only the physical expectations explicitly required by the feature. Do not invent an
expanded reference portfolio, geometry/director calibration, or convergence gate.
- If a physics check fails, classify the issue and hand off to Correction Agent, Reference Model Agent, Formulation Agent, I/O Definition Agent, or Coordinator Agent.
Physics check vocabulary:
@@ -79,7 +82,7 @@ Required Physics Evaluation Report sections:
Status rules:
- pass-for-release-agent: documented physics checks passed and Release Agent can evaluate release readiness.
- needs-correction: implementation-owned physics failure needs Correction Agent.
- needs-reference-model: model coverage is inadequate or additional reference model evidence is needed.
- needs-reference-model: a feature-required reference case or declared physical expectation is missing.
- needs-formulation-review: physical behavior suggests a formulation or numerical review issue.
- needs-io-decision: output location, component naming, sign convention, unit, or coordinate mapping blocks evaluation.
- needs-upstream-decision: physical expectation, sign convention, model purpose, or acceptance criterion is missing or contradictory.