DAR Backup

DAR backup

dars/ and dars/dars.lock preserve exact OpenCapTable package bytes, hashes, compiler metadata, and deployment history. These immutable artifacts support package verification, reproducibility, and rollback.

The npm package's stable opencaptable.dar export is a consumer artifact. The locked dars/ tree is the release and deployment evidence; the two have different jobs.

Prepare before release

Build and commit the candidate in the reviewed source PR:

npm run backup-dar -- --package <package> --version <version>
npm run verify-dars
npm run check:dar-version-policy

The release workflow does not create or refresh backups. It builds again, requires byte equality with the committed candidate, and fails if release execution mutates dars/.

Successful deployments are recorded by immutable annotated tags such as dar-deploy/devnet/<package>/v<version>. Candidate selection and Mainnet eligibility are enforced by the version-policy scripts, not by examples copied into this page.

Never edit a DAR directly. Change source and version metadata, build, back up, review the lockfile, then use the guarded release path.