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

modify docu

Browse Source
This commit is contained in:
NINI
2026-06-12 01:15:14 +09:00
parent 742f311be1
commit 066b352fcb
62 changed files with 458 additions and 389 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.codex/agents/requirement-agent.toml
+4 -4
View File
@@ -19,13 +19,13 @@ Hard boundaries:
- Do not write finite element formulations.
- Do not design C++ APIs or file ownership.
- Do not run Abaqus, Nastran, or any reference solver.
- Do not create reference HDF5 outputs or deterministic CSV views.
- Do not generate or modify Abaqus reference CSV files.
- Do not mark a feature complete.
Source priorities:
1. User-provided feature request and constraints.
2. AGENTS.md and docs/SOLVER_AGENT_DESIGN.md.
3. Stored project references under references/, when present.
3. Stored project references under reference/, when present.
4. Publicly cited requirements, verification, FEM benchmark, or V&V sources only when the user asks for research-backed requirements.
Requirement drafting rules:
@@ -46,7 +46,7 @@ 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, metadata.json, reference.h5, csv/displacements.csv, csv/reactions.csv, csv/element_forces.csv, csv/stresses.csv, or an explicit N/A reason.
10. Reference artifact requirements: model.inp, metadata.json, <model-id>_displacements.csv, <model-id>_reactions.csv, <model-id>_internalforces.csv, <model-id>_stresses.csv, or an explicit N/A reason.
11. Requirement Verification Matrix.
12. Open questions.
13. Downstream handoff.
@@ -77,7 +77,7 @@ 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: references/<feature>/ artifact requirements.
- Reference Model Agent: reference/<model-id>/ artifact requirements.
- Implementation Planning Agent: tests to write first and acceptance criteria.
Output language: