Skip to content
MasuGateRequest a customized demo
Menu

Stateful governance for concurrent agents

Many agents, governed by shared rules.

MasuGate keeps policy, changing state, and consequential effects on one protected path—even when agents act at the same time.

See the shared-budget problemOpen the demoView source on GitHubReview MasuGate · 15–60 min

One shared fact

DecisionTravel PlannerRefundable hotel deposit
DecisionWork ManagerHosted testing capacity
Shared mutable stateBusiness budget · $100
  1. Both decisions read $100.
  2. The first effect leaves $40 before the second decision is used.
Two agents depend on one changing business fact.

One shared rule

Both requests fit. Together, they do not.

The business budget has $100 available. Both agents submit $60 requests at nearly the same time.

Shared scenario fixtureBusiness budget: $100Review at or above $50
  • Travel PlannerRefundable hotel deposit$60
  • Work ManagerHosted testing capacity$60
Without coordination

Two approvals use one old observation.

Both reviews use the original capacity without protecting it.

  1. Step 01
    Travel request checks the original capacity
  2. Step 02
    Work request checks the same original capacity
  3. Step 03
    Both detached reviews approve
  4. Step 04
    First detached effect commits
  5. Step 05
    The stale second effect also commits
  6. Step 06
    Combined outcome violates the budget rule
Full transcript
  1. Travel request checks the original capacity: The detached stateful check sees $100 and escalates the $60 request.
  2. Work request checks the same original capacity: The overlapping check also sees $100 and escalates its $60 request.
  3. Both detached reviews approve: Both approvals were based on the same original capacity.
  4. First detached effect commits: The travel purchase consumes $60 and leaves $40.
  5. The stale second effect also commits: The combined spend reaches $120 against $100 of capacity.
  6. Combined outcome violates the budget rule: Each check looked valid when made, but the second decision became stale.
OutcomeRule broken

Each decision looked reasonable alone. Their combined result broke the rule.

With MasuGate

The later decision sees protected capacity.

Escalate makes the first operation pending; deny stops the overlap before the approved effect is committed.

  1. Step 01
    Travel Planner requests a refundable hotel deposit
  2. Step 02
    Travel request enters review
  3. Step 03
    $60 of capacity is protected
  4. Step 04
    Work Manager requests hosted testing capacity
  5. Step 05
    Second request denied
  6. Step 06
    Reviewer allows this operation once
  7. Step 07
    Travel purchase committed
Full transcript
  1. Travel Planner requests a refundable hotel deposit: The first overlapping business purchase requests $60.
  2. Travel request enters review: The policy decision is escalate because $60 meets the $50 threshold.
  3. $60 of capacity is protected: Later requests now see $40 available while review is pending.
  4. Work Manager requests hosted testing capacity: The second overlapping business purchase also requests $60.
  5. Second request denied: $60 exceeds the $40 that remains available.
  6. Reviewer allows this operation once: The resolution remains bound to the pending travel operation.
  7. Travel purchase committed: The protected $60 effect completes and $40 remains.
OutcomeRule preserved

The later decision reflects the state protected by the earlier operation. Separate records retain the committed and denied operations.

Follow the full OpenClaw demo

The same shape appears elsewhere

Shared state is more than a budget.

Capacity
Several agents consume the same inventory, quota, or service limit.
Time
Multiple assistants schedule against protected calendar commitments.
Work
Agents create or replace files under shared workspace rules.

In each case, an action changes a fact that a concurrent decision may depend on.

Why stateful checks are not enough

Keep the decision connected to the effect.

Stale authorization occurs when the state that justified a decision changes before the associated effect happens.

Reading mutable state determines what appears permissible now. Coordination determines whether that decision remains valid through the governed effect.

One decision needs one protected path

Keep the rule, changing state, and resulting effect connected.

Detached check

A decision can go stale.

  1. Request
  2. Check state
  3. Decision
  4. State changes
  5. Effect
Governed action

The decision stays connected.

  1. Request
  2. Policy + state
  3. Coordinate
  4. Effect
  5. Receipt

MasuGate governs only configured consequential routes. The host still owns the surrounding agent, orchestration, and model behavior.

Text equivalent

A request-local check can decide from one state observation and end before the effect, allowing the decision to become stale. In the stateful MasuGate path, the selected request, policy-relevant state, scoped coordination, provider-owned effect, and governance record remain connected while the surrounding agent host stays outside the boundary.

Adapted from Figure 1 of Stateful Governance for Concurrent Agentic Systems (arXiv 2608.02764v1).

