chore: remove retired workflow and historical material
This commit is contained in:
KOKO\Mimi
@@ -1,10 +0,0 @@
|
||||
---
|
||||
name: fem-formulation-spec
|
||||
description: Produce an implementation-ready mathematical formulation for a new or changed structural FEM model.
|
||||
---
|
||||
|
||||
# FEM Formulation Specification
|
||||
|
||||
Define only the model required by the assigned feature: assumptions, strong/weak form, kinematics, constitutive update, discretization, DOF/component and sign conventions, residual, consistent tangent where applicable, integration, state update, recovery, and formulation-level invariants. Distinguish small/large deformation and analysis-family assumptions.
|
||||
|
||||
Use approved requirements and evidence; consult [analysis-family guidance](references/analysis-families.md) when specifying that family's formulation. Make physics-changing choices explicit and return unresolved scope or evidence gaps rather than silently choosing them. Include verification implications, but do not prescribe C++ storage, persistent schema, tolerance values, or reference-result edits.
|
||||
@@ -1,4 +0,0 @@
|
||||
interface:
|
||||
display_name: "FEM Formulation Specification"
|
||||
short_description: "Specify structural FEM mathematics"
|
||||
default_prompt: "Use $fem-formulation-spec to specify the mathematics for an approved structural FEM feature."
|
||||
@@ -1,33 +0,0 @@
|
||||
# Structural Analysis Family Guidance
|
||||
|
||||
Read only the family selected by the approved requirements. Coupled features apply each relevant section and define the coupling terms explicitly.
|
||||
|
||||
## Common
|
||||
|
||||
Check DOF ordering, boundary conditions, units, coordinate transforms, rigid-body modes, element orientation, residual convention, output location, and conservation or equilibrium identities.
|
||||
|
||||
## Linear static
|
||||
|
||||
Define linearization assumptions, stiffness symmetry expectations, load assembly, constraint treatment, reactions, patch tests, rigid-body/null-space checks, and mesh-convergence quantities.
|
||||
|
||||
## Nonlinear static
|
||||
|
||||
Define configuration and strain/stress measures, state update, residual and consistent tangent, load/time parameter, convergence norms, increment/cutback behavior, path dependence, and energy or work checks.
|
||||
|
||||
## Modal, eigenvalue, and buckling
|
||||
|
||||
Define matrix problem, boundary conditions, mass or geometric stiffness, eigensolver target, normalization, repeated-mode handling, sign/phase invariance, residual norms, and mode correlation. Distinguish linearized buckling from nonlinear collapse.
|
||||
|
||||
## Dynamics
|
||||
|
||||
Define mass and damping, initial conditions, time integration, stability and algorithmic dissipation, load history, time-step convergence, energy balance, frequency/phase measures, and modal truncation where applicable.
|
||||
|
||||
## Contact and constraints
|
||||
|
||||
Define gap and normal orientation, active-set/search semantics, normal and tangential laws, enforcement method, consistent contributions, state transitions, penetration/slip measures, and action-reaction checks.
|
||||
|
||||
## Material nonlinearity
|
||||
|
||||
Define admissible state, yield/failure surface, flow/evolution laws, integration algorithm, consistent material tangent, history initialization, loading/unloading cases, and single-point constitutive tests.
|
||||
|
||||
Do not apply an irrelevant checklist merely for completeness. If the family is ambiguous and the choice changes physical meaning or acceptance, return `needs-user-decision`.
|
||||
@@ -1,12 +0,0 @@
|
||||
---
|
||||
name: fem-implementation-tdd
|
||||
description: Plan, implement, or correct structural FEM solver code with behavior-focused tests and configured verification.
|
||||
---
|
||||
|
||||
# FEM Implementation
|
||||
|
||||
Read the assigned task, directly affected contracts, and repository build configuration. Keep the change minimal and preserve public boundaries, units, ordering, state ownership, deterministic behavior, and fail-closed diagnostics.
|
||||
|
||||
For changed behavior, add or update meaningful verification and observe the failure before a bug fix when practical. Then implement the smallest correction and run affected configured checks. Run the configured full build/test once when the solver feature is complete, requested, or needed after broad impact. Required reference comparison must validate identity, quantities, units, row completeness, finite values, metrics, and the approved tolerance; do not alter references or tolerances to pass.
|
||||
|
||||
Read [toolchain-and-verification.md](references/toolchain-and-verification.md) when selecting configured commands or evaluating comparison evidence. Return changed files, commands and exit codes, decisive results, and blockers. Do not require phase files, automatic Git actions, or a formal RED/GREEN report for harmless refactors with sufficient coverage.
|
||||
@@ -1,4 +0,0 @@
|
||||
interface:
|
||||
display_name: "FEM Implementation TDD"
|
||||
short_description: "Implement and verify structural FEM code"
|
||||
default_prompt: "Use $fem-implementation-tdd to implement and verify this structural FEM solver change."
|
||||
@@ -1,7 +0,0 @@
|
||||
# Toolchain and Verification
|
||||
|
||||
Choose actual commands from `.harness/config.json`, then project presets/build metadata and repository instructions. `python scripts/execute.py` runs the configured complete build/test; use actual configured commands directly for focused checks. Missing metadata is not a passing solver validation.
|
||||
|
||||
For behavior changes, observe the relevant failing test before a fix when practical, make the minimal change, and rerun affected checks. Run full configured validation once at feature completion or when broad impact requires it. Preserve warning requirements.
|
||||
|
||||
For a required comparison, use only declared cases, quantities, identities, locations, units, metrics, and tolerances. Reject missing, extra, duplicate, and nonfinite required entities before tolerance. Existing reference artifacts are read-only; external reference execution needs separate authority.
|
||||
@@ -1,10 +0,0 @@
|
||||
---
|
||||
name: fem-io-contract
|
||||
description: Define supported structural solver input semantics, diagnostics, result schema, and deterministic comparison mapping.
|
||||
---
|
||||
|
||||
# FEM I/O Contract
|
||||
|
||||
Specify the assigned supported input subset, syntax and semantics, validation/diagnostics, source-label preservation, units, coordinates, components, internal mapping, authoritative output schema, and deterministic comparison projection. Unsupported meaningful semantics fail closed unless an explicit approved warning policy applies.
|
||||
|
||||
Use public Abaqus material only for observable convention. State any supported difference; do not infer private parser, data model, algorithm, or output-database behavior. A compatibility or authoritative-schema change is a user decision when it changes the public contract. Return the contract and open gaps; do not select physics, tolerances, implementation, or alter reference artifacts.
|
||||
@@ -1,4 +0,0 @@
|
||||
interface:
|
||||
display_name: "FEM I/O Contract"
|
||||
short_description: "Define structural FEM interface contracts"
|
||||
default_prompt: "Use $fem-io-contract to define deterministic interfaces for an approved structural FEM feature."
|
||||
@@ -1,10 +0,0 @@
|
||||
---
|
||||
name: fem-numerical-review
|
||||
description: Independently assess a structural FEM formulation, numerical risks, and verification/reference-case readiness.
|
||||
---
|
||||
|
||||
# FEM Numerical Review
|
||||
|
||||
Independently examine the assigned formulation and evidence for dimensions, signs, DOF ordering, coordinate transforms, residual/tangent consistency, Jacobian and quadrature rules, rigid-body modes, conditioning, locking/hourglass risks, convergence, and recovery. Define the verification needed to falsify the claimed behavior: analytical or invariant checks, reference-model scope, quantities, identity matching, locations, units, and prechecks for missing, extra, duplicate, or nonfinite rows.
|
||||
|
||||
Apply [toolchain-and-verification.md](../fem-implementation-tdd/references/toolchain-and-verification.md) only when reviewing command or comparison evidence. Follow `docs/TOLERANCE.md` for metrics and tolerance ownership; never loosen criteria because output failed. Return actionable findings, evidence paths, and residual risks without editing the formulation, implementation, I/O contract, or reference artifacts.
|
||||
@@ -1,4 +0,0 @@
|
||||
interface:
|
||||
display_name: "FEM Numerical Review"
|
||||
short_description: "Review structural FEM numerical readiness"
|
||||
default_prompt: "Use $fem-numerical-review to independently review a structural FEM formulation and its verification readiness."
|
||||
@@ -1,10 +0,0 @@
|
||||
---
|
||||
name: fem-physics-review
|
||||
description: Assess validated structural FEM results for equilibrium, physical plausibility, and model-coverage limits.
|
||||
---
|
||||
|
||||
# FEM Physics Review
|
||||
|
||||
Review the assigned result evidence for equilibrium and reactions, load/displacement direction, sign conventions, symmetry, element force balance, stress/strain/energy sanity, rigid-body symptoms, expected limits, and model coverage. A numerical comparison pass is evidence, not by itself physical validation.
|
||||
|
||||
Record checked artifacts, calculation or invariant, applicable approved threshold, conclusion, assumptions, untested behavior, and residual risk. Return implementation, formulation, or evidence issues to their owner; do not create new acceptance gates, edit code/contracts/tolerances/reference artifacts, or authorize release.
|
||||
@@ -1,4 +0,0 @@
|
||||
interface:
|
||||
display_name: "FEM Physics Review"
|
||||
short_description: "Review structural FEM physical plausibility"
|
||||
default_prompt: "Use $fem-physics-review to evaluate the physical plausibility of validated structural FEM results."
|
||||
@@ -1,10 +0,0 @@
|
||||
---
|
||||
name: fem-release-readiness
|
||||
description: Audit a structural FEM feature's evidence and limitations when the user explicitly requests release readiness.
|
||||
---
|
||||
|
||||
# FEM Release Readiness
|
||||
|
||||
Use only for an explicit release-readiness audit. Review the requested feature's relevant contracts, validation/reference evidence, known limitations, deferred work, and risks. Check that blocking requirements have credible evidence and that unsupported behavior is explicit; report contradictions or missing evidence rather than waiving them.
|
||||
|
||||
Produce a concise readiness recommendation with evidence paths, commands/exit codes where relevant, limitations, and residual risks. This is not a mandatory lifecycle stage and does not authorize code changes, commits, tags, packages, publication, deployment, or release.
|
||||
@@ -1,4 +0,0 @@
|
||||
interface:
|
||||
display_name: "FEM Release Readiness"
|
||||
short_description: "Audit structural FEM release readiness"
|
||||
default_prompt: "Use $fem-release-readiness to audit the requested structural FEM feature's release readiness."
|
||||
@@ -1,14 +0,0 @@
|
||||
---
|
||||
name: fem-requirements-baseline
|
||||
description: Define a durable, verifiable structural FEM feature scope and acceptance contract when one is needed.
|
||||
---
|
||||
|
||||
# FEM Requirements Baseline
|
||||
|
||||
Turn the assigned request into observable scope, exclusions, assumptions, compatibility boundary, and acceptance intent. Use an existing PRD when it is sufficient; create a separate requirements document or matrix only when the feature needs that separation.
|
||||
|
||||
Write atomic requirements with a measurable acceptance method. State quantities, locations, units, coordinates, and physical behavior where relevant. Preserve user- or standard-defined acceptance; leave formulation choices, implementation, schema design, and numerical tolerance selection to their owners.
|
||||
|
||||
Read [workflow-and-decisions.md](references/workflow-and-decisions.md) only for a material ambiguity or authority question. Return the document path, decisions, verification intent, and unresolved critical choice. Do not invent physics, compatibility, or acceptance promises.
|
||||
|
||||
Use [evidence notes](references/evidence-and-handoff.md) when a separate durable evidence record is needed.
|
||||
@@ -1,4 +0,0 @@
|
||||
interface:
|
||||
display_name: "FEM Requirements Baseline"
|
||||
short_description: "Baseline verifiable structural FEM requirements"
|
||||
default_prompt: "Use $fem-requirements-baseline to define verifiable requirements for a structural FEM solver feature."
|
||||
@@ -1,5 +0,0 @@
|
||||
# Evidence Notes
|
||||
|
||||
Use this reference only when a task needs a durable evidence record. Record the feature/document path, decisive facts and assumptions, relevant commands with exit codes, comparison quantities and tolerance source when applicable, and residual risks. Keep source facts, calculations, inferences, and decisions distinct. A required failed or unrun check is not a pass.
|
||||
|
||||
Return a concise result containing changed paths, evidence, and blockers; no common handoff envelope, workflow state, retry key, or coordinator inventory is required. Do not use repeated failure to justify changing requirements, formulations, schemas, reference artifacts, or tolerances.
|
||||
@@ -1,33 +0,0 @@
|
||||
# Workflow and Decision Authority
|
||||
|
||||
## Authority order
|
||||
|
||||
Use the first applicable authority:
|
||||
|
||||
1. Approved feature contract and explicit user decisions
|
||||
2. Governing physics, mathematics, standards, and safety obligations
|
||||
3. Official documentation and verification cases for a project-selected reference product or format
|
||||
4. Repository architecture decisions, configuration, and established conventions
|
||||
5. The simplest deterministic choice that preserves the authorities above
|
||||
|
||||
A commercial solver is a behavioral reference only when the project contract selects it. Its public input semantics, output definitions, documented procedures, and verification examples may support decisions; never infer undocumented internals or claim implementation equivalence.
|
||||
|
||||
## Autonomous decisions
|
||||
|
||||
Proceed without user review for reversible choices within approved contracts: internal naming and data layout, test organization, diagnostics, equivalent implementation mechanics, documentation formatting, and correction of clear build or test defects. Record assumptions that affect interpretation.
|
||||
|
||||
## User decisions
|
||||
|
||||
Ask the user only for a choice that changes at least one of:
|
||||
|
||||
- supported physics, formulation meaning, or analysis scope;
|
||||
- public compatibility or an authoritative I/O schema;
|
||||
- acceptance choices where reasonable criteria split the same evidence between pass and fail and change product acceptance or a public accuracy promise, or where authoritative requirements and reference evidence cannot be reconciled technically;
|
||||
- a material security/trust-boundary or credential-handling change, or acceptance of an unresolved security, legal, licensing, or compliance risk;
|
||||
- external reference-solver execution, destructive history changes, publication, deployment, or release.
|
||||
|
||||
Everything else follows the authority order. Lack of a preference is not a blocker when a deterministic in-contract choice exists.
|
||||
|
||||
## Responsibilities
|
||||
|
||||
Requirements own acceptance intent; research owns evidence; formulation owns mathematics; numerical review owns independent numerical findings and verification coverage; I/O owns mappings; implementation owns code and tests; and physics review owns plausibility findings. Use only the expertise needed by the task. Do not silently rewrite another owner's contract to make downstream work pass.
|
||||
@@ -1,12 +0,0 @@
|
||||
---
|
||||
name: fem-research-evidence
|
||||
description: Gather source-backed FEM theory, benchmark, or observable reference-convention evidence for a concrete solver decision.
|
||||
---
|
||||
|
||||
# FEM Research Evidence
|
||||
|
||||
Answer only the research questions needed by the assigned decision. Prefer standards, primary literature, authoritative textbooks, official verification guides, and public vendor documentation. Separate sourced fact, calculation, inference, and remaining gap; record stable locators and applicability limits.
|
||||
|
||||
Identify useful analytical, invariant, patch, convergence, manufactured, or published benchmark cases without treating a single solver comparison as proof. Abaqus material supports only documented observable syntax, semantics, outputs, and verification conventions, never its private internals. Use `fem-theory-query` only when the configured vault is the requested source.
|
||||
|
||||
Return concise evidence, candidate verification cases, and gaps. Do not finalize formulations, tolerances, schemas, code, or reference artifacts.
|
||||
@@ -1,4 +0,0 @@
|
||||
interface:
|
||||
display_name: "FEM Research Evidence"
|
||||
short_description: "Collect structural FEM research evidence"
|
||||
default_prompt: "Use $fem-research-evidence to build a source-backed evidence brief for a structural FEM feature."
|
||||
Reference in New Issue
Block a user