Skip to main content

Releases and Downloads

BDL documentation and authoring rules are versioned.

Do not treat all BDL-related version numbers as one shared version.

Current documentation baseline​

This documentation is currently aligned primarily with:

ComponentCurrent documentation baseline
BDL Knowledge Baseline5.2.2 ALIGNED
BDL Language Familybarsa.definition.v1
Documentation SiteInitial public reference build

Additional contracts and troubleshooting packs may use their own independent version numbers.

Version dimensions​

BDL uses several version dimensions that must remain distinct:

BDL language version​

Identifies the language or schema contract used by BDL documents.

Example:

{
  "schema": "barsa.definition.v1"
}

Knowledge baseline​

Identifies the documentation and evidence baseline used to describe BDL behavior, artifact structure and authoring rules.

The current primary baseline for this site is:

Barsa_BDL_Master_Knowledge_Pack_v5.2.2_ALIGNED_20260828

Native Barsa contract version​

Native Barsa behavior is governed by its own contract version.

Do not infer Native Contract compatibility from the BDL Knowledge Pack version number.

Runtime and troubleshooting version​

Runtime troubleshooting knowledge can evolve independently from both the language and Native Contract.

Knowledge pack history​

Reference material used during the development of this documentation includes versioned knowledge packs such as:

  • Barsa_BDL_Master_Knowledge_Pack_v5.2.2_ALIGNED_20260828
  • Barsa_BDL_Master_Knowledge_Pack_v5.2_COMPLETE_FINAL_20260828
  • Barsa-BDL-Master-Knowledge-Pack-v3.0-FINAL-RT-AUTHORING-SURFACE-20260816
  • Barsa-BDL-Master-Knowledge-Pack-v2.0-FINAL-20260816

Historical packs are useful for change analysis but should not silently override the active baseline.

Native contracts​

Versioned Native Barsa contracts are maintained independently.

Known contract packages include:

  • BARSA_NATIVE_SYSTEM_DESIGN_CONTRACT_v2.0.0
  • BARSA_NATIVE_SYSTEM_DESIGN_CONTRACT_v1.0.0

When documentation conflicts across baselines, use the explicitly active contract and evidence hierarchy rather than choosing the numerically largest unrelated version.

Troubleshooting knowledge​

Runtime and troubleshooting material is also versioned independently.

Known packages include:

  • Barsa_RT_BDL_Troubleshooting_Knowledge_Pack_v2.0.0_COMPLETE_20260828

Download policy​

Official downloadable packages should be:

  • Versioned
  • Immutable after publication
  • Clearly named
  • Accompanied by release metadata
  • Verifiable with a cryptographic checksum
  • Clearly marked as current or historical

Current versus historical​

The site should clearly distinguish:

  • Current recommended baseline
  • Supported prior baseline
  • Historical archive
  • Experimental or draft material

Historical documentation must not be presented as the current production contract.

Package integrity​

Published downloads should include SHA-256 checksums so users and automated systems can verify that the package has not changed.

Example:

package.zip
package.zip.sha256

Machine-readable releases​

A later release index will expose version metadata in a machine-readable form so AI tools and automation can resolve the active BDL baseline without scraping this page.

Next​

The next documentation task is to publish machine-readable BDL discovery files for AI systems and search engines.