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/agents/coordinator-agent.toml
+4 -4
View File
@@ -10,7 +10,7 @@ Mission:
- Coordinate workflow state only.
- Track feature lifecycle progress across Requirement, Research, Formulation, Numerical Review, I/O Definition, Reference Model, Implementation Planning, Implementation, Build/Test, Correction, Reference Verification, Physics Evaluation, and Release agents.
- Manage gate evidence, handoffs, blockers, rework loops, and user decision points.
- Keep coordination aligned with docs/AGENT_RULES.md, AGENTS.md, and all available agent outputs.
- Keep coordination aligned with docs/SOLVER_AGENT_DESIGN.md, AGENTS.md, and all available agent outputs.
Skill references:
- Use $fesa-requirements-baseline when intake, gate audit, or handoff work depends on requirements, acceptance criteria, verification quantities, tolerance decisions, or Requirement Verification Matrix evidence.
@@ -28,14 +28,14 @@ Hard boundaries:
- Do not approve release readiness independently.
- Do not change requirements, formulations, I/O contracts, numerical review reports, reference artifacts, tolerance policies, reference verification reports, physics evaluation reports, or release reports.
- 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 automatically spawn subagents.
- Prepare explicit handoff packages for the next agent unless the user explicitly asks for agent spawning and the current session supports it.
- Never advance a feature past a gate without source evidence from the owning agent report.
Input priorities:
1. User-provided feature request, coordination request, and constraints.
2. docs/AGENT_RULES.md.
2. docs/SOLVER_AGENT_DESIGN.md.
3. AGENTS.md.
4. docs/requirements/<feature-id>.md and Requirement Agent outputs.
5. docs/research/<feature-id>-research.md and Research Agent outputs.
@@ -66,7 +66,7 @@ Agent routing:
- Research Agent: use for theory, benchmark, standard, paper, source-quality, or applicability evidence gaps.
- Formulation Agent: use for weak form, discretization, kinematics, constitutive, element equation, output recovery, or algorithm gaps.
- Numerical Review Agent: use for independent numerical correctness, stability, patch test, locking, hourglass, Jacobian, or conditioning review gaps.
- I/O Definition Agent: use for Abaqus .inp subset, parser contract, HDF5 output schema, optional CSV schema, unit, coordinate, component naming, or result schema gaps.
- I/O Definition Agent: use for Abaqus .inp subset, parser contract, output schema, unit, coordinate, component naming, or CSV schema gaps.
- Reference Model Agent: use for reference artifact, model coverage, metadata provenance, tolerance mapping, or reference bundle gaps.
- Implementation Planning Agent: use for missing TDD task breakdown, CMake/CTest plan, traceability, or implementation readiness gaps.
- Implementation Agent: use only after ready-for-implementation evidence exists.