BLOGE Verify

Preview in BLOGE 0.9.8-RC1. bloge-verification executes customer business scenarios against the real BLOGE graph and customer OperatorRegistry. It is a verification foundation, not a production certification service.

BLOGE Verify turns a business-approved example into a repeatable check. A Scenario states the input and expected business facts, a Policy states the minimum acceptable assurance, and Fixture rules control declared external effects. The verifier then executes the same real graph used by the application and emits a verdict, report, and—when configured—sealed evidence.

OBSERVE & VERIFY · EVIDENCE PATHThe real execution emits events, traces, and contract evidence.

Scenario, Policy, and Fixture control the run; the verifier reads its actual outputs instead of simulating another graph.

Verification input

Scenario + Policy + Fixture

Reviewable output

PASS · report · SOURCE_BOUND evidence

EMITTINGLoad customercustomerId → customer

EMITTINGLoad inventoryproductIds → stock

WAITINGCalculate pricecustomer + stock → total

WAITINGCheck creditcustomer + total → approved

WAITINGCreate orderapproved order → orderId

NOT TAKENManual reviewfallback case → reviewId

approved = true otherwise

Loading interactive Graph…

Now running: Load customer + Load inventoryverdict follows observed results

Choose a path

You need to	Start here
Run the loan-approval example or add the test dependency	Getting started
Select the right Java entry point	API reference
Understand what a result can support	Capability matrix
Read or validate a sealed artifact	Evidence versions
Diagnose a non-PASS result	Error reference
Design Scenario, Policy, Fixture, durable, or governance inputs	User guide

Read the result on three independent axes

Axis	Values	Question answered
VerificationStatus	PASS, FAIL, INVALID, INCOMPLETE	Did this declared business contract complete and match?
EvidenceTrust	UNVERIFIED, LOCAL_INTEGRITY, SOURCE_BOUND, ATTESTED	How strongly is the artifact bound to its source and signer?
ClaimCapability	AUTHORING, TEAM_GATE, GOVERNED_GATE, RELEASE_QUALIFIED	Which decision gate has enough independently verified evidence?

A FAIL result can still be strongly source-bound. A PASS result does not automatically become RELEASE_QUALIFIED. Keep verdict, artifact trust, and decision authority separate.

Status first, reason code second

Status	Meaning	Default next action
PASS	Execution completed and declared expectations passed	Check ClaimCapability before using it as a gate
FAIL	Execution completed and a business or policy obligation failed	Inspect the first failed expectation or counterexample
INVALID	The input or capability combination is not valid	Fix configuration; repeating the same run is not useful
INCOMPLETE	The verifier could not finish the required evidence	Inspect resources, timeouts, isolation, persistence, or publication

What it proves—and what it does not

BLOGE Verify can show that the captured graph, operators, contracts, controls, and evidence agree for the declared cases and the frozen source boundary. It does not prove every production input, undeclared external behavior, ambient environment dependency, or business policy not represented by the Scenario and governance inputs.

The customer business owner remains the source of approved outcomes. BLOGE supplies controlled execution, evidence integrity, source binding, and claim assessment beneath that decision.