김경종
69 lines
2.9 KiB
Markdown
69 lines
2.9 KiB
Markdown
---
|
|
name: fesa-physics-sanity
|
|
description: Use when evaluating FESA solver physics and physical plausibility after reference verification, including equilibrium, reactions, displacement direction, symmetry, stress sanity, and model coverage.
|
|
---
|
|
|
|
# FESA Physics Sanity
|
|
|
|
Use this skill to determine whether reference-passing solver outputs are physically credible enough for release evaluation.
|
|
|
|
## Inputs
|
|
|
|
Read these first:
|
|
|
|
- `AGENTS.md`
|
|
- `docs/AGENT_RULES.md`
|
|
- `docs/physics-evaluations/README.md`
|
|
- Reference Verification report with `pass-for-physics-evaluation`
|
|
- `docs/reference-models/<feature-id>-reference-models.md`
|
|
- Requirements, formulation, numerical review, and I/O definition documents
|
|
- Stored solver/reference HDF5 files and approved optional CSV extracts as read-only evidence
|
|
|
|
## Workflow
|
|
|
|
1. Evaluate only documented physical expectations.
|
|
2. Require a reference verification status of `pass-for-physics-evaluation`.
|
|
3. Check global equilibrium when loads, reactions, and sign conventions are documented.
|
|
4. Check reaction consistency for constrained DOFs.
|
|
5. Check displacement direction against loads, boundary conditions, and expected deformation mode.
|
|
6. Check symmetry or expected zero conditions when the model defines them.
|
|
7. Check element force balance and element internal force sign conventions when documented.
|
|
8. Check stress/strain component naming, coordinate system, output location, and sign.
|
|
9. Check rigid body mode symptoms, nonfinite values, energy/residual evidence, and model coverage.
|
|
10. Classify failures and route them to the owning agent.
|
|
|
|
## Output Contract
|
|
|
|
Produce or revise `docs/physics-evaluations/<feature-id>-physics-evaluation.md` with:
|
|
|
|
- Metadata
|
|
- Input Evidence
|
|
- Physics Checks
|
|
- Failure Classification
|
|
- Evaluation Verdict
|
|
- Handoff Recommendation
|
|
- No-Change Assertion
|
|
- Open Issues
|
|
|
|
## Boundaries
|
|
|
|
- Do not edit source code.
|
|
- Do not edit tests.
|
|
- Do not edit CMake files.
|
|
- Do not edit requirements, formulations, I/O contracts, reference model contracts, reference artifacts, or tolerance policies.
|
|
- Do not run Abaqus, Nastran, or any reference solver.
|
|
- Do not generate reference HDF5 artifacts or reference CSVs.
|
|
- Do not approve release readiness.
|
|
- Do not approve reference tolerance success.
|
|
|
|
## Quality Gate
|
|
|
|
- A physics pass requires documented expectations and reference verification pass evidence.
|
|
- Use `needs-upstream-decision` when physical expectations, sign convention, or model purpose is missing.
|
|
- Use `needs-reference-model` when the model does not cover the claimed feature.
|
|
- `pass-for-release-agent` means Release Agent can audit release readiness; it is not release approval.
|
|
|
|
## Handoff
|
|
|
|
Send `pass-for-release-agent` reports to Release Agent. Send implementation-owned physics failures to Correction Agent, formulation concerns to Formulation Agent, I/O ambiguity to I/O Definition Agent, and model coverage gaps to Reference Model Agent.
|