KOKO\Mimi
2.6 KiB
name, description
| name | description |
|---|---|
| fem-release-readiness | Use when a structural FEM solver feature has completed technical gates and needs an evidence-based release-readiness audit. |
FEM Release Readiness
Audit closure evidence and prepare a release recommendation without modifying technical contracts or performing a release.
Inputs
- All lifecycle artifacts for one
feature_idand contract revision - Passing configured full validation and required comparison evidence
- Passing physics review
- Correction history, accepted risks, and project release policy
Workflow
- Inventory required artifacts and verify identity, revision, freshness, ownership, outcome, and absence of contradictions.
- Trace every blocking requirement through acceptance criteria, implementation/tests, required numerical or reference evidence, physics review, and final disposition.
- Confirm unresolved defects, deferred scope, compatibility limits, unsupported behavior, accepted risks, and environment limits are explicit.
- Produce the checklist, known limitations, release-notes draft, and readiness verdict. Return missing or failed evidence to its owning stage.
Use evidence and handoff to validate stage envelopes. Read toolchain and verification when auditing command or comparison evidence. Use workflow and decision authority for release-scope decisions.
Output
Follow Feature document management: read the Coordinator's feature context, keep main reports concise, and link necessary owned details in the same feature folder.
Create or revise docs/<feature-id>/release.md with release scope, gate inventory, requirement traceability, validation summary, known limitations, deferred items, release-notes draft, readiness verdict, residual risks, and handoff.
Evidence
A ready verdict requires complete, passing, current evidence for every blocking gate. Record artifact paths and hashes, configuration/toolchain identity, test and comparison summaries, approved exceptions, and the exact contract revision audited.
Boundary
Do not implement or correct code, edit tests or upstream contracts, waive missing evidence, change acceptance or tolerance, or reinterpret a failed gate. Do not commit, tag, package, publish, deploy, or externally release anything unless the user explicitly authorizes that separate action. Readiness is a recommendation, not publication approval.