Calybris Core
Decision infrastructure with replayable proof.
Evaluates catalog, policy and request; returns a deterministic decision, receipt and offline verification evidence.
- For
- Teams building decision infrastructure
- Engine
- Rust · Python
- Source code
- Open · Apache-2.0
- Version
- 1.3.0
- Buying
- Written, fixed-price pilot
What is Calybris Core?
Calybris Core is a deterministic, proof-carrying decision core. From a catalog, a policy and a request it makes a decision with integer arithmetic and writes every decision into a hash-chained write-ahead log (WAL). calybris-verify recomputes and verifies the decision on another machine. It is written in Rust, has Python bindings and is Apache-2.0 licensed.
One decision, from gates to receipt to replay.
- budget ≤ 120
- lead time ≤ 5 days
- risk ceiling ≤ 80%
🔒 Policy and catalog frozen
Visualisation. Digests are SHA-256 values of the inputs shown here, computed in your browser; Calybris' byte layout is defined in SPECIFICATION.md.
How it works
From the product's own documentation. Each number says where and on which version it was measured.
You write the rules
Budget, risk, lead time, region. Catalog and policy are frozen and can be Ed25519-signed.
An integer kernel selects
Every candidate passes hard gates; the best survivor wins. No floats, no unsafe.
Every decision is logged
Policy, input and decision digests go into a hash-chained WAL. Even a truncated tail is detected.
Verified on another machine
calybris-verify recomputes the decision from scratch. Change one record and the numbers stop matching.
- 1.3.0
- Published on crates.io and PyPI. API and formats are stable across 1.x. Source
- ~115 ns
- Per decision. CodSpeed CI, Linux x86_64, 22-candidate synthetic catalog. Source
- 0 unsafe
- #![forbid(unsafe_code)] in the kernel. Budget operations tested with Loom and Miri. Source
- Byte-exact
- Every digest layout is specified, so a second implementation can be checked against it. Source
Stack
- Rust
- Python (PyO3)
- C ABI
- WebAssembly
- SHA-256
- Ed25519
- Apache-2.0
Try it
pip install calybris # Python
cargo install calybris-core # calybris-verify CLI
calybris-verify chain decisions.wal.jsonlWhat it does not claim
It proves the integrity of the trail, not the truth of the inputs. It does not find the best commercial outcome either: it selects by the rules you wrote, and a wrong rule produces a wrong but visible decision.
Current boundary
1.x decision semantics and replay are stable; independent witness and timestamp features remain behind preview flags. Enterprise policy integration is separately scoped.
What a pilot covers
A sample starting scope. Final deliverables and acceptance criteria are fixed in the written proposal.
- Question
- Can the same input reproduce the same decision and proof?
- Likely input
- Alternatives, constraints and sample inputs
- Deliverables
- Example decision flow on the core
- Replay and verification record
- Enterprise policy integration outline
Before you decide
Can I buy this product today?
A paid pilot and setup proposal can be prepared. Scope, data access, deliverables, timeline and a fixed price are agreed in writing after a discovery call.
Why is there no price?
Data volume, integration and success criteria differ from job to job. After the call you get a fixed-price written proposal; no paid work starts without your approval.
Do I need to upload live data here?
No. This site has no file upload or accounts. Data access, retention and permissions are set only in the pilot agreement.
What is the first step?
Choose Calybris Core in the form and describe the problem you need to solve. The data and pilot boundaries are then set together.
More in this discipline
- Vinctum AegisPython · XGBoost · SHAP
From churn risk to an economically grounded retention decision.
- LuceThemisRust · Python
Audits signal quality in quantitative research.
- Churn Report KitPython · XGBoost
Churn analysis with an actionable retention queue.