Skip to content

Acceptance without product dependence

Public documentation is the source of truth. Project-authored synthetic decks pin behavior in the repository. A locally licensed MAPDL installation may be used once to confirm that a synthetic deck is accepted, but its output is not a fixture, oracle, formulation source, or shipped artifact.

Authorized private files are handled differently:

  • no file, path, title, identifier, hash, fragment, or derived fixture is kept;
  • only a non-identifying aggregate release-gate outcome is retained; private sizes, counts, topology, timing, and result values are not published;
  • a private observation may motivate a synthetic edge case, but the regression is re-authored from public format rules; and
  • solver answers are never used to infer an element formulation.

An executable acceptance deck must strictly parse, survive deterministic write/read, translate through OmniSolver's public model API, and return finite results from the declared interoperability route. Destination projections are documented, warning-producing, and separately disableable; they never alter the neutral source or writer output. A model-only CDB has no load case to solve; its gate ends at strict round-trip and public-model validation rather than inventing physics.

See the repository's ACCEPTANCE.md for the dated release record and ACCEPTANCE_TESTING.md for the governing test policy.