VVADRA
PUBLIC DEMOHandbookRoadmap

Deterministic demo / saved protocol evidence

Confidence is a protocol,
not a feeling.

One control plane. Many models. Many machines. One proof boundary.

Most agent systems optimize the path to completion. VADRA optimizes the path to justified confidence.

Try free — no sign-up Explore the verification protocol
Replay-safe by design

No CLI, Runner, live model, credentials, or protected Linux execution is used by this public demo.

WORKSPACEVADRA Demo Workspace
MACHINEExample Workstation
MODELS USEDNot available
EVENTS50 / 50

MULTI-MACHINE ARCHITECTURE DEMO

One control plane. Many machines. One proof boundary.

Illustrative architecture nodes — not live connections. A real VADRA installation pairs each runner with a one-time code and keeps evidence, policy and approvals centralized.

Architecture demo

Example Workstation

Local runner · illustrative only

Architecture demo

Example GPU Runner

GPU runner · illustrative only

Architecture demo

Example Cloud Runner

Cloud runner · illustrative only

VADRA CONTROL PLANE

↓

Local   ·   GPU runner   ·   Cloud runner

↓

Challenge / repair → Independent re-verify → Proof gate

THE VADRA LOOP

From challenge to justified refusal

01

Challenge

Interrogate the completion claim against bounded criteria.

8 saved events
02

Blind spot found

Required protected-action proof is missing.

8 saved events
03

Bounded repair

One repair round fixes only the proof-producing path.

12 saved events
04

Fresh independent re-verification

A clean context repeats the checks without repair-session state.

14 saved events
05

Evidence-bound decision

Technical completion and action authority are judged separately.

6 saved events
06

Protected action refused

No action occurs because required Astra proof is absent.

2 saved events

FINAL EVIDENCE-BOUND DECISION

Action refused — required proof is missing

external_action_astra_proof_missing
Repair rounds
1
External actions
0
Workflow
Complete
The AI that fixes the problem doesn't get to certify its own fix.
Inspect all 50 saved protocol events Read-only evidence
  1. 01
    Protocol opened

    A bounded release decision was created from public example inputs.

    08:00:00Z
  2. 02
    Workspace pinned

    Workspace identity fixed as VADRA Demo Workspace.

    08:00:01Z
  3. 03
    Machine pinned

    Execution identity fixed as Example Workstation.

    08:00:02Z
  4. 04
    Goal recorded

    Assess whether the example repair is safe to release.

    08:00:03Z
  5. 05
    Constraints recorded

    No network action and no unproved external action.

    08:00:04Z
  6. 06
    Acceptance criteria recorded

    All required evidence must be present and independently checked.

    08:00:05Z
  7. 07
    Initial artifact captured

    Public deterministic artifact digest saved.

    08:00:06Z
  8. 08
    Challenge pass started

    First-pass evidence review entered the ledger.

    08:00:07Z
  9. 09
    Claim inspected

    The completion claim referenced a successful local check.

    08:00:08Z
  10. 10
    Evidence enumerated

    Every evidence reference was resolved against the saved protocol.

    08:00:09Z
  11. 11
    Coverage compared

    Required external-action proof was absent.

    08:00:10Z
  12. 12
    Disagreement opened

    Completion and evidence coverage did not agree.

    08:00:11Z
  13. 13
    Blind spot classified

    Missing proof was classified as release-blocking.

    08:00:12Z
  14. 14
    Scope bounded

    Only the proof-producing path was eligible for repair.

    08:00:13Z
  15. 15
    Action gate closed

    External action remained disabled while evidence was incomplete.

    08:00:14Z
  16. 16
    Finding committed

    Blind spot finding saved before any repair began.

    08:00:15Z
  17. 17
    Repair round opened

    Repair round 1 started from the committed finding.

    08:00:16Z
  18. 18
    Repair boundary checked

    The proposed edit stayed inside the declared example workspace.

    08:00:17Z
  19. 19
    Repair intent recorded

    Add proof collection without widening execution authority.

    08:00:18Z
  20. 20
    Pre-repair digest captured

    The original public artifact digest was retained.

    08:00:19Z
  21. 21
    Bounded change applied

    The deterministic proof collector was updated.

    08:00:20Z
  22. 22
    Unrelated files unchanged

    Saved file-set comparison found no out-of-scope change.

    08:00:21Z
  23. 23
    Repair output captured

    A new example artifact digest was stored.

    08:00:22Z
  24. 24
    Repair check started

    The repaired path was evaluated in the saved harness.

    08:00:23Z
  25. 25
    Repair check passed

    The local deterministic check completed.

    08:00:24Z
  26. 26
    Repair transcript sealed

    The repair record became immutable input to re-verification.

    08:00:25Z
  27. 27
    Repair authority released

    The repair participant no longer held the decision step.

    08:00:26Z
  28. 28
    Fresh verifier requested

    A clean independent verification context was required.

    08:00:27Z
  29. 29
    Fresh context created

    No repair-session state was reused.

    08:00:28Z
  30. 30
    Artifact reloaded

    The verifier loaded the repaired artifact by digest.

    08:00:29Z
  31. 31
    Criteria reloaded

    Original acceptance criteria were independently re-read.

    08:00:30Z
  32. 32
    Constraint check repeated

    Workspace and no-network boundaries still held.

    08:00:31Z
  33. 33
    Change scope recomputed

    Only the bounded proof path had changed.

    08:00:32Z
  34. 34
    Deterministic check repeated

    The saved check passed in the fresh context.

    08:00:33Z
  35. 35
    Finding replayed

    The original blind spot was tested against the repair.

    08:00:34Z
  36. 36
    Blind spot repaired

    The proof collector now emitted the required record shape.

    08:00:35Z
  37. 37
    Evidence freshness checked

    The new evidence was produced after the repair.

    08:00:36Z
  38. 38
    Evidence independence checked

    Repair output and verifier judgment were separate records.

    08:00:37Z
  39. 39
    Completion candidate formed

    Technical repair criteria were satisfied.

    08:00:38Z
  40. 40
    External proof queried

    The protected-action proof set was evaluated separately.

    08:00:39Z
  41. 41
    Required proof absent

    No Astra-signed release proof existed in this saved demo.

    08:00:40Z
  42. 42
    Re-verification sealed

    Fresh verification completed with one remaining gate.

    08:00:41Z
  43. 43
    Evidence bundle assembled

    Challenge, finding, repair, and re-verification records were linked.

    08:00:42Z
  44. 44
    Decision rule evaluated

    Technical completion did not override the protected-action gate.

    08:00:43Z
  45. 45
    Completion recorded

    The bounded repair workflow itself was marked complete.

    08:00:44Z
  46. 46
    Action eligibility evaluated

    Release action remained ineligible without required proof.

    08:00:45Z
  47. 47
    Reason code selected

    external_action_astra_proof_missing

    08:00:46Z
  48. 48
    Decision committed

    Refusal was stored as an evidence-bound outcome.

    08:00:47Z
  49. 49
    External action refused

    The protocol refused to act because required proof was missing.

    08:00:48Z
  50. 50
    Protocol closed

    External actions = 0. The safe refusal is the final outcome.

    08:00:49Z

Developer preview · Live artifact review: PREVIEW — not yet completed in acceptance. See validated scope.

Saved evidence only. This page makes no claim that a live model performed the demonstration.

Local product quick start