- resolver (rules RTC-R0..R4/A1..A3/G1..G2) over the official cClassTrib table 2026-06-22 and LC 214/2025 annexes; local vs official catalog comparison - ONE root-cause RTC blocker per product (missing/unresolved/ambiguous/conflict/official mismatch/catalog outdated/evidence missing) - auto-apply: C000025.CCLASSTRIB only, three switches (FIREBIRD_WRITES + RTC_AUTO_APPLY_ENABLED + Hub authorization), per-product re-read and re-decision, never overwrites, rowcount 1, audit table rtc_write_audits (migration 0027) - copy-only write E2E (280/280 applied, only CCLASSTRIB changed, 2nd run 0 writes, stale decision 0 writes); real databases untouched - docs: cclasstrib_resolution, rtc_auto_apply, unified_fiscal_completeness Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
9 lines
575 B
Python
9 lines
575 B
Python
"""Single source of truth for the release version. Also what the Agent Windows
|
|
package is versioned as (scripts/build_agent_package.py reads release/VERSION,
|
|
kept identical to this) and what an AgentRelease row's `version` column holds
|
|
once published — never a second, independent version number. Fiscal semantics
|
|
are versioned separately (ENGINE_VERSION/DECISION_VERSION in classification.py,
|
|
DECISION_ENGINE_VERSION etc.) and are NOT changed by a release bump."""
|
|
GTI_FISCAL_VERSION = "1.1.9"
|
|
API_COMPAT_MAJOR_MINOR = "1.0" # an Agent 1.0.x/1.1.x talks to any Hub 1.0.x
|