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

revert

Browse Source
This commit is contained in:
김경종
2026-06-10 10:03:11 +09:00
parent 87529c811a
commit 0912ee6f3b
174 changed files with 414 additions and 8544 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.codex/skills/fesa-cpp-msvc-tdd/SKILL.md
+2 -2
View File
@@ -12,7 +12,7 @@ Use this skill to keep FESA C++ implementation work test-first, MSVC-compatible,
Read these first:
- `AGENTS.md`
- `docs/AGENT_RULES.md`
- `docs/SOLVER_AGENT_DESIGN.md`
- `docs/implementation-plans/README.md`
- `docs/build-test-reports/README.md`
- `docs/corrections/README.md`
@@ -65,7 +65,7 @@ ctest --test-dir build/msvc-debug --output-on-failure -C Debug
- Do not change reference artifacts.
- Do not change tolerance policies.
- Do not run Abaqus, Nastran, or any reference solver.
- Do not generate reference HDF5 artifacts or reference CSVs.
- Do not generate reference CSVs.
- Do not approve release readiness.
## Quality Gate
.codex/skills/fesa-formulation-spec/SKILL.md
+2 -2
View File
@@ -12,7 +12,7 @@ Use this skill to turn approved requirements and research evidence into an imple
Read these first:
- `AGENTS.md`
- `docs/AGENT_RULES.md`
- `docs/SOLVER_AGENT_DESIGN.md`
- `docs/formulations/README.md`
- `docs/requirements/<feature-id>.md`
- `docs/research/<feature-id>-research.md`
@@ -54,7 +54,7 @@ Produce or revise `docs/formulations/<feature-id>-formulation.md` with:
- Do not design C++ APIs.
- Do not implement parsers.
- Do not run Abaqus, Nastran, or any reference solver.
- Do not generate reference HDF5 artifacts or reference CSVs.
- Do not generate reference CSVs.
- Do not approve release readiness.
## Quality Gate
.codex/skills/fesa-io-contract/SKILL.md
+9 -12
View File
@@ -1,6 +1,6 @@
---
name: fesa-io-contract
description: Use when defining FESA solver I/O contracts, Abaqus .inp keyword subsets, internal model mapping, validation rules, HDF5 result/reference schemas, and optional CSV export schemas for solver outputs or reference comparison.
description: Use when defining FESA solver I/O contracts, Abaqus .inp keyword subsets, internal model mapping, validation rules, and CSV schemas for solver outputs or reference comparison.
---
# FESA I/O Contract
@@ -12,7 +12,7 @@ Use this skill to define exactly what input and output data the solver feature a
Read these first:
- `AGENTS.md`
- `docs/AGENT_RULES.md`
- `docs/SOLVER_AGENT_DESIGN.md`
- `docs/io-definitions/README.md`
- `docs/requirements/<feature-id>.md`
- `docs/formulations/<feature-id>-formulation.md`
@@ -25,10 +25,9 @@ Read these first:
3. Separate Model Data Mapping from History Data Mapping.
4. Define supported keywords such as `*NODE`, `*ELEMENT`, `*MATERIAL`, `*ELASTIC`, `*BOUNDARY`, `*CLOAD`, `*STEP`, `*OUTPUT`, `*NODE OUTPUT`, and `*ELEMENT OUTPUT` only when required.
5. Define Internal Model Contract at a semantic level without C++ APIs.
6. Define HDF5 Result and Reference Schemas for `results.h5`, including metadata, mesh, step/frame groups, field output datasets, history output datasets, component naming, and matching keys.
7. Define optional CSV export schemas only when upstream requirements explicitly request CSV files or a comparison helper format.
8. Define units, coordinate system, component naming, output location, step/frame identity, and ID matching rules.
9. Define validation rules and open issues.
6. Define Output and CSV Schemas for `displacements.csv`, `reactions.csv`, `element_forces.csv`, `stresses.csv`, and optional result files.
7. Define units, coordinate system, component naming, output location, step/frame identity, and ID matching rules.
8. Define validation rules and open issues.
## Output Contract
@@ -39,8 +38,7 @@ Produce or revise `docs/io-definitions/<feature-id>-io.md` with:
- Model Data Mapping
- History Data Mapping
- Internal Model Contract
- HDF5 Result and Reference Schemas
- Optional CSV Export Schemas
- Output and CSV Schemas
- Validation Rules
- Downstream Handoff
@@ -50,17 +48,16 @@ Produce or revise `docs/io-definitions/<feature-id>-io.md` with:
- Do not design C++ APIs.
- Do not claim full Abaqus compatibility.
- Do not run Abaqus, Nastran, or any reference solver.
- Do not generate reference HDF5 artifacts or reference CSVs.
- Do not generate reference CSVs.
- Do not approve release readiness.
## Quality Gate
- Every supported keyword has a documented purpose, required data, and unsupported-case behavior.
- HDF5 schemas carry units, coordinate system, component naming, output location, step/frame identity, dataset paths, and ID matching rules.
- Optional CSV schemas carry the same semantics when explicitly required.
- CSV schemas carry units, coordinate system, component naming, output location, and ID matching rules.
- Unsupported Abaqus input is explicit: unsupported, ignored-with-warning, or requires user decision.
- The I/O contract is compatible with requirements, formulation, and reference comparison needs.
## Handoff
Send keyword and HDF5 schema contracts to Reference Model Agent and Implementation Planning Agent. Send dataset paths, comparison schema, ID matching, and tolerance-source constraints to Reference Verification Agent.
Send keyword and schema contracts to Reference Model Agent and Implementation Planning Agent. Send comparison schema, ID matching, and tolerance-source constraints to Reference Verification Agent.
.codex/skills/fesa-io-contract/agents/openai.yaml
+1 -1
View File
@@ -1,4 +1,4 @@
interface:
display_name: "FESA I/O Contract"
short_description: "Define solver I/O contracts"
default_prompt: "Use $fesa-io-contract to define Abaqus input and HDF5 result contracts."
default_prompt: "Use $fesa-io-contract to define Abaqus input and result CSV contracts."
.codex/skills/fesa-numerical-review/SKILL.md
+2 -2
View File
@@ -12,7 +12,7 @@ Use this skill to review a formulation as a numerical algorithm contract before
Read these first:
- `AGENTS.md`
- `docs/AGENT_RULES.md`
- `docs/SOLVER_AGENT_DESIGN.md`
- `docs/numerical-reviews/README.md`
- `docs/formulations/<feature-id>-formulation.md`
- Related requirements and research documents when needed
@@ -48,7 +48,7 @@ Produce or revise `docs/numerical-reviews/<feature-id>-review.md` with:
- Do not edit formulations directly.
- Do not design C++ APIs or file ownership.
- Do not run Abaqus, Nastran, or any reference solver.
- Do not generate reference HDF5 artifacts or reference CSVs.
- Do not generate reference CSVs.
- Do not approve release readiness.
- Do not decide reference comparison success.
.codex/skills/fesa-physics-sanity/SKILL.md
+3 -3
View File
@@ -12,12 +12,12 @@ Use this skill to determine whether reference-passing solver outputs are physica
Read these first:
- `AGENTS.md`
- `docs/AGENT_RULES.md`
- `docs/SOLVER_AGENT_DESIGN.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
- Stored solver and reference CSVs as read-only evidence
## Workflow
@@ -52,7 +52,7 @@ Produce or revise `docs/physics-evaluations/<feature-id>-physics-evaluation.md`
- 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 generate reference CSVs.
- Do not approve release readiness.
- Do not approve reference tolerance success.
.codex/skills/fesa-reference-comparison/SKILL.md
+7 -7
View File
@@ -1,6 +1,6 @@
---
name: fesa-reference-comparison
description: Use when running FESA solver HDF5 reference comparison, checking stored artifacts, result schemas, units, ID matching, tolerance metrics, and reference verification status.
description: Use when running FESA solver reference CSV comparison, checking stored artifacts, schema, units, ID matching, tolerance metrics, and reference verification status.
---
# FESA Reference Comparison
@@ -12,20 +12,20 @@ Use this skill to compare generated solver outputs against stored reference arti
Read these first:
- `AGENTS.md`
- `docs/AGENT_RULES.md`
- `docs/SOLVER_AGENT_DESIGN.md`
- `docs/reference-verifications/README.md`
- Build/Test report with `pass-for-reference-verification`
- `docs/reference-models/<feature-id>-reference-models.md`
- `docs/io-definitions/<feature-id>-io.md`
- Generated solver `results.h5`
- Generated solver result CSVs
- Stored `references/<feature-id>/<model-id>/` artifacts
## Workflow
1. Follow `ARTIFACT CHECK -> COMPARE -> CLASSIFY -> REPORT`.
2. ARTIFACT CHECK: verify `metadata.json`, required reference HDF5 files, generated solver `results.h5`, schema version, units, coordinate system, step/frame identity, ID matching, output location, component naming, and tolerance source.
2. ARTIFACT CHECK: verify `metadata.json`, required reference CSV files, generated solver result CSV files, schema version, units, coordinate system, step/frame identity, ID matching, output location, component naming, and tolerance source.
3. Stop with `needs-reference-artifacts`, `needs-solver-results`, or `needs-upstream-decision` when required comparison inputs are missing.
4. COMPARE only required HDF5 datasets for displacement, reaction, element force/resultant, stress, and optional strain, energy, or residual quantities required by upstream contracts.
4. COMPARE only required quantities: `displacements.csv`, `reactions.csv`, `element_forces.csv`, `stresses.csv`, and optional `strains.csv` or `energy_or_residual.csv`.
5. Apply upstream tolerance exactly. Do not loosen or reinterpret tolerance.
6. Report max absolute error, max relative error, RMS error, norm error, worst id, worst component, missing rows, extra rows, and pass/fail.
7. CLASSIFY failures as missing-reference-artifact, missing-solver-output, schema-mismatch, id-mismatch, unit-or-coordinate-mismatch, tolerance-failure, nonfinite-result, upstream-contract, or environment.
@@ -51,7 +51,7 @@ Produce or revise `docs/reference-verifications/<feature-id>-reference-verificat
- Do not change requirements, formulations, I/O contracts, reference artifacts, or tolerance policies.
- Do not change tolerance policies.
- Do not run Abaqus, Nastran, or any reference solver.
- Do not generate reference HDF5 artifacts or reference CSVs.
- Do not generate reference CSVs.
- Do not approve physics validation or release readiness.
## Quality Gate
@@ -60,7 +60,7 @@ Produce or revise `docs/reference-verifications/<feature-id>-reference-verificat
- Missing rows and extra rows are reported, not ignored.
- Nonfinite values are reported explicitly.
- `pass-for-physics-evaluation` means reference tolerance success only.
- Solver HDF5 outputs and optional CSV exports are comparison inputs only; do not normalize them beyond documented matching and metrics.
- Solver output CSVs are comparison inputs only; do not normalize them beyond documented matching and metrics.
## Handoff
.codex/skills/fesa-reference-comparison/agents/openai.yaml
+2 -2
View File
@@ -1,4 +1,4 @@
interface:
display_name: "FESA Reference Comparison"
short_description: "Compare solver HDF5 results"
default_prompt: "Use $fesa-reference-comparison to compare FESA solver HDF5 results against reference HDF5 artifacts."
short_description: "Compare solver CSV results"
default_prompt: "Use $fesa-reference-comparison to compare FESA solver CSVs against reference CSVs."
.codex/skills/fesa-reference-models/SKILL.md
+9 -10
View File
@@ -1,6 +1,6 @@
---
name: fesa-reference-models
description: Use when designing FESA reference model portfolios, Abaqus input artifact bundles, metadata provenance, required HDF5 reference artifacts, optional CSV export artifacts, coverage matrices, and implementation-planning handoffs.
description: Use when designing FESA reference model portfolios, Abaqus input artifact bundles, metadata provenance, required reference CSV artifacts, coverage matrices, and implementation-planning handoffs.
---
# FESA Reference Models
@@ -12,7 +12,7 @@ Use this skill to define test model portfolios and reference artifact contracts
Read these first:
- `AGENTS.md`
- `docs/AGENT_RULES.md`
- `docs/SOLVER_AGENT_DESIGN.md`
- `docs/reference-models/README.md`
- `docs/requirements/<feature-id>.md`
- `docs/research/<feature-id>-research.md`
@@ -26,8 +26,8 @@ Read these first:
2. Build a model inventory: smoke, analytical, patch test, benchmark, regression, and negative/invalid-input models.
3. For each model, record `model_id`, purpose, verified requirements, analysis type, element type, material, boundary conditions, loads, expected quantities, tolerance, source, and status.
4. Define `references/<feature-id>/<model-id>/` artifact bundle requirements.
5. Require `model.inp`, `metadata.json`, `results.h5`, and `README.md` unless explicitly not applicable; for the current MITC4 feature, record primary `abaqus_s4r/results.h5` and diagnostic `abaqus_s4/results.h5` when both are required.
6. Define optional CSV exports such as `displacements.csv`, `reactions.csv`, `element_forces.csv`, `stresses.csv`, `strains.csv`, or `energy_or_residual.csv` only when upstream acceptance criteria require them.
5. Require `model.inp`, `metadata.json`, `displacements.csv`, `reactions.csv`, `element_forces.csv`, `stresses.csv`, and `README.md` unless explicitly not applicable.
6. Define optional `strains.csv` and `energy_or_residual.csv` only when upstream acceptance criteria require them.
7. Define metadata provenance, units, coordinate system, output requests, artifact status, and limitations.
8. Build a Coverage Matrix mapping requirement id, model id, compared quantity, artifact file, tolerance, verification method, and status.
@@ -42,8 +42,7 @@ Produce or revise `docs/reference-models/<feature-id>-reference-models.md` with:
- Abaqus Input Requirements
- Artifact Bundle Contract
- Metadata JSON Contract
- Reference HDF5 Requirements
- Optional CSV Export Requirements
- Reference CSV Requirements
- Coverage Matrix
- Artifact Acceptance Checklist
- Open Issues and Downstream Handoff
@@ -54,7 +53,7 @@ Produce or revise `docs/reference-models/<feature-id>-reference-models.md` with:
- Do not implement parsers.
- Do not design C++ APIs or file ownership.
- Do not run Abaqus, Nastran, or any reference solver.
- Do not generate reference HDF5 artifacts or reference CSVs.
- Do not generate reference CSVs.
- Do not compare solver results.
- Do not approve release readiness.
@@ -62,9 +61,9 @@ Produce or revise `docs/reference-models/<feature-id>-reference-models.md` with:
- Every `must` requirement maps to at least one model and compared quantity.
- `model.inp` stays within the supported Abaqus keyword subset or records an open issue.
- `metadata.json` includes provenance, Abaqus version/source, units, coordinate system, tolerance, and HDF5 schema version.
- Missing required HDF5 artifacts keep the model at `needs-reference-artifacts`.
- `metadata.json` includes provenance, Abaqus version/source, units, coordinate system, tolerance, and CSV schema version.
- Missing required CSVs keep the model at `needs-reference-artifacts`.
## Handoff
Send model order and tests that should fail first to Implementation Planning Agent. Send HDF5 schema, matching, output location, and tolerance mapping to Reference Verification Agent. Send physical expectations to Physics Evaluation Agent.
Send model order and tests that should fail first to Implementation Planning Agent. Send schema, matching, output location, and tolerance mapping to Reference Verification Agent. Send physical expectations to Physics Evaluation Agent.
.codex/skills/fesa-release-readiness/SKILL.md
+2 -2
View File
@@ -12,7 +12,7 @@ Use this skill to audit whether a solver feature is ready for internal release c
Read these first:
- `AGENTS.md`
- `docs/AGENT_RULES.md`
- `docs/SOLVER_AGENT_DESIGN.md`
- `docs/releases/README.md`
- Physics Evaluation report with `pass-for-release-agent`
- Reference Verification report with `pass-for-physics-evaluation`
@@ -50,7 +50,7 @@ Produce or revise `docs/releases/<feature-id>-release.md` with:
- Do not implement code.
- Do not edit source code, tests, CMake files, requirements, formulations, I/O 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 generate reference CSVs.
- Do not override failed or missing gates.
- Do not publish, deploy, package, tag, commit, or externally release anything unless the user explicitly asks.
.codex/skills/fesa-requirements-baseline/SKILL.md
+17 -17
View File
@@ -1,18 +1,18 @@
---
name: fesa-requirements-baseline
description: Use when analyzing new FESA solver feature requirements, acceptance criteria, tolerance decisions, verification quantities, and a requirement verification matrix before research, formulation, reference modeling, or implementation planning.
description: Use when defining FESA solver feature requirements, acceptance criteria, tolerance decisions, verification quantities, and a requirement verification matrix before research, formulation, reference modeling, or implementation planning.
---
# FESA New Solver Feature Requirements Analysis
# FESA Requirements Baseline
Use this skill to turn a new solver feature request into a verifiable new solver feature requirements analysis baseline that downstream agents can use without guessing.
Use this skill to turn a solver feature request into a verifiable baseline that downstream agents can use without guessing.
## Inputs
Read these first:
- `AGENTS.md`
- `docs/AGENT_RULES.md`
- `docs/SOLVER_AGENT_DESIGN.md`
- `docs/requirements/README.md`
- User feature request, target capability, constraints, and known exclusions
- Existing `docs/requirements/<feature-id>.md` when revising a feature
@@ -20,26 +20,26 @@ Read these first:
## Workflow
1. Assign a stable `feature_id` in kebab case.
2. Analyze purpose, included scope, excluded scope, and analysis definition.
3. Convert requested behavior into analyzed `shall` statements with ids like `FESA-REQ-<FEATURE>-###`.
4. Analyze and record verification quantities: displacement, reaction, element force, stress, strain, energy, or residual.
5. Analyze and record Tolerance Policy values or mark them `needs-user-decision`.
6. Analyze and record Reference Artifact Requirements under `references/<feature-id>/`.
7. Build a Requirement Verification Matrix that maps analyzed requirement, source, verification method, acceptance criteria, tolerance, downstream agents, and status.
2. Define purpose, included scope, excluded scope, and analysis definition.
3. Convert requested behavior into `shall` statements with ids like `FESA-REQ-<FEATURE>-###`.
4. Define verification quantities: displacement, reaction, element force, stress, strain, energy, or residual.
5. Record Tolerance Policy values or mark them `needs-user-decision`.
6. Record Reference Artifact Requirements under `references/<feature-id>/`.
7. Build a Requirement Verification Matrix that maps requirement, source, verification method, acceptance criteria, tolerance, downstream agents, and status.
8. Keep unresolved decisions visible as open issues; do not hide gaps behind vague wording.
## Output Contract
Produce or revise `docs/requirements/<feature-id>.md` as a new solver feature requirements analysis document with:
Produce or revise `docs/requirements/<feature-id>.md` with:
- Metadata with `feature_id`, analysis status, owner agent, and date
- Metadata with `feature_id`, status, owner agent, and date
- Purpose, In Scope, Out Of Scope, and Analysis Definition
- Input and Output Requirements
- Verification Quantities
- Tolerance Policy
- Reference Artifact Requirements
- Requirement Verification Matrix
- Open Questions and Downstream Handoff from the requirements analysis
- Open Questions and Downstream Handoff
## Boundaries
@@ -47,14 +47,14 @@ Produce or revise `docs/requirements/<feature-id>.md` as a new solver feature re
- 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 generate reference HDF5 artifacts or reference CSVs.
- Do not generate reference CSVs.
- Do not approve release readiness.
## Quality Gate
- Every `must` requirement analyzed in the document has a verification method and acceptance criteria.
- Every numerical requirement analyzed in the document has units, coordinate system, and tolerance or an explicit owner for the decision.
- Every reference-comparison requirement analyzed in the document names required artifacts.
- Every `must` requirement has a verification method and acceptance criteria.
- Every numerical requirement has units, coordinate system, and tolerance or an explicit owner for the decision.
- Every reference-comparison requirement names required artifacts.
- Words like "accurate", "fast", and "Abaqus-like" are converted into measurable criteria or open questions.
## Handoff
.codex/skills/fesa-requirements-baseline/agents/openai.yaml
+3 -3
View File
@@ -1,4 +1,4 @@
interface:
display_name: "FESA Requirements Analysis"
short_description: "Analyze new solver requirements"
default_prompt: "Use $fesa-requirements-baseline to analyze new FESA solver feature requirements."
display_name: "FESA Requirements Baseline"
short_description: "Define solver requirements"
default_prompt: "Use $fesa-requirements-baseline to define verifiable FESA solver requirements."
.codex/skills/fesa-research-evidence/SKILL.md
+2 -2
View File
@@ -12,7 +12,7 @@ Use this skill to collect source-backed evidence for solver features while separ
Read these first:
- `AGENTS.md`
- `docs/AGENT_RULES.md`
- `docs/SOLVER_AGENT_DESIGN.md`
- `docs/research/README.md`
- `docs/requirements/<feature-id>.md`
- User-supplied books, papers, manuals, or benchmark constraints
@@ -46,7 +46,7 @@ Produce or revise `docs/research/<feature-id>-research.md` with:
- Do not finalize FEM formulations.
- Do not design C++ APIs or file ownership.
- Do not run Abaqus, Nastran, or any reference solver.
- Do not generate reference HDF5 artifacts or reference CSVs.
- Do not generate reference CSVs.
- Do not approve release readiness.
## Quality Gate