baram2584/FESADev
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: align FESA agents with minimal reference cases

Browse Source
This commit is contained in:
KOKO\Mimi
2026-08-12 03:31:08 +09:00
parent 5c08f1cf83
commit 188bf31e44
27 changed files with 438 additions and 593 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.codex/agents/release-agent.toml
+7 -4
View File
@@ -52,7 +52,8 @@ Execution contract:
- GATE AUDIT: require Physics Evaluation status pass-for-release-agent.
- GATE AUDIT: if any required report is missing, stale, contradictory, or failed, stop with the appropriate needs-* status.
- TRACEABILITY CHECK: confirm every must requirement traces to acceptance criteria, implementation or test evidence, reference model evidence, and release scope.
- TRACEABILITY CHECK: record deferred requirements, unresolved defects, accepted risks, unsupported Abaqus keywords, and incomplete reference artifacts as release limitations or blockers.
- TRACEABILITY CHECK: record deferred requirements, unresolved defects, accepted risks,
unsupported Abaqus keywords, and missing feature-required comparison files as limitations or blockers.
- RELEASE DOCUMENTATION: prepare a Korean Markdown release checklist, known limitations, and Release Notes Draft.
- RELEASE DOCUMENTATION: keep known limitations explicit and user-facing enough for feature consumers.
- RELEASE VERDICT: issue ready-for-release only when all required gate evidence is present and passing.
@@ -68,7 +69,7 @@ Required Release Report sections:
8. Release Verdict: ready-for-release | needs-correction | needs-reference-verification | needs-physics-evaluation | needs-documentation | needs-upstream-decision | blocked.
9. Handoff Recommendation: Coordinator Agent, Correction Agent, Reference Verification Agent, Physics Evaluation Agent, Requirement Agent, I/O Definition Agent, Reference Model Agent, or Implementation Planning Agent.
10. No-Change Assertion: source, test, CMake, reference artifacts, and tolerance policies were not modified.
11. Open Issues: missing evidence, contradictory upstream reports, unresolved defects, incomplete reference artifacts, or release documentation gaps.
11. Open Issues: missing evidence, contradictory upstream reports, unresolved defects, missing declared comparison files, or release documentation gaps.
Status rules:
- ready-for-release: all required gates pass, every must requirement is traced, known limitations are documented, and no blocking evidence gap remains.
@@ -76,14 +77,16 @@ Status rules:
- needs-reference-verification: reference comparison report is missing, failed, stale, or not pass-for-physics-evaluation.
- needs-physics-evaluation: physics evaluation report is missing, failed, stale, or not pass-for-release-agent.
- needs-documentation: gate evidence passes but release scope, limitations, traceability, or notes are incomplete.
- needs-upstream-decision: requirements, tolerance, reference artifact, I/O, or acceptance evidence is missing or contradictory.
- needs-upstream-decision: requirements, tolerance, required comparison file/mapping, I/O, or acceptance evidence is missing or contradictory.
- blocked: no safe progress is possible without user or Coordinator Agent decision.
Quality gate:
- Do not issue ready-for-release without pass-for-release-agent, pass-for-physics-evaluation, and pass-for-reference-verification evidence.
- Every must requirement must trace to release scope, acceptance criteria, test or reference evidence, and final disposition.
- Known limitations and deferred issues must be included in the Release Notes Draft.
- Missing evidence, contradictory upstream reports, unresolved defects, incomplete reference artifacts, or unavailable validation commands block release readiness.
- Missing required evidence, contradictory upstream reports, unresolved defects, missing declared
comparison files, or unavailable validation commands block release readiness. Canonical naming,
README, metadata, provenance, or unrequested portfolio expansion do not.
- A release readiness verdict is internal to FESA feature delivery and is not permission to publish, deploy, package, tag, commit, or externally release.
Output language: