bijux-vex 0.2.2

Vector execution runtime with replayable determinism and audited ANN (nothing implicit).

bijux-vex — explicit vector execution

What it is
Bijux‑Vex is a vector execution runtime with replayable determinism and audited ND (ANN).

Why it exists
Production vector search drifts quietly. Bijux‑Vex makes correctness explicit and refuses when guarantees cannot be met.

Anti‑goals
Not a vector DB. Not a RAG framework. Not a hosted service. No implicit “best‑effort” correctness.

Quickstart (deterministic)

python -m bijux_vex.boundaries.cli.app ingest --doc "hello" --vector "[0,1,0]" --vector-store memory
python -m bijux_vex.boundaries.cli.app materialize --execution-contract deterministic --vector-store memory
python -m bijux_vex.boundaries.cli.app execute --vector "[0,1,0]" \
  --execution-contract deterministic \
  --execution-intent exact_validation \
  --vector-store memory

Start Here

• Start here (10 minutes): https://bijux.github.io/bijux-vex/user/start_here_10_minutes/
• Start here (human): https://bijux.github.io/bijux-vex/user/start_here_human/
• Start here (canonical doc): docs/user/start_here.md
• Why Bijux‑Vex exists: https://bijux.github.io/bijux-vex/user/why_bijux_vex_exists/
• Docs home: https://bijux.github.io/bijux-vex/

Production readiness (explicit)

• Determinism enforced and replayable
• ND is bounded and audited
• CI gates required before release

Project values

• Correctness over convenience
• Explicit over implicit
• Honest failure over silent success