ui-automation-control-plane

Public Stress Lab Guided Demo

This is the fastest public-safe, no-setup way to understand what Prooflane is today.

Think of it like a guided museum route:

you see the front door,
you walk the main rooms in order,
you inspect one sanitized proof object,
and you leave understanding where AI and MCP actually fit.

What This Demo Is

a read-only walkthrough of the current product story
a public-safe demo layer for external evaluators
a bridge between the stress-lab front door and the deeper governed proof lane

What This Demo Is Not

not a hosted live sandbox
not a public runtime bundle
not a claim that arbitrary public-web targets are fully open today
not a replacement for local verification or governed runs

Step 1. Understand The Product In One Sentence

Prooflane is an AI-native WebUI stress lab for localhost-first browser experiments, with governed proof and agent-ready workflows when results need deeper review.

That sentence is doing three jobs:

main product: WebUI stress lab
safe current scope: localhost-first
deeper layers: governed proof, AI/MCP-assisted workflows

Step 2. See The Main Product Surface

The current launch-first shell map is shown here:

Prooflane studio preview showing the launch-first operator path: Stress Lab first, then Runs and Blocks, then Flow Studio, with Advanced Review as the deeper governed layer behind the first visible result.

This is a semantic front-door preview, not a literal runtime screenshot. That keeps the public demo aligned with the current IA without treating an older maintainer-local capture as current shell proof.

Read it in this order:

Stress Lab: start with the target and experiment mode
Runs & Blocks: read the latest result and clear manual blockers
Flow Studio: refine the journey after you learn something from the run
Advanced Review: open the deeper compare/proof/AI layer only when the result needs it

Step 3. Understand The Result Path

This diagram shows how the public front door and the governed deeper lane fit together:

Prooflane result path diagram showing the local first-look path, the governed run path, and the MCP connection route.

Plain-language rule:

front door first
governed proof second
AI and MCP stay as amplifiers, not identity replacement

Step 4. Inspect One Public-Safe Proof Object

Prooflane keeps exactly one public-safe proof sample in the repo:

Public Proof Sample

Use it to confirm that the deeper layer is real:

governed run bundles exist
manifest and summary contracts exist
public-safe structure can be shown without exposing private runtime evidence

Step 5. See Where AI And MCP Fit

AI and MCP are support layers, not the homepage identity.

AI helps with briefs, grouped findings, and next-step guidance
MCP gives agents and operator copilots access to the same governed runtime
neither one replaces the main stress-lab story

If you want that deeper layer:

Honest Current Boundary

The current public story is intentionally narrower than “test any public URL by default”.

Today the honest MVP boundary is:

localhost-first
web.any-localhost
--base-url
fail-closed outside explicit allowlists

That is a product boundary, not just a marketing disclaimer.

If You Want To Go One Step Further

See the front door: README.md
Follow the quickstart: docs/get-started.md
Read the positioning: docs/why-prooflane.md
Inspect the public proof lane: docs/proof-center.md

This site is open source. Improve this page.