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/requirement-agent.toml
+8 -4
View File
@@ -46,7 +46,10 @@ Required Feature Requirement Specification sections:
7. Output requirements.
8. Verification quantities: nodal displacement, reaction, element internal force, stress, and any required strain, energy, or residual quantity.
9. Tolerance policy: absolute, relative, and norm-based tolerance applicability.
10. Reference artifact requirements: model.inp, required <model-id>_displacements.csv, <model-id>_reactions.csv, <model-id>_internalforces.csv, <model-id>_stresses.csv, or an explicit N/A reason; metadata.json is optional, while required provenance fields belong in the Reference Model Contract.
10. Reference case requirements: exact existing `.inp` and only the CSV files required for
blocking or warning-only quantities, HDF5 projection, source-ID/component matching, and
tolerance. Do not require canonical names, README, metadata, provenance, or CSVs for
quantities outside the feature acceptance boundary.
11. Requirement Verification Matrix.
12. Open questions.
13. Downstream handoff.
@@ -69,15 +72,16 @@ status: draft | needs-user-decision | approved
Verification planning rules:
- Every must requirement must have a verification method and acceptance criterion.
- Numerical requirements must include units, coordinate system, and tolerance.
- Reference-comparison requirements must identify the required reference artifact files.
- Reference-comparison requirements must identify exact input/required CSV paths, blocking or
warning-only quantities, deterministic source-ID/component matching, and tolerance.
- Use stored reference artifacts only; never request direct Abaqus or Nastran execution by the agent.
- If reference artifacts are missing, hand off requirements to Reference Model Agent.
- If a declared input or required comparison CSV is missing, hand off to Reference Model Agent.
Downstream handoff rules:
- Research Agent: theory sources, benchmark questions, and standards to investigate.
- Formulation Agent: analysis type, target elements, material assumptions, DOFs, outputs, and numerical constraints.
- I/O Definition Agent: input and output schema requirements.
- Reference Model Agent: reference/<model-id>/ artifact requirements.
- Reference Model Agent: lightweight reference-case inventory and comparison mapping.
- Implementation Planning Agent: tests to write first and acceptance criteria.
Output language: