Skip to content
MasuGateRequest a customized demo
Menu

Get Started

MasuGate 0.1.1 · Public source · Research preview

Run one governed action from the public source.

Start with the browser story or use the documented Linux/amd64 workflow to build, run, and verify the credential-free procurement demonstration.

Run the public-source demoExplore in the browserBrowse the source ↗

Three ways in

Choose the shortest path to your question.

Each path names both the useful outcome and the boundary you should keep in view.

Best for

See the governed flow

Anyone meeting MasuGate for the first time.

You will
Understand how one request stays connected to policy code, live shared state, the governed effect, and its record.
Boundary
An interactive, deterministic product walkthrough—not captured runtime evidence.
Explore the browser walkthrough
Best for

Run the procurement demo

Developers with the exact Linux/amd64 reference environment.

You will
Build the 0.1.1 release artifacts from source, run the credential-free scenario, and verify its retained result.
Boundary
Source-based only. Setup may use the network; the measured demo needs no credential or network.
Run the public-source demo
Best for

Review or extend the artifact

Researchers and application developers inspecting exact contracts.

You will
Follow a bounded review path, inspect integrations, or trace the implementation and its limitations.
Boundary
Exact research profiles, not a general compatibility or production-assurance claim.
Choose a review path

Public-source workflow

Build once. Run in five minutes. Verify the result.

Start in a clean checkout of the public source. Use the exact commands below; the linked repository guide remains canonical if this workflow changes. Policy-state serializability (PSS) asks whether completed decisions and effects retain a valid, real-time-respecting serial explanation over the declared policy state. Read the full PSS explanation →

  1. 01
    Before you run

    Start from a clean source checkout

    Open the public repository and use a clean Git checkout. The main branch is the current source channel, not an immutable tagged release.

    Open canonical instructions ↗
  2. 02
    Before you run

    Confirm the exact reference profile

    Use Linux/amd64, CPython 3.12, Node.js 24.16.0, npm 11.13.0, uv 0.11.26, and Docker with Compose. Allow 15 minutes and 8 GiB for a cold setup.

    Open canonical instructions ↗
  3. 03
    Run this step

    Prepare the reviewer inputs once

    This setup step uses anonymous network access to retrieve lock- or digest-bound public inputs. The demo itself is offline afterward.

    Command
    test ! -e /tmp/masugate-reviewer-setup
python3 scripts/prepare-reference-demo.py \
  --outdir /tmp/masugate-reviewer-setup

    ExpectedMasuGate reviewer inputs: /tmp/masugate-reviewer-setup/reviewer.env

    Open canonical instructions ↗
  4. 04
    Run this step

    Run the procurement demonstration

    The measured command starts a disposable local Compose stack, retains JSON evidence, and should finish in under 300 seconds.

    Command
    . /tmp/masugate-reviewer-setup/reviewer.env
cd "$MASUGATE_CANDIDATE_DIR"
test ! -e /tmp/masugate-five-minute-demo
"$MASUGATE_REVIEWER_PYTHON" scripts/run_reference_demos.py procurement \
  --release-dir "$MASUGATE_RELEASE_VERIFICATION_RELEASE_DIR" \
  --offline-npm-cache "$MASUGATE_OFFLINE_NPM_CACHE" \
  --source-revision "$MASUGATE_SOURCE_REVISION" \
  --source-date-epoch "$MASUGATE_SOURCE_DATE_EPOCH" \
  --outdir /tmp/masugate-five-minute-demo

    ExpectedMasuGate procurement evidence: /tmp/masugate-five-minute-demo/evidence/procurement.json

    Open canonical instructions ↗
  5. 05
    Run this step

    Verify the generated evidence

    Run the supplied verifier against the same output directory. Treat any non-pass result as a failed gate.

    Command
    "$MASUGATE_REVIEWER_PYTHON" scripts/verify-flagship-demo.py \
  --outdir /tmp/masugate-five-minute-demo

    ExpectedJSON containing "result": "PASS"

    Open canonical instructions ↗
  6. 06
    Run this step

    Inspect the decision-and-effect record

    Follow the request, policy state, decision, governed effect, receipt, and both PSS results in procurement.json and run-metadata.json.

    Open canonical instructions ↗
  7. 07
    After the run

    Remove only the disposable demo output

    After inspection, remove the exact demo output directory. The separate reviewer setup can be retained for another run or removed with the repository's documented cleanup.

    Command
    rm -r -- /tmp/masugate-five-minute-demo
    Open canonical instructions ↗

Success contract

A pass connects the unsafe baseline to the governed result.

The supplied verifier reads the generated evidence instead of asking you to infer success from a screenshot or log excerpt.

A passing verifier confirms
  • the deliberately unsafe stale concurrent baseline is retained
  • the governed execution is PSS-valid
  • one successful committed receipt connects decision and effect
  • both the unsafe and governed PSS verdicts are present
What it does not establish

A passing local run is evidence for this exact 0.1.1 research profile. It is not a production, compliance, arbitrary-host, or arbitrary-policy assurance claim, and it is not an independently retained public verification.

Source and support

Public to inspect, precise about distribution.

The repository, runbook, expected results, review paths, issue tracker, and security policy are public. Package-registry installation and a tagged GitHub Release remain unavailable.

Open the GitHub repositoryRead the repository guide
Exact setupPrerequisites, setup command, network boundary, and cleanup.ReproductionRequired local tier, optional checks, and failure interpretation.Expected resultsObservable pass conditions and nondeterministic fields.Review pathsBounded 15-, 30-, and 60-minute review routes.Claims and limitationsThe exact claim ledger and explicit exclusions.Issue trackerReport a reproducible defect or propose a bounded change.Security policyUse the private reporting route for sensitive findings.

Continue

Inspect the product story or the complete technical boundary.

Use the interactive demo for the concept, or the technical reference for runtime anatomy, outcomes, profiles, and troubleshooting.

Open the browser demoOpen technical reference