Skip to content

Releases: SkyOneBranch/cba-kb-engine

Release list

CBA-KB v2.0.4-2

Choose a tag to compare

@SkyOneBranch SkyOneBranch released this 17 Oct 07:20
74f8987

CBA-KB v2.0.4-2 Engine Release

1. Release Identity

  • Release Tag: v2.0.4-2
  • Target Commit: 74f8987934423a56c50c7e734528b03bdb75e7ec
  • Source Package Version: 2.0.2 (in pyproject.toml / src/cba_kb/__init__.py; package version alignment tracked under release lifecycle)
  • Dependency Lock SHA-256: 9dfa4d8f3110ec5192053aa0083c85eb6b0a4b085001ad9e7673282a86cc0d94 (requirements.lock)

2. Functional Capabilities Delivered

  • Dual-Backend Support (F1, F2): Local filesystem and Google Drive integration, Changes API polling, durable checkpoint tracking.
  • Evidence & Identity Separation (F3, F4): Strict separation of Source, Document, Statement, Claim, and Fact. WAL journaled state machine with transaction crash recovery.
  • Rights-Aware Search (F5): Visibility-gated search engine; unverified or restricted content fails closed and is quarantined from public results.
  • Guarded Plans & Safety (F6, R5): Deterministic move/retain planning with parent set verification and PlacementGuard enforcement.
  • Observability & Multi-Backend Metrics (F7, R1–R4, R7): Standardized 11-column inventory, orthogonal lifecycle states, independent metrics for processing rate, archive rate, and query rate.
  • E2E Golden Paths (F8, A1–A6, AC01–AC08, GAT01–GAT08): 10 synthetic test sample categories, automated idempotence, clean-room smoke pass.

3. Release & Operational Boundary Notice

  • Engine Release vs Data Production: This GitHub Release publishes the open-source CBA-KB Engine. Historical production data releases remain preserved at their respective canonical baseline (v2.0.1-1).
  • Production Deployment Status: Target host execution operates under restricted read-only discovery and polling; no unauthorized production data modifications or batch re-classifications are performed.
  • Final Acceptance: Repository maintenance items (CODEOWNERS comments, Issue lifecycle, documentation alignment) and final Consumer Acceptance are being finalized through standard governance.