Velaris GroupStrix
← Strix Execution Control

Authority Runtime candidate · XGI-001

Approval for one refund is not authority for a different refund.

The former browser-only state machine has been retired on this branch. This surface now describes the real five-operation runtime contract instead of fabricating execution, signatures, or provider observation in the browser.

Canonical server path

finance.refund.issue

SANDBOX · AUTH REQUIRED
  1. 1evaluate(proposal)

    Derive the refund consequence outside the kernel and submit the existing Strix decision lifecycle.

  2. 2acquireAuthority(decision)

    After ordinary approval/quorum, use the existing decision execute route to mint the single-use authority.

  3. 3execute(request)

    Re-derive the exact binding, atomically redeem through verifyAndRedeemExecutionToken, then enter the registered adapter.

  4. 4observe(executionId)

    Ask a separately configured HTTPS consequence source what state actually exists. The observer never receives Strix’s expected material or expected hash.

  5. 5verify(evidenceId)

    Delegate to the existing verification-contract v2 path for hash recomputation, full chain walk, JWKS key resolution, and Ed25519 verification.

What changed

Execution is no longer represented by local browser replay state. The candidate server boundary reuses Strix’s existing token redemption and Signed Evidence path, while observation and verification are separate read-side operations.

Why this page does not auto-run it

Refund authority is CRITICAL and must still earn ordinary Strix approval/quorum. This public page will not mint demo approval or embed a tenant credential to create a smoother demo. That would be a second authority path.

Open authenticated execution controlInspect proof surfaces

XGI-001 remains unproven until X1-X5 run against preserved evidence. An unconfigured independent observer returns UNKNOWN; it never upgrades an adapter report into a verified consequence.