Skip to content

stability.md

Latest commit

 

History

History
98 lines (66 loc) · 6.46 KB

stability.md

File metadata and controls

98 lines (66 loc) · 6.46 KB

Stability and Maturity

Boruna is at version 1.3.0 — third minor release on the 1.x LTS line. This document is explicit about what is stable, what is experimental, and what is planned.

LTS contract for 1.x: see lts.md. The Stable tier below is what becomes LTS-protected at 1.0 GA — the surfaces listed there are the same surfaces the LTS document commits to preserving across the 1.x line. Experimental and Alpha tiers are explicitly NOT LTS-protected and may break in 1.x minor releases.

Current status

Boruna 1.3 is shipped and under long-term-support per lts.md. The core execution engine, distributed-execution stack, four formal versioned specifications (.ax language, bytecode, workflow DAG, evidence bundle), HA coordinator, mTLS, bundle encryption, capability-tagged worker placement, blob GC, migration tooling, and performance baselines are all shipped, tested, and frozen for the 1.x line. All 13 stdlib packages are 1.0-stable as of 1.3.0.

Boruna is appropriate for:

  • Production workloads on the LTS-protected surface (lts.md §B)
  • Evaluation, proof-of-concept, and internal tooling
  • Audit-sensitive AI pipelines

Boruna is not yet certified for:

  • Regulated environments requiring third-party security audit attestation (booking is the Q4 2026 commitment per lts.md; results expected Q2 2027)
  • Workloads exceeding the PERFORMANCE.md budget without your own benchmarking
  • Storage layouts beyond local filesystem (cloud-storage adapters are post-1.0 work)

Stability tiers

Stable (LTS-protected at 1.0 GA — see lts.md §B)

These components are complete, tested, and behave as documented. Every 1.0 program continues to work on every 1.y release:

  • .ax language 1.0 — syntax, type system, pattern matching, records, enums; formal spec at spec/ax-language-1.0.md
  • VM execution — bytecode format, capability enforcement, determinism guarantees
  • Workflow DAG 1.0 — workflow.json format with schema_version: 1, topological execution, step isolation; spec at spec/workflow-dag-1.0.md
  • Evidence bundle 1.0 — hash-chained log + bundle.json manifest with format_version: "1.0", optional AES-256-GCM envelope encryption; spec at spec/evidence-bundle-1.0.md
  • Capability system — the capability set is frozen at 1.0; any additions in 1.x are additive
  • CLI commands — run, compile, workflow validate/run/approve, evidence inspect/verify/gc-blobs/rotate-kek, coordinator serve/wait, worker run, migrate, new, lang check/repair, template list/apply
  • BundleStorage trait and adapters — BundleStorage, StorageRef, StorageError (#[non_exhaustive]), LocalFs, from_uri dispatcher, and the S3/GCS/Azure Blob adapter modules (storage_s3, storage_gcs, storage_azure) are now stable public API
  • Coord/worker HTTP protocol — protocol_version: 1 responses, locked coord.* and evidence.* error_kind taxonomy
  • MCP tool response shapes — protocol_version: 1 carried on every response (success and failure)
  • HA + mTLS surfaces — multi-coord deployments, worker URL failover, X.509 client certs

Experimental (may change in minor versions)

These components work but may change based on usage feedback:

  • Actor system — spawning, message passing, supervision semantics
  • Multi-agent orchestration — boruna-orch binary and its API
  • Package system — boruna-pkg manifest format and registry protocol
  • Standard libraries — all 13 std-* packages are 1.0-stable as of v1.3.0; see docs/stdlib-graduation-tracker.md
  • App templates — template variable names and generated code structure
  • trace2tests — test generation format and minimization behavior
  • Migration tooling — boruna migrate is currently in beta; covered migrators are stable, additional migrators may ship in 1.x

Alpha (expect breaking changes)

These components are available but under active development:

  • --live HTTP handler — real network calls, SSRF policy, response handling
  • Replay verification — semantics of --verify with partial replays
  • Framework app testing — framework test message protocol

Experimental — new in 1.1.0 / 1.3.0

These components shipped in 1.1.0 but may change based on usage feedback in 1.x minors:

  • boruna evidence serve — local web UI for evidence bundle inspection. Requires --features boruna-cli/serve. May change in 1.x based on operator feedback.
  • lex_full() / trivia-in-AST API — lex_full(source) returning tokens with leading_trivia. Foundation for boruna fmt v2. Not yet used by any public tool; shape may change before the formatter ships.

Planned (post-1.1 — see roadmap.md)

These capabilities are on the roadmap but do not yet exist:

  • Rolling-upgrade per-capability version negotiation
  • boruna fmt v2 (comment-preserving formatter using the lex_full() trivia foundation) and boruna run --watch
  • LLM provider registry and model routing
  • Commercial platform features (SSO, RBAC, policy management UI)

What "stable" means

For stable components (LTS-protected at 1.0 GA): a .ax file, workflow.json, or evidence bundle that compiles, validates, or verifies on 1.0 will continue to do so on every 1.y release. Per lts.md: language_version: "1.x", workflow DAG schema_version: 1, and evidence bundle format_version: "1.x" are forward-compat-readable across the entire 1.x line.

For experimental and alpha components: best-effort compatibility, with breakage documented in CHANGELOG ### Changed or ### Deprecated.

Versioning policy

Boruna follows Semantic Versioning:

  • Patch (1.0.x): Bug fixes, security patches, no API changes
  • Minor (1.x.0): New capabilities, experimental components may change, stable components preserved per LTS contract
  • Major (x.0.0): Breaking changes to stable API surface; deprecation announced ≥6 months prior in a minor release; full migration tooling provided

Dependency on nightly Rust

Boruna builds on stable Rust. No nightly features are required. Minimum supported Rust version (MSRV): 1.75.0.

Security

See SECURITY.md for the vulnerability disclosure policy, supported version matrix, and CVSS-based backport SLAs (CRITICAL/HIGH within 7 days of disclosure).