modify documents

2026-09-05 15:14:21 +09:00
parent 31dac85192
commit 97e4d7a971
79 changed files with 4570 additions and 2787 deletions
@@ -0,0 +1,39 @@
+---
+name: fem-io-contract
+description: Use when an approved structural FEM feature needs external syntax, validation, internal mapping, result schema, or comparison identity contracts.
+---
+
+# FEM I/O Contract
+
+Turn approved requirements, mathematics, and logical verification quantities into deterministic interfaces without changing their meaning.
+
+## Inputs
+
+- Requirements, formulation, numerical review, and reference-model contracts for one `feature_id`
+- Project architecture and configured input, output, and comparison backends
+- Official specifications for any approved compatibility subset
+
+## Workflow
+
+1. Define the supported external syntax and semantics, defaults, ordering, identifiers, units, coordinates, validation, diagnostics, and unsupported behavior.
+2. Map validated input to implementation-neutral model entities while preserving source identity.
+3. Define result schema versioning, analysis step/frame identity, quantities, components, locations, units, coordinates, precision, and deterministic ordering.
+4. Map logical verification quantities to result and reference identities. Specify missing, extra, duplicate, and nonfinite prechecks before tolerance evaluation.
+5. Add parser, schema, round-trip, migration, and comparison contract tests.
+
+Use [workflow and decision authority](../fem-requirements-baseline/references/workflow-and-decisions.md) when a format choice changes public compatibility. Use [evidence and handoff](../fem-requirements-baseline/references/evidence-and-handoff.md) for return data.
+
+## Output
+
+Follow [Feature document management](../../../docs/FEATURE_DOCUMENTATION.md): 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>/io.md` with input scope; grammar/semantic rules; validation matrix; internal mapping; output schema; comparison mapping; compatibility/versioning policy; test obligations; limitations; and handoff.
+
+## Evidence
+
+Trace every public field and mapping to a requirement, formulation quantity, numerical-review identity, or authoritative selected-format specification. Include positive and negative examples only where they disambiguate behavior.
+
+## Boundary
+
+Do not claim full compatibility from a subset, infer undocumented reference-product behavior, alter the formulation, redefine logical acceptance quantities, change tolerances, implement code, modify reference artifacts, or run an external solver. Input syntax, result containers, and tabular comparison formats are project-selected contracts, not mandatory solver identity.
@@ -0,0 +1,4 @@
+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."