MasuGate 0.1.1 · OpenClaw reference

Inspect the public-source purchase boundary.

Inspect the OpenClaw 2026.7.1 boundary declared by the MasuGate 0.1.1 public-source research preview without treating the website simulation as recorded execution.

Exact source identity

The source and runbook are public. Distribution remains source-only.

These values come from the public Git tree and 0.1.1 descriptor. The observed mutable main revision and the release provenance identity are deliberately shown separately.

Reference identity: masugate-openclaw-reference/0.1.1
Public repository: github.com/masugate/masugate
Observed main commit: 10f097ced9480ca86c138a9c3d8c92bebdadcefa
Host pin: OpenClaw 2026.7.1
Adapter pin: @masugate/openclaw@0.1.1
Governed route: masugate_governed_action → purchase → spend.purchase

Public-source reference detailEnvironment, source lineage, and distribution state

Channel: research-preview
Visibility: Public as observed 2026-09-03
Release provenance revision: 1373f5507c1680c60a7700d8a6c26a8b4d3fb025
Observed main tree: 75ae5448eb7b688895be34260f937a4a51dfdc54
Release tag: Not Published
Target: Linux/amd64 · CPython 3.12 (tested 3.12.3)
JavaScript toolchain: Node 24.16.0 · npm 11.13.0
Source toolchain: Git 2.43.0 · uv 0.11.26
Container toolchain: Docker 29.6.1 · Compose 5.3.0
Reference deployment: masugate-openclaw-reference 0.1.1

Source intake · 2026-09-03Public source and local runbook available; tag and registries unpublished.

MasuGate 0.1.1 is public as a source-based research preview with a documented local demonstration. The mutable main branch is not a tagged release, registry packages are not published, and no independent retained public run is claimed.

Finite governed route

One exact purchase boundary—not a general OpenClaw plugin claim.

Source-reviewed configuration excerptReference configuration · not a registry install

{
  "masugatedBaseUrl": "http://masugated:8000",
  "agents": {
    "buyer-alpha": "MASUGATE_BUYER_ALPHA_TOKEN"
  },
  "routes": {
    "purchase": {
      "action": "spend.purchase",
      "arguments": {
        "amount_cents": "integer",
        "merchant_id": "string",
        "request_ref": "string"
      },
      "owner": {
        "providerId": "masugate.spend.reference",
        "position": "protected-external",
        "connectorId": "reference-purchase-v1"
      }
    }
  }
}

Trusted identity

openclaw:buyer-alpha

The adapter derives openclaw:<agentId> and a SHA-256 stable identity from trusted agent ID, canonical session key, live session ID, and tool-call ID. Model arguments cannot supply those fields.

Provider ownership

masugate.spend.reference

spend.purchase · protected-external · reference-purchase-v1

Replacement boundary

masugate_governed_action

The configured MasuGate tool returns the authoritative committed, denied, or pending result. It does not call a second native purchase effect afterward, and it does not govern unrelated OpenClaw tools.

Source-reviewed policyspend_budget_guard@1.0.0

policy spend_budget_guard on spend.purchase {
  deny budget_cap when args.amount_cents > spend.available_cents(principal.team);
  escalate ask_first when args.amount_cents >= 500;
  allow otherwise;
}

The 500-cent ask-first threshold belongs to this bounded reference deployment. It is not a universal spending rule, and the reference policy does not establish merchant, tax, fraud, or legal validity.

Provider-owned state view

`spend.available_cents(String) -> Int`

Consistency: scoped-policy-state
Bound: 100 ms declared maximum
Scope: spend:team:<team>
Reservation view: unsupported

The policy reads provider-owned remaining capacity. Admission must still reserve that budget atomically at the protected execution boundary.

Two related evidence lanes

Keep the OpenClaw host path separate from the procurement workload.

Both are useful public-source surfaces. They are not interchangeable, and this website does not present either as an independently retained run.

Public source · Reference evidence

Pinned OpenClaw host round trip

OpenClaw 2026.7.1 agent harness and @masugate/openclaw 0.1.1

The source gate is designed to assert:

$1 purchase commits and an identical tool call replays the same operation
$6 purchase returns a durable pending result
Two concurrent $2.50 calls produce one committed and one denied result
The committed audit contains a succeeded protected-execution receipt

Boundary

The public source contains this integration gate with PostgreSQL MasuGate state and a SQLite purchase-effect fixture. This website does not present a retained execution of that gate.

Promotion gate: Pinned-host integration gate (PostgreSQL MasuGate state; SQLite effect fixture)

Public source · Reference evidence

Clean-artifact concurrent procurement workload

Credential-free MasuGate service workload inside the reference stack

The source gate is designed to assert:

Two $60 requests compete for one $100 budget
One request becomes pending while the other is denied against protected capacity
Allow-once resolves the pending operation to one committed effect
The verifier checks policy-state serializability (PSS): whether terminal decisions and effects retain a valid, real-time-respecting serial explanation over declared policy state

Boundary

This workload matches the Stage 2 arithmetic, but it drives masugated directly rather than an OpenClaw conversation and uses different identifiers and policy artifacts.

Promotion gate: Five-minute procurement and flagship-verifier gates

Relationship to the three-stage walkthroughRelated to the walkthrough, but not the same evidence.

Source overlap is shown as related—not exact—until identifiers, driver, policy, outcome, and retained evidence all match.

Stage 1 · Related source path

One governed purchase

The pinned host gate encodes test cases for a governed purchase, replay, pending result, and receipt.

Why this is not exact

The website uses a $40 Work Manager request and categorized-purchase@v1; the source reference uses buyer-alpha, spend_budget_guard@1.0.0, and different amounts.

Stage 2 · Related workload

One budget across agents

The clean-artifact workload uses the same $60 + $60 against $100 concurrency and approval shape.

Why this is not exact

Its runner drives masugated directly, not an OpenClaw chat or tool turn, and its agent, route, and policy identifiers differ from the website fixture.

Stage 3 · Simulation only

More governed operations

The public source contains calendar and filesystem components and narrower reference checks.

Why this is not exact

No credential-free OpenClaw gate reproduces the website's overlap policy, fixed alternative, itinerary, and protected-file story.

Availability boundary

What is public now—and what remains unpublished.

The source workflow is runnable now. Recorded or Verified labels still require retained output, an exact environment, and a dated evidence destination; a tag or registry package is a separate step.

Public nowPublish the 0.1.1 source reference
The repository, release descriptor, package catalog, and OpenClaw integration guide are publicly inspectable.
Public nowPublish the source-level controls
The public tree includes documentation checks, exact version pins, locks, and the 0.1.1 descriptor.
Public nowPublish the source-based run contract
The exact setup, procurement run, verifier, expected output, and cleanup steps are documented for the Linux/amd64 profile.
Public nowExpose the local reference workflow
The source-owned workflow builds the exact local artifacts and runs the credential-free procurement demonstration with its supplied verifier.
Still unpublishedRetain dated runtime evidence
Publish the request, decision, governed effect, record, verifier result, exact revisions, and verification date as one evidence bundle.
Still unpublishedPublish an immutable distribution
A v0.1.1 tag, GitHub Release, and PyPI/npm packages do not exist yet. Do not present the source channel as those distribution forms.
Public nowKeep public support routes active
The public source exposes its issue tracker, review path, and SECURITY.md route. This does not imply a tagged or registry release.

Continue with the exact boundary

Run the source reference or return to the simulation.

Run from public source Return to the interactive walkthrough Request a customized demo