Primary product

Agent governance that starts before the session does.

Signed governance loads at start or resume. Local hooks enforce the installed policy outside the model. Signed observations and service receipts make the result inspectable.

Request accessInspect the signed skill library

Alpha access is free and no payment method is collected. Pricing will be introduced before general availability, with advance notice and an explicit choice.

Two ways to run an agent

Check each action, or set up the world first.

Both keep an agent inside limits. They differ in where the check happens and how many chances there are to slip past it. The first is often called supervision, the second governance. mistwire's alpha installs hooks, which is the first; setting up the session first is next.

What has to be watched
Every way the agent can act.
What can be missed
Any path nobody covered.
When a bypass is possible
At any action.

The cycle in five moves

From published trust to local enforcement.

Every arrow from the service carries something signed by a key your machine pinned. Every arrow from your machine carries something signed by a key the service enrolled. Neither side acts on an unsigned claim from the other. Click a numbered step or play the sequence.

The cycle in five movesTwo lanes, your machine and the mistwire service. The service publishes keys and your machine pins them. Your machine pulls the signed policy, verifies and installs it, checks each request locally, then reports what is installed and receives a signed receipt.your machinemistwire service · outside the sessionPublished keyspublisher key · receipt key1 · Pin the keysonce, before trusting anythingthe keys your machine will trust2 · Pull the policyask for the current signed policySigned policymanifest + files, signed by the publisher keyaskssigned policy + files3 · Verify and installsignatures · rollback floor · hashes · hooks4 · Check each requestallow · deny · ask a humannothing leaves the machine5 · Report what is installedpath · present · hash · modeCompare and signagainst the policy it signedsigned reportsigned receiptSTEP 5 REPORTS WHAT IS INSTALLED · STEP 4 NEVER LEAVES THE MACHINE
The complete lifecycle

Trust and signed policy originate outside the agent-controlled session. Verification and request enforcement happen locally. Installed-state attestation remains a separate evidence lane.

What happens to a request

See the local decision—and keep attestation separate.

Choose a behavior covered by the current signed alpha bundle. Follow its local outcome, then inspect the separate evidence path for installed governance state.

The request
It points to

Choose a current alpha behavior. The path lights up from local request to a bounded, legible outcome.

Where a request can goOne request enters, meets one of four signed-rule results, and ends allowed locally, denied locally, or with a human decision. The chosen path is lit.1 · REQUEST2 · SIGNED RULE3 · OUTCOMERequestreaches the local hookSafe-read rule matchessigned ruleProtected governance path matchessigned ruleKnown hazard pattern matchessigned ruleNo rule matchessigned ruleAllowed locallyoutcomeDenied locallyoutcomeHuman decisionoutcome
Auto-approved locally

Bounded safe-read rule matches. Host proceeds within the signed boundary.

Tool request

The session asks to read one source file.

The host exposes the requested operation and path to the installed local permit hook before deciding whether to proceed.

Plainly: the action is named before any auto-approval.

Separate lane

Attestation verifies installed governance state. It does not claim to be a per-action log or proof of what this individual request did.

What the receipt catches

Your machine reports what it saw. The service decides what it means.

Set the state of each governed file and read the verdict. The service compares the report against the policy it signed, and signs the answer with a key your machine does not hold.

reportwhat arrived from your machine
policypolicy/governance.toml
hookhooks/mw-permit.sh
skillskills/commit-ritual/SKILL.md
docdocs/ENFORCEMENT.md
extraan unlisted file in the governance folder
nexta second, independent witness
The receipt says Compliant

Every governed file matches the signed policy.

    Every verdict
    • Compliant live
    • Drifted live
    • Unknown live
    • No report yet planned
    • Reports disagree planned

    Mirrors the service's adjudicator: policy, hooks and skills are graded; docs are not. Unknown means the report named a policy the service does not know, so it cannot judge. No report yet and Reports disagree are planned verdicts, drawn here so the layout has room for them. A signed receipt binds an enrolled key, observation, bundle, time, and service verdict. It attests installed governance state; it is not a per-action activity log or proof that a customer-controlled machine reported truthfully.

    Outside the agent-controlled session

    Trust & policy plane

    Identity, trust roots, signed policy distribution, and attestation remain above the session so the agent cannot rewrite its own governance.

    Protected
    Trust rootsPublisher and receipt keys
    Signed bundlesVersioned policy artifacts
    EnrollmentBound agent identity
    AttestationInstalled-state verdict
    Inside the execution path

    Local enforcement plane

    Installed hooks evaluate covered requests before execution. A safe read may proceed, a signed hazard is denied, and uncertain requests remain with the host and human.

    Local
    Agent requestProposed tool action
    Signed ruleLocal match and boundary
    OutcomeAllow, deny, or ask
    Host controlHuman remains authoritative
    Two locations, one governance model

    The policy is distributed from outside the session and enforced locally in the request path. Attestation remains separate from individual action outcomes.