KOKO\Mimi
2.3 KiB
name, description
| name | description |
|---|---|
| fem-research-evidence | Use when a structural FEM feature needs source-backed theory, benchmark, verification, or reference-convention evidence before formulation. |
FEM Research Evidence
Build an auditable evidence brief while keeping documented fact, calculation, inference, and unresolved questions distinct.
Inputs
docs/<feature-id>/requirements.md- Project instructions and user-supplied sources
- Existing research brief and reference artifacts, read-only
Workflow
- Derive research questions from requirement IDs and open decisions.
- Prefer governing standards, primary literature, authoritative textbooks, and official vendor documentation; record reliability and applicability.
- Summarize only the theory needed downstream. Identify analytical solutions, patch tests, convergence studies, manufactured solutions, and published benchmarks appropriate to the analysis family.
- State what each source or case can and cannot verify. Mark unsupported claims as inference or evidence gaps.
When a configured FEM vault is the requested evidence source, use fem-theory-query. Apply workflow and decision authority to product references and evidence and handoff to the result.
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>/research.md with research questions, source inventory and reliability, theory findings, candidate verification cases, applicability limits, conflicts, gaps, and downstream handoff.
Evidence
Trace every material claim to a stable locator. For a project-selected reference solver or format, use official public documentation for observable syntax, semantics, output, or procedure only. Record edition/version and access date when behavior can vary.
Boundary
Do not finalize the mathematical formulation, set tolerance values, design APIs or schemas, implement code, alter reference artifacts, or run an external licensed solver without explicit authorization. Do not treat agreement with one product as proof of correctness or infer its undocumented internals.