EXECUTED LOCAL TRIAL
From a failed API
to a verified repair.
A teammate starts an approved task. A local model proposes a correction, isolated tests check it, separate reviewers challenge it, and Verdock applies the permitted change and verifies the result. Below are recorded results from the installed private engine.
Recorded results · Actual local Git, SQLite and disconnected Docker workers, on test business cases. Explore the execution evidence below; shared live integrations are part of private beta development.
A repair that ran through the shared service
A refund API returned the wrong result. Under a standing permission limited to one function, Verdock generated a candidate using a local model, tested it in a disconnected worker, scanned it, requested three separate reviews, rehearsed the change and updated a local Git branch atomically.
| Step | Observed result | Why it matters |
|---|---|---|
| Model proposes the correction | 1 candidate, 1 model call | Only the approved function body could change. |
| Approved tests run in isolation | 3 passing tests on the candidate | The defective baseline failed 2 of the same 3 tests. |
| Separate reviewers challenge the change | 3 reviews; 2 required | The controller still enforces scope independently. |
| Apply and verify | 1 branch update; all 3 final checks matched | Unrelated Git content stayed unchanged. |
| Replay the same approved request | 0 additional branch updates | Completion did not depend on repeating the change. |
| Process exits immediately before the Git update | Restart completed and verified; 1 total update | The reserved attempt stayed within the approved retry budget. |
| Process exits immediately after the Git update | Restart verified completion; 1 total update | The already committed change was not repeated. |
| Ask for another human approval during execution | 0 pauses | The original permission covered this bounded recovery. |
This is a recorded local 0.1.9 trial, not a production deployment or a promise to repair arbitrary code. Reviewers in this trial were separate deterministic Docker programs. A separate model-backed offboarding trial also passed with two actual inference calls and three verified record changes.
Organization sign-in was tested against actual local Keycloak over verified HTTPS, including callback replay refusal and identity revocation. Customer identity providers still need configuration.
Read the repair, model and sign-in evidenceOne result your whole team can use
Creators, product, support, operations and engineering can read the same outcome and reasoning. Private workspace members can follow progress, add notes and hand off ownership. Their assigned permissions remain in force in every view.
Another executed case: remove employee access
- ScopeApproved target, actions, expiry and incident allowance.
- Plan and challengeSeparate roles. The controller independently checks authority.
- Rehearse and applySeparate rehearsal storage. Atomic checks before writes.
- VerifyCheck business state and the unchanged control record.
What happened
Select a result to see why it passed or stopped.
| Situation | Result | Record changes | Explanation |
|---|
What this establishes
The permitted sample completed without an approval pause during execution. Replaying its event caused no additional changes. A new permitted incident was corrected, and an exhausted standing allowance was refused.
Evaluation criteria
Measure integration effort, supervision time, total cost and recovery performance across the agreed operations. Match each result to its tested scope and execution environment.
Roles in this trial were deterministic programs. Model-backed decisions are experimental and face the same independent checks.
Shared work, through the same execution engine
The installed 0.1.9 trial used separate authenticated engineer, teammate and viewer clients. An engineer handed off a paused task; the teammate resumed the same approved work. Team notes never became agent instructions.
| Situation | Observed result | Record changes |
|---|---|---|
| Viewer tries to start work | Refused | 0 |
| Engineer pauses before business changes | Paused | 0 |
| Teammate resumes after handoff | Completed and verified | 4 |
| Same event delivered again | Reverified without extra changes | 0 |
| New permitted access incident | Recovered and verified | 1 |
| Revoked viewer tries to reconnect | Refused | 0 |
Recorded shared-service results · Actual SQLite transactions and isolated Docker roles. The test driver synchronized one pause.
Read the shared-workspace evidenceExplore private team operations
Choose local or connected execution. Define the agents, permissions, systems and recurring work, then measure total effort against your current process.
Prepare a private trial