What a receipt is, what a bundle promises.
The design principles under BLKBXS. Short and opinionated. Read this before you argue with our defaults.
Receipts, not reassurance.
A receipt binds model, policy, controls, human review, signer, and outcome. It survives audit because it can be recomputed. Marketing copy cannot.
The bundle is the buyer's artifact.
Bank reviewers do not read dashboards. They read packets. The bundle is the shape BLKBXS commits to. Everything else is optional.
Portability beats platform.
Receipts are verifiable without BLKBXS. Bundles are readable without BLKBXS. The developer keeps their keys, their signatures, and their exit.
Not a governance stack.
BLKBXS does not replace evals, tracing, guardrails, or model-risk management. It consumes their outputs and emits standardized evidence.
Price the pain.
The SDK is free because generating receipts should be free. Bundles cost money because moving evidence out of your building is where value transfers.