Skip to content

Answerable computing for work passed between agents.

Transaction Answerability means retaining the terms, evidence, authority, and recourse for work passed between systems. If a witness later signs an incompatible view, declared reliance paths identify which decisions require another look.

Experimental · source-only · synthetic · project-operated. Repository source contains the reference network; the installed Bulla package does not. The result does not establish complete dependency capture, witness independence, custody, collection, real settlement, or customer activity.

No orphaned consequence. No silent discharge.

Under the Answerability Network profile, a consequence must reference the eligible predicate and the authority that permitted it. When the profile accepts evidence defeat, declared dependents remain marked for recheck or unresolved; they are not silently cleared.

One agent hires two providers.

Both provider receipts name the same digest. Provider A also supplies the bytes required by the buyer’s policy. The browser verifies that record, its witnessed history, and its binding to the named consequence rules.

Retained promise

Task
Exact inference artifact
Price
$125.00
Witness bond
$200.00 fixture allocation
Covered fault
sign no different roots for one log, epoch, and tree size
Maximum remedy
$125.00

Not yet reproduced locally

Before showing a result, the browser checks the verifier bundle against its published closure hash and requires the report to match the frozen Python and Node results.

Local reproduction is not independent verification.

Records ready.

Verify the retained transaction records locally in the browser.

One witness forks. An accepted correction notice marks the declared paths to revisit.

Compare the checkpoint views to load the declared graph.

RecheckA declared path reaches the disputed checkpoint.
SeparateComplete ancestry contains no declared path.
UnresolvedAncestry is incomplete, so no automatic clearance is available.

No verified network stage.

What the fork proves

Two authentic checkpoints from one witness name the same log, epoch, and tree size but different roots. That conflict concerns the witness's signed history. It does not make the provider's result false.

What the bond covers

A pre-agreed covenant covers that objective non-equivocation duty. Its $125 remedy uses only the fixture-reported $200 dedicated allocation. Other witness duties and provider claims follow their own challenge rules.

Reproduce the reports

The public packet carries the standalone Node checker and both sibling verifier kernels at their recorded repository paths. The Python command requires a repository checkout with Bulla’s source dependencies.

PYTHONPATH=bulla/src python3 bulla/spec/answerability-network/check.py bulla/spec/answerability-network/vectors/fork-authorized --context bulla/spec/answerability-network/contexts/fork-authorized.json
node bulla/spec/answerability-network/check.mjs bulla/spec/answerability-network/vectors/fork-authorized --context bulla/spec/answerability-network/contexts/fork-authorized.json