Evidence object · EV-0241
Privileged-access review
- Authority
- Pinned requirement and source version
- Integrity
- Version, checksum, and custody events
- Use
- Control mappings and freshness policy
- Decision
- Review state, reason code, and release eligibility
Five role views · swipe to explore
One evidence spine · role-specific authority
The operating model between the team being audited and the firm auditing it.
ControlFrame is designed for both sides of assurance. In an activated engagement, internal teams prepare and maintain source-bound evidence while a scoped independent assessor can challenge, re-perform, and conclude against the same governed objects. The record stays connected. The authority does not blur.
Choose the operating view
The same record should answer a different job for every role.
Each view below follows a role through real public product references while naming the boundary between implemented workflow and configured activation.
Prepare and maintain
Compliance teams
Turn obligations into evidence contracts, keep artifacts current, route gaps, and prepare a package candidate before fieldwork becomes an emergency.
Follow the compliance laneChallenge and conclude
Audit and advisory firms
Bring versioned methods into fieldwork, inspect the original source record, re-perform the declared procedure, and preserve reason-coded human judgment.
Follow the assessor laneSee and govern
Executives and boards
Separate defensible claims from incomplete work, see what is waiting on a person, and inspect the operating boundary behind the posture summary.
Follow the executive laneConnect and control
Security and platform operators
Keep source credentials and collection inside an approved boundary while the control plane receives governed jobs, artifacts, and explicit failure states.
Follow the operator laneDistinct public product references
Choose the surface that answers the question being tested.
These are existing, labeled synthetic references for different capabilities. They do not share browser state and should not be read as one continuous tenant run. No customer evidence, activated private runner, audit opinion, or certification is represented.
- 01
Agent boundary
Declare the agent mission
Inspect the roles, plans, tool boundaries, and human release gate before execution.
Inspect reference - 02
Collection trace
Trace a governed run
Replay a labeled synthetic collection from declared target through captured artifact.
Inspect reference - 03
Assessor interaction
Work the evidence
Open the browser-local assessor reference and record reason-coded human decisions.
Inspect reference - 04
Package model
Inspect package eligibility
See how accepted evidence, custody, mappings, and reviewer gates become a release candidate.
Inspect reference - 05
Offline verification
Re-check outside the portal
Re-derive covered hashes and inspect key provenance without relying on a ControlFrame session.
Inspect reference
Bring both sides to the walkthrough.
In a role-based walkthrough, we will anchor the discussion to one declared evidence lane and distinguish the internal owner’s work, independent challenge, named human decisions, release controls, and portable verification.