Skip to content

Releases: BaionSyS/baion-vault-method

Release list

v0.2.0 — Vault Lab ships; release and method versions split

v0.2.0 — Vault Lab ships; release and method versions split Latest
Latest

Choose a tag to compare

View all tags
@SaMullinsJr SaMullinsJr released this 16 Jul 22:03
v0.2.0
8bfd8f5
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

The release record catches up with main: Vault Lab v1 is now part of a published release, not just unreleased main.

Vault Lab

A local, deterministic teaching and falsification environment for the BAION Vault Method. Break a fictional vault five specific ways, watch the real checker catch each one, see the exact byte-level repair — then try to beat the checker.

./lab/start.sh          # guided run (15–25 min)
./lab/start.sh --check  # non-interactive verification (what CI runs)
  • Five break/repair cases: missing review, missing reference, candidate byte mismatch, active receipt conflict, review byte mismatch.
  • Four judgment scenarios the checker cannot decide for you.
  • A checker-escape challenge with a public four-class ruling model and a Hall of Catches.
  • Fail-closed: guided mode and --check share one assertion path. Any expectation drift — wrong diagnostic codes, findings on a fixed vault, a substituted checker — exits nonzero and suppresses the final bounded claim. Adversarial regression tests cover the zero-findings-checker and unexpected-code cases.
  • No AI model runs inside the lab. No network. All fixtures fictional. No badge, certification, or score.

Governing specification: BAION_VAULT_LAB_V1_REFINED_BUILD_SPEC v0.3.0 (2026-07-16), SHA-256 2afb782d8607e8db0c795b0b57fe0a42ad8182c266a58124efba0362aee7c143 — cited with its required verbatim statements in lab/README.md.

Version model: release ≠ method

This release names two versions on purpose:

  • Release version 0.2.0 — what ships from this repository (checker, lab, docs).
  • Method version 0.1.0, unchanged — the specification contract vaults declare via method_version. SPEC.md, src/, and schemas/ are byte-identical to v0.1.0 except the SPEC.md status line. The method did not change; a teaching surface was added.

The previous single-string version parity made this release impossible to cut honestly: bumping method_version past the 0.1.x series makes bvm-lint reject its own templates (BVM002). scripts/check_version_parity.py now enforces the two tracks separately, with a regression test for the series-escape case.

Evidence

Boundaries

PASS means the checker found no declared structural violation in fictional fixtures — not that any claim is true, complete, safe, or decision-grade. Structural conformance only; no factual, scientific, legal, security, or safety certification. Reference methodology, not a standard. v0.1.0 remains the preserved record of the first cut.

Assets 2
Loading

BAION Vault Method v0.1.0

BAION Vault Method v0.1.0

Choose a tag to compare

View all tags
@SaMullinsJr SaMullinsJr released this 15 Jul 21:07
v0.1.0
40066d1

First public release of the BAION Vault Method (BVM) — a file-based governance layer for human–AI work where agents do not get to invent state.

Agents may propose state. Receipts establish it.

What ships

  • Normative core specification (SPEC.md) — the 11-point state contract: unknown stays unknown, the governed object outranks its description, receipts precede promotion, reviews bind exact bytes, negative results require a positive control, corrections preserve history.
  • bvm-lint — zero-dependency Python checker (49 stable diagnostic codes) that makes structural conformance a command rather than a feeling. Python 3.11+, stdlib only.
  • Machine-readable schemas and starter templates for evidence, review, promotion, and retraction receipts.
  • A runnable fictional tutorial vault with a complete promotion + correction lifecycle.
  • Four anonymized field reports from real operating catches: a shared partial-source window, a budget-bound null mislabeled as a wall, a differential-attribution correction, and a skipped authoritative search.

Boundaries

Structural conformance only — no factual, scientific, legal, security, or safety certification. Reference methodology, not a standard. Fresh public authorship; not a sanitized export of a private vault (see PUBLICATION_BOUNDARY.md).

Verification

./verify_repo.sh — 58 tests, tutorial probe + positive control, strict lint of the tutorial vault, link/boundary/version/diagnostic/release-surface checks. CI runs the same gate on Python 3.11–3.13.

🤖 Generated with Claude Code

Loading