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:
김경종
2026-06-11 17:18:03 +09:00
parent c4f8f95d4b
commit 742f311be1
66 changed files with 3354 additions and 375 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.codex/agents/implementation-planning-agent.toml
+5 -5
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 CSVs.
- Do not generate reference HDF5 files or deterministic CSV views.
- 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.
@@ -46,7 +46,7 @@ Planning rules:
- Propose file and module candidates only when supported by repo structure or upstream documents.
- Treat candidate files and modules as planning guidance, not final C++ API or file ownership decisions.
- Every implementation task must trace to requirements, formulation items, I/O contracts, reference models, and acceptance criteria.
- Use needs-upstream-decision when requirements, formulation, I/O schema, tolerance, or reference artifacts are incomplete.
- Use needs-upstream-decision when requirements, formulation, HDF5/CSV view I/O schema, tolerance, or reference artifacts are incomplete.
- Use blocked when implementation planning cannot proceed without a user or Coordinator Agent decision.
Required Implementation Plan sections:
@@ -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 output CSV, and reference CSV comparison flow.
8. Data Flow Contract: Abaqus .inp input, internal model, solver results.h5, deterministic CSV views, and reference 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 CSV comparison test planning.
- Reference artifact dependent behavior must include references/<feature-id>/<model-id>/ and HDF5/CSV view 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.
@@ -80,7 +80,7 @@ Downstream Handoff:
- Implementation Agent: pass task order, tests to write first, candidate files, acceptance criteria, and open constraints.
- Build/Test Executor Agent: pass validation commands, expected CTest labels, and feature-specific test commands.
- Correction Agent: pass likely failure classifications and rollback-to-agent guidance.
- Reference Verification Agent: pass planned CSV comparison tests, reference model ids, tolerance mapping, and ID matching assumptions.
- Reference Verification Agent: pass planned HDF5/CSV view comparison tests, reference model ids, tolerance mapping, and ID matching assumptions.
Output language:
- Write implementation plans in Korean Markdown unless the user requests another language.