MEGURO Docs
Documentation

Task-oriented technical guidance for practice, evidence, automation, and verification.

Understand the result

Read the current receipt

Interpret the customer hierarchy first, then move into evidence and developer details.

Use this when

Use this for any concluded receipt before sharing it or evaluating it with a Configured Receipt Gate.

Before you start

Treat the receipt as a technical evaluation. Recorded API behavior is automatic whether or not a Configured Receipt Gate exists, and its customer wording comes from the Default run policy. Confirm the store, scenario, seed, declared agent subject, client API target, execution environment, live verification state, and exercised operation scope. Customer-declared build identity is not independently verified by Meguro.

Steps

  1. Read Goal outcome for whether the intended technical task happened.
  2. Read Lane integrity for whether the run stayed inside the declared execution lane.
  3. Read Footprint for calls, accepted and rejected writes, and modeled changes.
  4. Inspect the Decisive moment and Next technical proof.
  5. Use Evidence for reviewable facts and Developer details for protocols and debugging.
  6. Classify claims as Observed, Modeled, or Not established.

Success looks like

You can trace the result to recorded calls and explicitly bounded modeled consequences without upgrading simulation evidence into production proof.

If it fails

If the evidence is partial, identify the missing proof layer: agent contact, representative write, state delta, scenario source, or completion. Do not replace missing evidence with inference.

Next action

Continue to Apply the proof boundaries, or select the store and reopen its Runs tab.