Get Involved

Participate

Register deviations, submit proposals, apply the standard, or review open proposals.

BASICS is designed to be used, tested, and improved by the people building products under real constraints. There are four ways to participate.

Apply the Standard

The most valuable form of participation is implementing BASICS in a real product. The Adoption Playbook is a 30-day track that walks through Core tier conformance step by step.

When you achieve a conformance tier, you can publish your conformance evidence and list your product in the BASICS ecosystem. Contact basics@babb.tel to register.

What you’ll need for Core tier:

  • A published command contract (JSON Schema or equivalent)
  • A published event schema
  • Evidence of local record operations without network
  • A compatibility policy
  • A degraded-mode matrix

Read the Adoption Playbook →

Submit a Proposal

Proposals change, add, or remove rules in the standard. Any party may submit a proposal via GitHub Issues using the proposal template.

A strong proposal includes:

  • The specific rule IDs affected (or new IDs requested)
  • A clear problem statement — what behavior the current standard does not handle
  • A proposed normative statement in the style of the existing rules (“MUST”, “SHOULD”, “MAY”)
  • Known implementation implications and any draft trial results

Proposals move through a 100-day governance cycle from Draft to Ratification. You can track all open proposals in GitHub Issues.

Open a proposal →

Register a Deviation

If your product cannot satisfy a mandatory control, you may register a formal deviation. A registered deviation is a transparent disclosure, not an approval. It keeps the conformance model honest and allows the community to see where the standard needs to flex.

A valid deviation registration includes:

  • The rule ID being deviated (e.g., BASICS-SC-010)
  • A rationale for why the control cannot be satisfied as written
  • A proposed compensating or equivalent control
  • A durable deviation identifier (assigned by Babb: DEV-[YYYY]-[NNN])

Submit a deviation →

Review Open Proposals

Community review is a formal stage in the governance cycle. During the 30-day community review window, all comments are logged and must receive a disposition. You do not need to be implementing BASICS to participate in review.

View open proposals →

Join GitHub Discussions →

Contact

For questions, private deviation registrations, or Industrial tier review requests:

Email: basics@babb.tel
GitHub: babbworks/BASICS-standard