Observa private beta · Now open

The Observa private beta is open for n8n and OpenClaw workflows.

Bring one real workflow. We map it together, capture reviewable governance evidence, and independently verify supported outcomes against the system that holds the real state. Founder-assisted, SHADOW mode, no production control.

This is a shadow-only beta. Authority remains NONE. Enforcement remains OFF. Applying does not create an account or grant connected dashboard access.

Request Private Beta Access Watch the Demo Explore Observa → Docs and help →

Private beta open n8n + OpenClaw No billing

Use the public OpenClaw plugin Review the public source

Who is it for

Operators and builders whose agents touch real systems.

The beta is a strong fit if a wrong or unverified outcome in your workflow actually costs you something.

Good fitReal n8n workflows in active use.
Good fitOpenClaw agents that take actions with tools.
Good fitMulti-agent or tool-using, action-taking AI systems.
Good fitCRM or system writes with meaningful downstream state.
Good fitWorkflows with retries, validation, or human approval gates.
Good fitTeams that want evidence, not just an activity log.

What happens

Self-service request. Human-reviewed access.

You start the request yourself from the command line. A person still reviews every one, so the beta stays small and the feedback stays real — and founder-assisted onboarding remains available throughout.

Install the Local Node CLI

npm install -g @mcpherson-ai/observa-local-node

Request access

observa request-access --api-url https://governance-plane-observa.tailb473db.ts.net

Check where you stand, any time

observa request-status

Requires Node.js 22 or newer. Installing the package activates nothing: it has zero dependencies, runs no install scripts, and contacts nothing until you explicitly request access.

Email verificationA one-time code, valid for 10 minutes, proves the address is yours.
Human approvalA person reviews the request and decides. This step is never automatic.
PairingApproval sends a single-use invitation. Sign in, create a pairing code, and pair this installation.
Runtime observationInstall the signed composition, configure your runtime, and SHADOW evidence begins to accumulate.

The step-by-step commands for each of these are documented in getting started, with the full CLI reference, the access and pairing lifecycle and troubleshooting beside it.

Observa can discover and map the workflow, capture governance evidence, show review state, observe execution, and independently verify supported outcomes. Verification applies where an appropriate verification contract or profile exists. Runtime completion is not treated as proof, and uncertainty is never silently turned into success.

Watch the demo

See Observa in action: 43 seconds from a real agent task to a reviewable governance record.

An agent before mapping, discovery and AutoMap proposals, human review and classification, and the mapped result. Mapping is proposed and human-confirmed, never applied automatically.

Observa product demo · 43 seconds · has sound; nothing plays until you press play. An agent gets a real task and reaches outside the model, Observa discovers the real capability surface, and a human approves and classifies it. Discovery is automatic; meaning stays human-controlled.

What SHADOW mode means

Observa watches and checks. It does not take the wheel.

In this beta, Observa observes, evaluates, maps, and verifies without taking control of production actions. Your systems keep doing exactly what they did before.

Included in the beta scope

Supported discovery and mapping for approved n8n and OpenClaw workflows
Human review and classification of mapping proposals
Structured, reviewable governance evidence
Shadow policy evaluation with visible review state
Independent verification of supported workflow outcomes
Direct, founder-assisted onboarding and support

Not included or authorized

No public self-service signup or anonymous connected dashboard
No billing, payment flow, plans, or enforcement credits
No blocking, permitting, denying, delaying, approving, or rewriting actions
No production control of any customer system
No PHI, production healthcare workflows, payments, or destructive actions
No guarantee of exhaustive coverage, compliance, or universal outcome verification

Observa proposes and checks. A person reviews. Nothing in this beta grants execution authority.

What we want to learn

The beta exists to test the product against reality.

Participants shape the product. These are the questions we are asking together.

Getting started

Onboarding friction
Installation issues
Runtime and system edge cases

Mapping and governance

Mapping quality
Governance usefulness
Review workflow clarity

Verification and review

Verification accuracy
Dashboard usability
Evidence readability

Supported runtimes

n8n and OpenClaw are the first beta runtime paths.

Runtime positioning

Version-specific support, not blanket compatibility

n8n and OpenClaw are the initial supported runtime paths for the beta.
Exact versions, hosting, and rollback readiness are confirmed during onboarding.
The public OpenClaw plugin remains a separate, free product, currently v0.7.3 and shadow-only. The Local Node CLI for n8n is 0.1.6 on npm.
Runtime support does not mean every connected tool or system has authoritative readback.
McPherson Governance is independent and is not affiliated with or endorsed by OpenClaw or n8n.

Design-partner track

A strong fit for operators, agencies, and builders

You operate or support action-taking agents or workflows.
You can begin in shadow mode and keep human authority intact.
You will review mappings, evidence, and verification results with Blake.
You can provide practical feedback without sharing secrets or customer content.
You want independent verification before considering controlled authority later.

From skill to governed workflow

Already using a McPherson AI skill?

Keep the workflow you already use. The private beta is the next step for operators who want to map the surrounding agent capabilities, capture governance evidence, and see supported outcomes independently verified.

Requests should contain environment context only. Never include secrets, credentials, prompts, message contents, customer records, PHI, or payment data.

Request Beta Access

Request access

Tell us enough to evaluate fit. Nothing sensitive.

This form prepares an email in your own mail app. The website does not create an account, store the answers, or send anything automatically.

If you choose to send the prepared email, McPherson AI receives the information only to evaluate beta fit and reply to your application.

Before you apply

Do not include secrets, credentials, tokens, prompts, message bodies, file contents, customer records, PHI, payment data, or other sensitive material.

Name Email Company or project Your role Runtime Agents or workflows in scope Runtime version or hosting What does the workflow do, and what do you need to understand?

I am open to a design-partner conversation and structured feedback sessions. I understand that applying does not create an account, grant connected access, start billing, or enable enforcement.

Email Blake directly

Nothing is sent automatically. Preparing the application will offer it to your email app and show a copyable fallback.

Private beta FAQ

The important boundaries, in plain language.

Does applying give me dashboard access?

No. observa request-access submits a request; it does not create connected access. A verified email moves the request to review, and a person decides. Founder-assisted onboarding is still available once you are approved.

Will the beta stop or approve agent actions?

No. Authority is NONE and enforcement is OFF. The beta observes supported activity, maps capabilities for human review, captures governance evidence, and independently verifies supported outcomes. It does not control production actions.

Is there a public signup or paid plan?

No. There is no public self-service account flow, billing, payment processing, or enforcement credit in this beta. Access is requested through this page and approved manually.

Does Observa verify every workflow outcome?

No. Independent verification applies to supported workflows where an appropriate verification contract or profile exists for the authoritative system. A successful runtime response is not treated as proof of the downstream state, and when evidence is unavailable or uncertain the outcome stays nonverified.

What do I need to bring?

One real, bounded n8n or OpenClaw workflow that you can discuss without sharing secrets or customer content. Version, hosting, and rollback readiness are confirmed together during onboarding.

Does the beta certify compliance or prove every outcome?

No. Coverage depends on supported integrations, mappings, evidence, and environment context. Unknown, incomplete, conflicting, or stale evidence remains unknown and must not be presented as proof.