Our doctrine is versioned, not static.

The commitment

Quarterly audit cycle. Every 90 days Thabit reviews every standard in this registry against its publishing authority (DLA QuickSearch for MIL-STDs, RTCA for DO-x, FDA for 21 CFR, ISO for ISO-x, NRC for 10 CFR, ASME for NQA-1, and so on). Change Notices, draft revisions, and sanctioned interpretations are incorporated into Thabit's doctrine modules.

Versioned doctrine modules. When a standard revises, Thabit ships a new doctrine module version alongside the old one. Customers running packages against the prior revision continue working; customers migrating to the new revision get an explicit diff showing what would change in their existing packages. Nothing breaks silently.

Revision-aware packages. When a program office generates a package, they select which revision of each standard applies to their contract. Government programs routinely cite cancelled or superseded revisions for continuity; Thabit honors the contract, not the latest release.

Subscriber notifications. Customers configure which standards their programs use. When a revision ships, they get an email with the diff, the migration implications, and the list of their existing packages affected.

Standards currently encoded

Every standard below is indexed in Thabit's doctrine corpus. Click any status badge to read the explanation. The Encoded column shows the date our doctrine module was last audited against the publishing authority.

Status legend

CURRENT

Current revision, publishing authority actively maintaining

CANCELLED / CONTRACTED

Formally cancelled by issuing authority but still contractually required on legacy programs

FROZEN

No longer revised but still in active use; modern successors exist and are also encoded

REVISION IN FLIGHT

Publishing authority has draft revision in circulation; Thabit tracks the draft

HARMONIZING

In transition to a harmonized or merged standard; Thabit encodes both

How we handle the hard cases

Cancelled-but-contracted standards

MIL-STD-973 was cancelled by DoD in September 2000 and officially replaced by EIA-649. Yet DoD contracts still cite MIL-STD-973 for continuity on legacy programs. A capture manager responding to an RFP that references MIL-STD-973 can't tell the government's contracting officer the standard is cancelled; they have to produce compliant artifacts against the cancelled document. Thabit encodes both the cancelled standard and its replacement, and lets customers pick which their contract requires.

Frozen standards (MIL-HDBK-217F)

MIL-HDBK-217F has been frozen since 1995. Its component failure-rate models are three decades old and known to over-predict failures for modern electronics. The DoD community's modern successor is 217Plus, maintained by the Reliability Information Analysis Center. Thabit encodes both. Customers with 217F contractual requirements get 217F; customers modernizing get 217Plus; customers transitioning can run both side-by-side and compare predictions.

Harmonizing standards (FDA QMSR)

The FDA published the Quality Management System Regulation (QMSR) final rule in February 2024, harmonizing 21 CFR 820 with ISO 13485:2016. The transition period ends in February 2026, after which QMSR is the sole regulation. Medical-device manufacturers in mid-flight submissions need both the legacy QSR and the new QMSR encoded. Thabit ships both doctrine modules; the registry clearly marks which applies to which submittal date.

Standards in continuous amendment (FAR)

The Federal Acquisition Regulation amends multiple times per year via Federal Acquisition Circulars. Each FAC is a delta to specific parts of the FAR. Thabit tracks every FAC published during its monthly review cycle and ships doctrine deltas within 30 days of publication.

The commitment, in one sentence

If your program office references a standard on this page, Thabit's doctrine module for that standard is at most 90 days old, the revision history is public, the changelog is traceable, and when the authority publishes a revision we ship the update before you need to ask for it.

Requesting coverage for a standard not yet on this list

Thabit's doctrine corpus grows with customer programs. If your contract references a standard not listed above, email doctrine@thabit.ai with the standard identifier, controlling revision, and the program context. New doctrine modules typically ship within 30 days of first customer request for standards we haven't encoded before.