CONTROLLED DEVELOPMENT TEST / OCTOBER 11, 2026
One approval.
One exact action.
An approval to create one branch should not grant permission to create a different one. This local test checks that boundary, then examines missing approval, revoked access, expiry and a repeated request.
Recorded by Praxenor on October 11, 2026, from 11:12:21 to 11:12:25 AM Eastern. This is a controlled development test of the local Agent Defender integration. It is not a customer outcome or an independent assessment.
THE QUESTION
Does permission stay tied
to the selected task?
Git records changes to a project. A branch is a separate line of work. The test creates a fresh local Git repository with no remote connection and asks a helper to create one named branch from a fixed starting commit.
The trusted local operator selects the exact request, adds a finite delegation and supplies native signed approval. The helper then submits requests through the development integration.
ACTUAL RECORDED RESULTS
Watch the result viewer.
This silent screen recording shows selected results from the completed October 11 test. It records a viewer of the saved results, rather than live execution or a finished product interface. The six cases appear in their recorded order. Playback does not run software or connect to your tools.
Read the recording transcript
The result viewer identifies this as a controlled local test recorded on October 11, 2026. It shows the following cases:
Changed action
A different branch name was requested using approval for the original task. The controller refused the changed scope before dispatch. No branch was created.
Approved exact action
The original branch creation was sent with its exact signed operator approval. The native adapter reported completion and the repository contained one new branch.
Repeated completed action
The same completed request was submitted again. The adapter reconciled its existing journal and repository state. It did not dispatch the creation a second time.
Missing operator approval
A separate request had a valid delegation but no signed operator approval. The native gateway denied it. No branch was created.
Revoked delegation
Another request was prepared and approved, then its delegation was revoked before execution. The local controller refused it. No branch was created.
Expired delegation
The controller clock was advanced to the grant's expiry boundary before execution. The controller refused the expired delegation. No branch was created. This checks the expiry boundary rather than waiting for a long running task.
The final screen reports one new branch, four refused requests and one reconciled repeat. The temporary gateway stopped and the disposable repository was removed.
SIX CASES / ONE LOCAL ACTION
What happened in each case?
| Request | Recorded outcome | Observed change |
|---|---|---|
| Changed action | scope denied | No new branch |
| Approved exact action | completed | One new branch |
| Repeated completed action | reconciled | No new branch |
| Missing operator approval | denied | No new branch |
| Revoked delegation | scope denied | No new branch |
| Expired delegation | scope denied | No new branch |
Scope denied means the local controller refused the request before native dispatch. Denied means the native gateway rejected the request. Reconciled means the adapter checked its existing journal and repository state without repeating the action.
Permission and effect are checked separately. An approval is not treated as proof that work completed. Refused requests are checked against branch state before and after the attempt.
Download the selected test record as JSONThe public record keeps selected case names, decision states, branch references, observed changes and cleanup results. Private paths, operator identity, approval tokens, credentials and raw native receipts are excluded. The screen recording uses only this public selection.
WHAT THIS SUPPORTS
A narrow, inspectable result.
For this exact local action, the recorded checks show that changed scope, missing approval, revoked delegation and expired delegation did not create a branch. Repeating completed work did not cause another dispatch.
This demonstrates one development connection. It does not establish a failure rate, detection accuracy, speed improvement or protection across every application.
Limits that matter
- The controller is trusted local code. Code running as the same user can bypass it. It is not a computer wide security boundary.
- Parent and helper labels are assertions. This test does not verify remote agent identity.
- Revocation stops dispatch that has not begun. Work already started may finish.
- The expiry case advances the controller clock to the boundary. It is not a long duration test.
- The fixture uses short Windows paths and disposable test keys. An initial capture using a deeply nested path returned an uncertain outcome; that environment limitation remains unresolved.
- Google Workspace, Microsoft 365 and Slack were not connected or tested.
No independent product assessment or certification is claimed.
What would your first test need to prove?
Choose one action, define its allowed scope and decide what evidence would show both refusal and completion. Confirm the supported build and setup with Praxenor before a product evaluation.