The MasuGate boundary

One complete path, from selected request to governed result.

The detailed view shows which responsibilities stay with the host and provider, and which travel through MasuGate together.

Canonical governed-action path

Evidence: Reference
Agent environmentOpenClaw orchestrationAgents, models, sessions, and declared routes stay host-owned.
Policy environmentReviewed policy programOwners maintain the rule outside prompts and runtime code.
Provider environmentState views and effectThe provider owns its facts and configured consequential action.
Host-ownedAgent requestA selected action enters the governed route.
MasuGate boundary
  1. Reviewable stateful policyA structured program holds the rule outside prompts.
  2. Certified policy-state viewsRegistered views supply the rule's mutable facts.
  3. Scoped coordinationThe selected mechanism protects overlapping scopes.

Receipt: revision, state facts, decision, and outcome stay linked.

Provider-ownedGoverned effectThe provider executes the configured effect.

The surrounding agent framework still owns orchestration and model behavior. MasuGate governs only the selected action paths configured to cross its boundary.

Text equivalent

A selected consequential request enters a governed route. MasuGate binds trusted context, evaluates a reviewable policy over certified provider views, coordinates overlapping logical scopes, dispatches the provider-owned effect, and retains the authoritative committed, denied, or pending outcome with its governance record.

Adapted from Figure 4 of Stateful Governance for Concurrent Agentic Systems (arXiv 2608.02764v1).

What MasuGate contributes

From stateful policy to governed concurrent execution.

01

Policy over shared mutable state

Express rules over the shared state that changes as agents act.

How it works

Bounded policy programs can use registered views such as accumulated spend, remaining capacity, approval state, or risk context.

02

Coordination for overlapping actions

Preserve the meaning of stateful policy decisions when governed actions run concurrently.

Technical premise

The technical model is policy-state serializability under explicit policy, provider, and enforcement assumptions.

03

Independently managed, interpretable policy

Manage governance as structured policy, independently of agent prompts and tool implementations.

What reviewers can inspect

Policy owners can inspect, validate, test, review, version, and evolve one shared rule. Records identify the applicable rule, revision, and state facts used.

Policy lifecycleOperations policy owner → reviewed revision → governed agent routes → versioned records

OpenClaw integration

Keep OpenClaw in control. Protect the consequential action.

Selected calls cross the MasuGate boundary; orchestration stays in OpenClaw.

Open the OpenClaw developer demo

OpenClaw governed purchase route

Presentation: SimulatedEvidence: Reference
  1. Host-ownedOpenClaw governed tool callOrchestrates agents and selects the registered purchase tool.
  2. Deployment-owned adapter edgeBind trusted request contextPrincipal and stable action identity come from host context—not model arguments.
  3. MasuGate-owned runtimeResolve route + categorized-purchase@v2Runtime protects the owner-and-category scope; produces allow, deny, or pending.
  4. Provider-ownedCertified state → Configured provider effect
    • Certified view: budget.available
    • Execute: configured purchase effect only after allow or approval
  5. MasuGate outcome → hostCanonical record + authoritative resultThe governed tool returns the authoritative MasuGate operation result.
Text equivalent

OpenClaw continues to orchestrate the Travel Planner and Work Manager. Their declared purchase tool sends the shared-budget request through the selected MasuGate route. MasuGate applies categorized-purchase version 2 to certified budget state, coordinates the owner-and-category scope, returns the authoritative operation result, and retains the canonical record. Unrelated OpenClaw tools remain outside this boundary.

Reference profile: OpenClaw 2026.7.1. Unrelated OpenClaw tools remain outside the declared MasuGate route. Adapted from Figure 4 of Stateful Governance for Concurrent Agentic Systems (arXiv 2608.02764v1).

Blog & announcements

Technical thinking and project updates.

Read the current explainers. Future MasuGate releases, studies, and announcements will appear here too.

View all posts

Inspect the assumptions and evidence.

MasuGate's formal and empirical claims have explicit premises, controlled evaluation boundaries, and named evidence paths.

Open the paper

Continue the conversation

Want to see the scenario applied to your agent system?

Request a customized demo or ask a bounded integration question through the MasuGate project inbox.

Customized walkthrough

Request a customized demo

Tell us the agent system and governance question you want to explore. We will use it to scope the conversation.

This opens your email app with a prepared message to masugate.governance@gmail.com. Review it and press Send there; this website does not transmit or store the form.

Prefer webmail? Copy masugate.governance@gmail.com into a new message.