Concept reference

Standards Packs

Author report policy as typed standards packs so docs, help, validation, and report generation never drift.

1 min read

Author against typed report contracts

Standards packs are explanatory in docs, but executable in the product only through typed report-policy fields: sections, checklists, figure overlays, mandatory extracts, signature blocks, and algorithm references. There is no free-form markdown sneaking past review.

Published standards-pack inventory

  • ASME BPV VIII-2 Linear Elastic Review Pack

Standards tighten evidence, never hide it

A standards pack should tighten the evidence contract — require more QoIs, demand a verification series, mandate a signature block — never hide what the report claims. Required artifacts must be inspectable from the same public docs and help surface before an operator edits the pack.

Writing a new pack

  1. Start from an existing pack in packages/skills/standards/ (or open an authoring chat).
  2. Declare typed required sections, checklists, and signature blocks.
  3. Bind mandatory QoIs and figure overlays to the figure catalog.
  4. Cite algorithm references so the report can footnote them automatically.
  5. Sign and publish through the platform's signed-skill registry.

Was this page helpful?

Edit this page on GitHub

Search docs

Find pages across the SimPilot docs.