Repository navigation
CBA-KB v2.1.3 Engine Release
CBA-KB Engine v2.1.3 — Engine-only Release
Scope: Engine code only. This Release publishes the v2.1.3 local Engine code. It does NOT authorize formal data release, Identity release, E4a, E-1, Production, formal Consumer acceptance (5/5), full version closure, formal current changes, or any real Drive write. REQ-212 leftover obligations remain independently tracked under #235/#237. Production current was not switched.
Release identity
- Tag:
v2.1.3(annotated,a7a63601…), target commitbe172d49d2b23a7be4a0c858315480b3e101cc9e(PR #243 merge commit; parents: main85b17891…+ PR head2751914e…). - Git tree:
7a6f94f320a66edebd19c2b5fd327ae4c5f9708a. - PR chain: #240 (v1 baseline) → #241 (v2 Sandbox) → #242 (Step 2 card-posture fix) → #243 (
kc_consume.pyscope-shadowing fix, Human Approve & Merge, 6/6 remote CI green). - Frozen spec SHA-256
269181c7…6cb62; protocol86d9a0b9…3000; acceptance testcd7c303c…f1f8; scoring code60ae461a…. - Package version vs Tag (independent naming, v2.1.0/v2.1.1 precedent): the source package version is
2.0.2(pyproject.tomlandsrc/cba_kb/__init__.pyagree; untouched by this Release). Tagv2.1.3is the Engine Release version identifier.
Delivered Engine functions (local code behavior)
kc_consume.pyscope-shadowing fix (PR #243):consume_answer()no longer overwrites the query scopeWHOLE_SEASONwith the guarantee's field list; the research card's Statistical Evidence now rendersCLEAN_OFFICIAL / 20.1on the real projection path (card SHA-256c07ad35f…, Snapshot digestafa5b444…).- 9-file formal projection verified (
verify_local_projection()valid, manifest digestf0e32a77…). - Oracle v3 frozen (
req213-p03-hexining-v3, manifest2907c633…) and the final real Consumer round run (GPT-6 Medium, 2026-11-12): formal 3/5 PASS; the two formal FAILs are non-code residuals recorded as-is in the post-launch observation list (see Issue #239 receipt).
Honest boundaries
- Formal AC-213-P0-3: 3/5 PASS (raw scorer output, never rewritten). This Release does NOT claim a formal 5/5 PASS.
- The two formal FAILs (CUTOFF locator routing; IDENTITY scope token vs the 4-file evidence) are recorded as-is and marked
ACCEPTED_FOR_POST_LAUNCH_OBSERVATIONunder the Human closeout criteria (2026-11-12); no code was changed to pass them. - Production
currentwas not switched; no real Drive write was made by this Release. - REQ-212 leftover obligations remain independently tracked under #235/#237; this Release does not close or repackage them.