FESADev/docs/PLAN.md

FESA Multi-Agent Plan

Purpose

This file tells a new AI Agent what work is planned and how to continue without reconstructing project intent from the full conversation.

New Agents must read AGENTS.md, this file, docs/PROGRESS.md, docs/WORKNOTE.md, and docs/AGENT_RULES.md before editing files.

Active Objective

Build the FESA structural solver foundation around the initial feature mitc4-linear-static-shell.

Current High-Level Plan

1. Maintain project-level documentation and handoff files.
2. Define requirements for mitc4-linear-static-shell.
3. Gather research evidence for MITC4, OpenSees ShellMITC4, Abaqus S4/S4R, patch tests, and Scordelis-Lo.
4. Write FEM formulation for the MITC4 linear static shell feature.
5. Define Abaqus .inp input subset and HDF5 output/reference schemas.
6. Define stored Abaqus S4R/S4 reference model bundles.
7. Write a TDD implementation plan.
8. Implement C++17/MSVC code using CMake/CTest, MKL, TBB, and HDF5.
9. Compare FESA HDF5 results against stored Abaqus S4R reference artifacts using abs-or-rel 1e-5.
10. Prepare release documentation after reference verification passes.

Acceptance Criteria

• Every solver feature follows the stage-gated workflow in AGENTS.md.
• C++ production changes are test-first.
• python scripts/validate_workspace.py remains the default validation path.
• MITC4 reference comparison covers nodal displacement, reaction, element internal force/resultant, and stress.
• Result comparison uses a single tolerance value 1e-5 with absolute-or-relative pass logic.

Coordination Rules

• Update this file when the plan, scope, ordering, or acceptance criteria change.
• Update docs/PROGRESS.md after completing work or running validation.
• Update docs/WORKNOTE.md after mistakes, failed approaches, environment traps, or decisions that future Agents should not rediscover.
• Keep .codex/agents/*.toml and .codex/skills/*/SKILL.md pointed at docs/AGENT_RULES.md for common operating rules.

Known Blockers

• No CMake project exists yet, so python scripts/validate_workspace.py currently takes the no-op path.
• HDF5 is not detected in standard local environment paths; implementation will need HDF5_ROOT or HDF5_DIR.
• Abaqus reference artifacts are not generated by Agents and must be supplied by a human-approved process.