Waveframe Labs mark
Waveframe Labs
Reference Scenarios

Concrete actions. Deterministic outcomes.

These scenarios are canonical examples for understanding Waveframe's execution-governance boundary. They are not customer case studies; they are reference patterns for evaluating how authority, evidence, and runtime blocking work.

Operational Reference Patterns

Each scenario follows the same structure: proposed mutation, authority check, contract-bound evaluation, and ALLOW/BLOCK outcome.

Finance Transfer Governance

High-value transfer by an unapproved actor

Proposed action: transfer $1.25M from operating reserves to a vendor account.

Evaluation: actor role is intern; contract requires manager approval and finance controller approval.

Result: BLOCKED before execution

CI/CD Deployment Enforcement

Production deployment without release evidence

Proposed action: deploy a production build from an AI-generated change set.

Evaluation: missing test artifact, missing reviewer approval, and unsigned release manifest.

Result: BLOCKED before deployment

Privileged Permission Change

Admin role escalation

Proposed action: grant organization administrator rights to a service account.

Evaluation: actor lacks authority for privileged identity mutation.

Result: BLOCKED before permissions change

Approval Replay Blocking

Old approval reused against a new mutation

Proposed action: execute a modified transfer using an approval from a previous transfer.

Evaluation: approval artifact does not bind to the current mutation hash.

Result: BLOCKED for integrity violation

Multi-Role Approval Flow

Required approvals satisfied

Proposed action: reallocate a budget after manager, controller, and CFO approvals are bound to the proposal.

Evaluation: required roles, artifacts, and contract identity checks pass.

Result: ALLOWED to execute

Contract Mismatch Blocking

Proposal references the wrong authority

Proposed action: run a production mutation with a proposal that declares an outdated contract hash.

Evaluation: proposal contract hash does not match the compiled authority contract.

Result: BLOCKED for contract identity mismatch

What these scenarios have in common

The model can propose. A workflow can request. A service can prepare an action. But the action reaches the production system only after the contract-bound execution boundary returns an allowed decision.

View the public tools that implement the boundary