Skip to content

What may happen before a disputed term is resolved?

The controller can request more evidence, refuse, route the dispute, execute provisionally under a declared reserve, or finalize only when the stated conditions pass.

Problem being tested

Some actions cannot wait for every semantic dispute to disappear. The controller keeps the disputed meaning, authority, stated completeness assumptions, reserve, evidence, and recourse separate so provisional execution cannot masquerade as finality.

Controller boundary

The profile evaluates a ConsequenceProfile, an independently recomputable worst-case AmbiguityReserve, a stated completeness warrant, and distinct operative, refinement, and supersession authorities. It returns FINALIZE, EXECUTE_PROVISIONALLY, REQUEST_EVIDENCE, ROUTE, REFUSE, or TERM_STALE. Conflict and non-unique choice are typed route causes, not silent state mutations.

Run the procurement shadow

$ cd bulla
$ PYTHONPATH=src python examples/semantic-settlement/demo.py
$ python -I scripts/verify_semantic_finality.py \
    bench/invention/semantic-settlement/reproduction-vectors/procurement-provisional.internal.json

The demo distinguishes dispatch from custody transfer, locks a simulated reserve, executes provisionally, admits carrier evidence, releases reserve, finalizes, and makes an old term stale after a new epoch.

What verification establishes

  • the finality decision binds the exact epoch, completeness warrant, authority regime, policy, and consequence profile;
  • reserve equals the declared worst-case represented loss plus explicit model-risk buffer;
  • refinement within one model cannot increase the represented reserve;
  • conflict, staleness, and impermissible finalization do not mutate operative state;
  • finality blockers and sufficient repair routes replay independently.

What the supplied evidence supports

Availability: experimental code ships in Bulla 0.44.1 under bulla.experimental; it is not part of the stable API. Evidence: team-authored state machines and Golden cases under bounded finite models and stated completeness assumptions. The escrow adapter is simulated. The profile does not establish real custody, collectibility, legal authorization, actuarial pricing, portfolio netting, or production settlement.

See Golden Gate for the state-space and abstention evidence boundary.