RBEK Python SDK candidate

RBEK is the governed execution layer for AI agents, workflows and software.

Your framework or application decides what it wants to do. RBEK decides what may execute at the governed execution boundary.

60-second governed action

from rbek import CLIExecutionBinding, GovernedAction, Policy

weather = GovernedAction(
    name="weather.current",
    policy=Policy.allow_if(
        "latitude <= 90",
        deny_reason="Latitude outside business policy",
    ),
    binding=CLIExecutionBinding(
        provider="open-meteo",
    ),
)

result = weather.execute(
    latitude=32.66,
    longitude=-16.92,
)

print(result.status)
print(result.executed)
print(result.output)

The public Python layer stays small:

• Policy
• GovernedAction
• GovernedResult
• CLIExecutionBinding

CLIExecutionBinding sends a versioned declarative JSON request to:

rbek-cli developer execute

The developer does not manage project roots, provider registration files, plans, gates or evidence paths for this managed execution path.

Two different policy roles

Policy.allow_if(...) is a deterministic pre-execution business policy in the Python SDK. If it denies, the execution binding is not called.

It is not claimed to be equivalent to the canonical RBEK runtime gate policy.

After the SDK business policy allows an action, RBEK CLI remains the execution authority and the private runtime materializes the governed execution inputs before the canonical gate and provider execution.

Framework-agnostic integration

Keep your orchestrator. Govern the execution boundary.

The same GovernedAction pattern can be called from plain Python or wrapped by an agent/workflow framework. Framework-specific examples are reference integrations; they do not move orchestration authority into RBEK.

Publication status

This directory is a staged prerelease candidate for rbek 0.3.0a1.

It is not yet authorized for publication. Final source-license approval remains a release gate.