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/implementation-planning-agent.toml
+3 -3
View File
@@ -23,7 +23,7 @@ Hard boundaries:
- Do not edit CMake.
- Do not run CMake/CTest.
- Do not run Abaqus, Nastran, or any reference solver.
- Do not generate reference HDF5 files or deterministic CSV views.
- Do not generate or modify Abaqus reference CSV files.
- Do not compare solver results.
- Do not approve release readiness.
- Do not finalize C++ APIs, class names, storage layout, or file ownership beyond candidate planning.
@@ -57,7 +57,7 @@ Required Implementation Plan sections:
5. TDD Test Plan: unit, integration, parser/I/O, and reference-comparison tests ordered by RED/GREEN cycle.
6. CMake/CTest Plan: target candidates, add_test needs, labels, and ctest -C Debug execution expectations.
7. Candidate Files and Ownership: candidate source/header/test/CMake files and responsibility boundary; never final API.
8. Data Flow Contract: Abaqus .inp input, internal model, solver results.h5, deterministic CSV views, and reference comparison flow.
8. Data Flow Contract: Abaqus .inp input, internal model, solver results.h5, Abaqus reference CSV files under reference/<model-id>/, and FESA HDF5-to-reference-CSV comparison flow.
9. Acceptance Traceability Matrix: requirement id, task id, test id, reference model id, and acceptance criterion.
10. Validation Commands: python -m unittest discover -s scripts -p \"test_*.py\", python scripts/validate_workspace.py, and feature-specific CTest commands.
11. Risks and Downstream Handoff: Implementation Agent, Build/Test Executor Agent, Correction Agent, and Reference Verification Agent.
@@ -71,7 +71,7 @@ Status rules:
Quality checks:
- All must requirements must map to at least one task and one test.
- Reference artifact dependent behavior must include references/<feature-id>/<model-id>/ and HDF5/CSV view comparison test planning.
- Reference artifact dependent behavior must include reference/<model-id>/ and FESA HDF5-to-reference-CSV comparison test planning.
- CMake/CTest planning must remain compatible with MSVC x64 Debug validation.
- The plan must explicitly preserve the order: write test, verify failure, implement minimally, run validation.
- Do not claim reference tolerance success or release readiness.