01 / Agree the capture boundary
Start with the runtime, version, expected actions, data sensitivity, and questions a reviewer needs answered. Identify what instrumentation can observe and what it cannot before enabling capture.
02 / Connect within a defined scope
The proposed connection flow uses a short-lived setup credential exchanged for a scoped reporting credential, with a self-check before a connection is considered ready. Actual credential formats and installation commands will be provided only as part of a verified pilot.
03 / Receive events without rewriting history
The intended ingestion layer validates records, limits request sizes, and uses idempotency to avoid duplicate history during retries. It should preserve distinct failed and recovered steps, not collapse them into the final result.
04 / Inspect the recorded activity
Read tools, models, services, domains, handoffs, and human interventions in context. View elapsed time alongside activity time. Treat financial states as observed events: a request, approval, attempt, and settlement are different things.
05 / Export and check the artifact
The planned export preserves the source evidence with sufficient format and provenance information for review. Verification would check defined integrity properties; it would not evaluate whether the agent made a good decision.
06 / Request attestation only when needed
Optional certification is a proposed separate workflow for eligible records. It would require explicit selection and a configured independent provider. No artifact is submitted to a certification service by this website.