docs: refresh Abaqus subroutine guidance

This commit is contained in:
KOKO\Mimi
2026-08-18 11:27:22 +09:00
parent a3197dc2e3
commit e76c1b96fd
64 changed files with 498 additions and 4560 deletions
+19 -38
View File
@@ -6,56 +6,37 @@
## Current Objective
3D Euler-Bernoulli beam Abaqus/Standard `UEL` 구현을 하네스 phase 흐름에 따라 진행한다.
Abaqus User Subroutine 프로젝트 지침, 문서, custom agent, skill을 정비한다. FEM 지식은 `fem-theory-query`로 탐색하고, Abaqus 매뉴얼은 `INDEX_MAP.md``INDEX.md`를 거쳐 원문 span을 읽으며, 사용자가 폐기한 과거 feature 산출물의 잔존 참조를 제거한다.
## Active Phase
- Phase directory: `phases/uel-3d-euler-beam`
- Current planned entry point: `python scripts/execute.py uel-3d-euler-beam`
- First pending action: execute `step8` validation readiness using the corrected Abaqus-facing `UEL` wrapper/interface
- Phase: project guidance refresh complete
- Owner: root agent
- Design: `docs/superpowers/specs/2026-08-18-project-guidance-refresh-design.md`
- Implementation plan: `docs/superpowers/plans/2026-08-18-project-guidance-refresh.md`
## Planned Steps
1. Requirements: `docs/requirements/uel-3d-euler-beam.md`
2. Research: `docs/research/uel-3d-euler-beam-research.md`
3. Formulation: `docs/formulations/uel-3d-euler-beam.md`
4. Numerical review: `docs/numerical-reviews/uel-3d-euler-beam.md`
5. Interface contract: `docs/io-definitions/uel-3d-euler-beam.md`
6. Test/reference model plan: `docs/reference-models/uel-3d-euler-beam.md`
7. RED no-Abaqus Fortran tests and manifest - completed
8. GREEN Fortran implementation - completed
9. Validation, physics sanity, and readiness audit - next
1. [완료] 사용자 승인을 받은 설계와 구현 계획을 기록한다.
2. [완료] `AGENTS.md`, 핵심 docs, 관련 agent와 skill을 최소 수정한다.
3. [완료] 폐기된 과거 feature의 versioned 파일과 참조를 제거한다.
4. [완료] 테스트 없이 정적 검색, 문서 재독, diff 검사로 검증한다.
5. [완료] `PROGRESS.md``WORKNOTE.md`를 갱신하고 변경 사항을 handoff한다.
## Success Criteria
- Every must requirement has verification method, acceptance criteria, and tolerance or decision owner.
- Fortran production changes follow RED -> GREEN -> VERIFY.
- No-Abaqus tests pass through `python scripts/validate_fortran.py` when compiler and manifest are available.
- Workspace validation passes through `python scripts/validate_workspace.py`.
- Solver-result validation is marked complete only after externally generated ODB-extracted CSV artifacts are provided and validated.
- FEM 관련 지식 탐색이 `fem-theory-query`로 명시된다.
- Abaqus 매뉴얼 탐색 순서가 `INDEX_MAP.md``INDEX.md` → 모든 `source_ranges`로 명시된다.
- 외부 Abaqus PC에서 생성한 변위·응력 CSV 비교 계약이 유지된다.
- 폐기된 project-specific feature의 versioned 파일과 참조가 남지 않는다.
- Harness skill과 테스트를 실행하지 않는다.
## Out Of Scope Until Explicitly Approved
- Running Abaqus jobs from this repository.
- Direct ODB parsing in this repository.
- Fabricating reference CSV, `.msg`, `.dat`, `.log`, or `.sta` evidence.
- Geometric nonlinearity, Timoshenko shear deformation, mass, damping, distributed loads, plasticity, damage, thermal strain, warping torsion, and section offsets for the first UEL implementation.
- Abaqus job 실행 또는 ODB 직접 parsing
- Harness phase 생성 또는 실행
- Validation script 구현 변경
## Open Decisions
- Confirm exact first-scope beam assumptions in the requirements step.
- Decide `PROPS`/`JPROPS` ordering and orientation-vector convention in the interface step.
- Decide exact no-Abaqus Fortran source and test file layout in the reference model step.
- External Abaqus validation artifacts still need to be supplied by the user before solver-result comparison.
## Concurrent Documentation Task: Manual Index
- Objective: create an AI-agent-oriented index for the Markdown chunks under `docs/AbaqusUserSubroutineManual`.
- Scope: document the index schema in `docs/AbaqusUserSubroutineManual/INDEX_DESIGN.md` and index all numbered leaf sections in `docs/AbaqusUserSubroutineManual/INDEX.md`.
- Success criteria:
- all `# <chapter>.<section>.<entry>` and `# A.<entry>` leaf headings are represented exactly once;
- every source range uses 1-based inclusive line numbers and resolves to an existing file;
- multi-file sections list every file span explicitly;
- indexed heading text and location match the source Markdown;
- agents are instructed to treat the manual, not the summary, as authoritative.
- Out of scope: editing the source manual chunks or adding a persistent index generator.
- None.