Evidence
Evidence in Subbasis is execution-grade recordkeeping, not just logging.
What this means
Evidence captures what happened in a governed workflow so teams can review, debug, and prove operational behavior.
Why it matters
Basic logs often record events without business context. Evidence links actions to runtime intent and governance state.
Evidence supports:
- reviewable execution history
- failure analysis and workflow recovery
- audit-ready posture
- technical primitives for regulated environments
How Subbasis handles it
Evidence events can record:
- action
- actor
- policy
- approval
- connector
- outcome
- failure
- retry
- timestamp where relevant
- execution reference
This record layer is tied to workflow execution, not detached telemetry only.
Example scenario
Finance operation prepares a payment request:
- Agent drafts request payload.
- Policy marks operation as approval-required.
- Human approves.
- Connector action executes.
- Runtime writes evidence for each stage, including failure/retry if needed.
Reviewers can reconstruct both decision logic and technical path.
What to configure
- evidence event granularity
- required fields per operation type
- retention/export expectations
- policy linkage requirements
- approval/evidence dependencies
Limits and deployment notes
- Evidence depth, retention windows, and export envelopes can vary by plan/deployment.
- Evidence improves audit-readiness but does not itself claim certification.