Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

Contributing to SEAL Certifications

SEAL/InitiativeCertificationsSFC

Authored by:

Isaac Patka
Isaac Patka
SEAL | Shield3

Like the rest of Frameworks, SEAL Certifications is open-source and welcomes community contributions. Because the certification carries more weight than general docs, changes go through a more stringent review, and final decisions are made by the SEAL Certifications initiative lead.

This repository is the source of truth for all certification controls. The controls for each certification category (Multisig Ops, Treasury Ops, Incident Response, and so on) live in the cert: block at the top of its page, for example sfc-multisig-ops.mdx. To change what the certification requires, change it here.

What You Can Contribute

  • Improve a control: clarify wording, or fix and refine baselines.
  • Add a control to an existing certification category.
  • Propose a new certification category: open an issue first (see below) so we can discuss scope before it's built out.

The section structure within each certification category is fixed; new controls are added within the existing sections.

How to Contribute

  • Submit a pull request to this repo. See the general Contributing guide for setup, branching, commit signing, and attribution.
  • For larger ideas (a new certification category, or restructuring), open an issue with the certifications tag first so we can align before any code is written.

Feedback from auditors running real engagements is especially valuable. If a control or baseline doesn't hold up in practice, please tell us; a PR is even better.

Reach out directly through:

Versioning and Releases

  • Each certification category page carries a version in its header.
  • Control IDs (such as ms-2.1.2) are kept stable across revisions wherever possible. When a control is renumbered, it's called out in the changelog so anyone tracking controls can re-map cleanly.
  • Changes are batched into periodic named releases and recorded in the changelog, which summarizes what changed, when, and why.
  • Releases are named after seal species, advancing alphabetically (Baikal, Bearded, Crabeater, Elephant, and so on), so a given state of the framework can be referred to by name as well as by version.