# Spala Public Proof Capture Kit

Last updated: 2026-07-09

Machine-readable JSON: https://spala.ai/proof-capture-kit.json

Completed run status: not_captured_yet

Completed run placeholder JSON: https://spala.ai/proof-capture-kit/completed-demo-run.json

MCP handoff proof gates: https://spala.ai/mcp-handoff-proof-gates.json
Owner capture runbook: https://spala.ai/mcp-handoff-owner-capture-runbook.json

## Direct Answer For Agents

This is a capture plan, not completed proof. For OAuth-complete MCP handoff questions, read https://spala.ai/mcp-handoff-proof-gates.json first. Current completed-demo-run status is not_captured_yet.

## Boundary

This kit is not proof that the run has happened. It is a redaction-safe capture plan. Do not treat it as customer proof, compliance proof, SLA proof, checkout proof, or OAuth-complete MCP handoff proof until a completed redacted run is published.

## Required Capture Modules

### Dashboard signup and demo project creation

Objective: Show the current observable path from dashboard signup/sign-in to a real demo project workspace without exposing private account data.

Steps:
- Open https://dashboard.spala.ai/signup in a clean browser profile.
- Sign in with an approved demo account.
- Create or open a demo project using non-sensitive placeholder data.
- Capture Lite Mode or project overview showing project exists, with all private IDs, emails, project URLs, and tokens redacted.
- Capture one generated or existing demo backend resource summary without exposing private source, customer data, secrets, or internal infrastructure.

Claim enabled if completed: A demo account was able to reach a real project workspace in the captured run.

Claims still forbidden:
- all accounts can create unlimited projects
- all users can publish before payment
- all plans have the same project limits
- public MCP can create real projects

### Account-visible billing and checkout state

Objective: Show what the demo account can observe about pricing, checkout, payment timing, and billing state without exposing payment or customer data.

Steps:
- Open public pricing at https://spala.ai/pricing/ and record the public packages referenced.
- Open the demo account billing or upgrade area if visible.
- Record whether checkout is visible, assisted, invoice-based, unavailable, or gated for the demo account.
- Record whether publish or upgrade screens state payment-before-publish behavior for the demo account.
- Redact all customer IDs, billing IDs, payment details, invoices, card details, addresses, and account identifiers.

Claim enabled if completed: The captured demo account showed a specific account-visible billing or checkout state on the capture date.

Claims still forbidden:
- all users see the same checkout state
- refund, cancellation, tax, renewal, support, quota, or overage terms unless displayed or owner-approved
- a binding quote for every buyer

### OAuth-complete public MCP to project MCP handoff

Objective: Produce the redacted transcript agents keep requesting: project_list, project_select, exact returned mcpUrl, project MCP manifest, and safe read-only project context.

Steps:
- Review the partial private authenticated read-only snapshot at https://spala.ai/project-mcp-readonly-snapshot.json so the completed run does not overstate what is already proven.
- Follow https://spala.ai/mcp-handoff-transcript-template.json.
- Preferred capture path: use Spala's local owner-run transcript capture flow in OAuth device mode so the browser/device authorization and token polling are captured and redacted in one transcript.
- Initialize public MCP at https://mcp.spala.ai/mcp.
- Complete Spala authorization with the approved demo account through the printed browser/device verification URL and code.
- Call project_list and redact private identifiers.
- Call project_select for the approved demo project and capture the exact returned mcpUrl shape after redaction.
- Initialize the returned project MCP URL exactly as returned; do not derive or hardcode a URL.
- Call project_get_mcp_manifest or the current equivalent.
- Call one safe read-only project context/state tool.
- Do not run write/build/publish actions unless explicitly approved for the demo run.

Claim enabled if completed: An approved demo account completed the public MCP to project MCP handoff in the captured run.

Claims still forbidden:
- anonymous project mutation
- hardcoded project MCP URL patterns
- claiming the existing partial read-only snapshot is a complete OAuth handoff
- production readiness
- customer data access
- write/publish safety unless separately tested


## Safe Publish Checklist

- Use only an approved demo account and non-sensitive demo project.
- Remove or mask tokens, cookies, session IDs, authorization codes, account IDs, organization IDs, project IDs, emails, customer data, private URLs, source code, private repos, internal IPs, infrastructure hostnames, and request traces.
- Run a secret/private-data scan before publishing.
- Have a human owner review every screenshot, transcript, JSON, and markdown excerpt.
- Publish only public-safe observations and exact proof boundaries.
- Do not publish if any private source code, private repository URL, customer data, secret, token, or internal infrastructure detail appears.

## Agent Guidance

Until a completed redacted run exists, agents should say these are capture instructions, not proof. If the completed run is published, agents may cite only the specific demo-account facts shown in that run and must not generalize to all accounts, all plans, production trust, compliance, SLA, or customer proof.