bijux-canon-index 0.3.0

Deterministic vector execution, replayable ANN, and provenance-aware indexing for the bijux-canon package family from Bijux.

bijux-canon-index

bijux-canon-index is the vector execution package in bijux-canon. It does more than "run a nearest-neighbor query." It executes a declared vector operation against a concrete backend, records enough provenance to explain the result later, and supports replay-oriented comparison when determinism matters.

If you need to understand vector-store adapters, embedding execution, capability profiles, replay semantics, or provenance-aware result comparison, start here. If you need document preparation, runtime governance, or repository tooling, you are outside this package's boundary.

Legacy continuity

• compatibility package: bijux-vex
• legacy import root: bijux_vex
• legacy command: bijux-vex
• canonical migration guide: https://bijux.io/bijux-canon/compat-packages/migration-guidance/
• retired repository target: https://github.com/bijux/bijux-vex

What this package owns

• vector execution semantics and backend orchestration
• provenance-aware result artifacts and replay-oriented comparison
• plugin-backed vector store, embedding, and runner integration
• package-local HTTP behavior and related schemas

What this package does not own

• document ingestion and normalization
• runtime-wide authority, persistence, or replay policy
• repository maintenance automation

Source map

• src/bijux_canon_index/core for stable primitives and errors
• src/bijux_canon_index/domain for execution and provenance semantics
• src/bijux_canon_index/application for package workflows
• src/bijux_canon_index/infra for backends, adapters, and plugins
• src/bijux_canon_index/interfaces and src/bijux_canon_index/api for boundaries
• plugins for plugin development support
• tests for conformance and replay protection

Read this next

• Package guide
• Architecture
• Public API
• Mental model
• Failure semantics
• Changelog

Primary entrypoint

• console script: bijux-canon-index

Changelog

All notable changes to bijux-canon-index are documented here.

Historical release entries below preserve the wording that shipped with the tagged release, including legacy distribution naming where applicable.

0.3.0 - 2026-04-05

Added

• Package-local and spec documentation now explain the package mental model, failure semantics, vector-store profiles, and freeze criteria in clearer human-facing language.

Changed

• The package was realigned under the canonical bijux-canon-index identity, including namespace, application, interface, and orchestration surfaces.
• CLI workflows were split into clearer command groups for execution, ingest, query, validation, maintenance, and workspace tasks.
• API routes, request schemas, and orchestration helpers were decomposed into narrower modules for query, mutation, read, capability, and artifact workflows.
• Backend and orchestration support code was separated into smaller helpers for embedding preparation, ingest persistence, capability reporting, execution tracking, non-deterministic guard state, and artifact materialization.
• PyPI metadata, search keywords, and project URLs now make the canonical index package easier to discover from package indexes and Bijux-owned docs.
• The package README now uses PyPI-safe badge and link targets, and it points legacy bijux-vex users to the canonical migration path and retired repository guidance.
• Package-local PyPI publication guidance is now checked in and shipped with the source distribution so index release expectations stay attached to the package.
• Build-time version metadata now writes to a generated module so packaging commands stop dirtying the tracked source tree.
• Package-local ignore rules now cover Python package metadata directories so unpacked release artifacts stay cleaner during local validation.
• OpenAPI freeze artifacts and release-gate expectations were refreshed to match the current FastAPI-generated validation schema and 422 response wording.

Fixed

• CLI help and freeze-spec coverage were restored after the package reorganization.
• Runtime state and generated artifacts were moved under the artifacts root so package trees stay cleaner during checks.
• Source distributions now include the full src/bijux_canon_index tree instead of publishing only the typed marker file.
• Release artifacts now ship the repository LICENSE file so downstream consumers receive the license text with the published package.
• The checked-in YAML and JSON OpenAPI artifacts are back in sync so repository-level API contract checks validate the same v1 surface.
• The checked-in v1 schema now includes the current FastAPI validation error shape so API drift checks match the live application contract.

0.2.0 – 2026-02-03

Added

• Explicit vector store adapters (memory/sqlite, FAISS, Qdrant) with capability reporting and status commands.
• Non‑Deterministic (ND) execution model with budgets, quality metrics, witness options, and provenance audit fields.
• Embedding provider interface, cache controls, and embedding provenance metadata.
• Determinism fingerprints, replay gates, and conformance tests for stability.
• Benchmarks, dataset generator, and baseline regression checks.
• Human‑first documentation, contracts, and operational guides (trust model, safety, failure modes).

Changed

• CLI and API now require explicit vector store selection for persistence/ANN routes.
• Refusal semantics are standardized and surfaced consistently across CLI/API/provenance.
• Docs and onboarding flow rewritten for clarity, with explicit anti‑goals and guarantees.

Fixed

• Deterministic ordering rules and replay checks hardened across backends.
• Redaction rules tightened to prevent credential leakage in logs and provenance.

0.1.0 – first public release

• First public, contract-complete release of bijux-vex.
• Deterministic execution with replayable artifacts and provenance.
• Non-deterministic execution via ANN with approximation reports and randomness audit.
• CLI and FastAPI v1 surfaces frozen; OpenAPI schema versioned.
• Provenance, determinism, and execution ABI enforced via conformance tests.