Proof-bearing remote operations
Prove criticalremote access.
Identified. Authorized. Evidenced.
VaultDesk turns high-risk remote access into a governed action record: who crossed in, what they were allowed to do, who could stop it, what changed, and what evidence survived after the session.
ActorHuman or AI principal attributed
AuthorityScope granted before control
ReviewReviewer can hold or deny
EvidenceTimeline and receipts attached
Checkpoint 01
Session context / private release
Replay remains in private release
The recorded browser replay is not public yet. Until public release is explicitly cleared, this frame holds the session context and reviewer-held posture in view.
Session principals
Aly Reyes / primary operator
Jo Hart / release reviewer
Field Android 06 / mobile witness
VaultDesk bounded assistant / proposal-only lane
Governed crossing
Treasury payroll workstation
A protected treasury payroll workstation is being patched under live reviewer hold. Remote action is visible, bounded, and attributable before release can move.
Workspace artifact
Recorded web replay remains in private release.
Recorded browser replay remains in private release.
Approvals and collaborators
Aly Reyes
Primary operator · Driving the patch lane
Jo Hart
Release reviewer · Hold is active
Field Android 06
Witness lane · View-only mobile presence
Release held at session open
Witness lane attached
Session sealed
Mutual authentication completed for treasury-payroll-14.demo.int with the reviewer lane already attached.
Witness joined
Field Android 06 joined as a mobile witness and inherits view-only posture.
Release held
Propagation remains reviewer-held until the patch lane and evidence chain are complete.
AI proposal lane
AI posture at mission open
The bounded assistant is present in observation and planning mode only while the reviewer hold is active.
Low-risk visible
- Summarize current patch lane context
- Propose diagnostic sequence
Still reviewer-held
- Execute patch
- Release to tenant
Authority boundary
What this checkpoint actually allows
Observe desktop
Allowed
Diagnostic navigation
Allowed
Patch execution
Held
Release to tenant
Held
Treasury Patch Guardrail keeps consequential authority explicit instead of widening it silently.
Evidence record
What survives after the run
Session seal receipt
Session seal and mutual-auth event for the replay lane.
Operator identity watermark
Operator identity remains attached to the visible session.
Active reviewer hold
Release hold exists before execution authority widens.
Witness presence record
Mobile witness participation remains visible in the same session.
Trust model
Why this replay stays bounded
- Recorded browser replay remains in private release
- Sanitized replay, not a live customer endpoint
- No public actor receives endpoint authority
- Replay media and metadata remain watermarked
- This pack is a public-safe replay export, not a live tenant console.
Law of the system
The replay matters because the same four conditions stayed visible all the way through.
Identity remains attributable, authority stays scoped before control, review can stop release in-session, and evidence survives the crossing after the moment of action.
Attributed principal
Identity stays attached
Human operators and AI agents enter the same governed session with attributable identity, so the system knows who or what is attempting to cross into a protected machine.
Human + AI principalSession attributionProtected target
Scoped authority
Authority is explicit
Control, clipboard, file transfer, and release require scoped grants and can be held or denied before a protected system accepts the action.
Capability grantsDenied inlineEscalation held
Reviewer hold
Review can stop release
Reviewers, witnesses, and release control sit inside the same live session, so consequential action does not outrun approval.
Reviewer postureWitness laneRelease hold
Evidence path
Proof survives the crossing
Timeline, recordings, receipts, and session truth stay attached to the same operation, so evidence outlives the moment of access.
Attached timelineRecording stateExport evidence
Serious handoff
Continue from the public session.
If the session makes the product real, continue into bounded access or step back into the proof and read the control conditions more closely.
Primary next step
Request bounded product access.
Run VaultDesk in an evaluation flow for your environment, with the same governed session model, reviewer posture, and evidence path shown in the public replay.
Control model
Read the proof before deeper review.
The replay shows the posture. The proof page names the control conditions that make the posture admissible: authority, bounded execution, durable evidence, and reviewable release.
- Authority is explicit before action begins.
- Review can stop release before consequence propagates.
- Evidence survives after the live moment ends.