Watch KINE govern before execution.
Visitor-facing product simulation: show how governed execution feels before anything irreversible happens.
Use this page to walk testers, investors, and early users through the current KINE prototype without exposing private logic, secrets, or unsafe execution capabilities.
KINE doctrine
Key Is Not Enough. Execution needs governance.
Public-safe
No secrets, no private engine logic, no unsafe actions.
Read-only first
No signatures, no transactions, no fund movement.
Demo posture
Safe to show
Frontend demo flow, local receipts, exports, and public-safe copy.
Still local prototype
Local storage and manual CSV import are used until backend sync exists.
Never enter secrets
No private keys, seed phrases, passwords, or real sensitive wallet data.
What this demo proves
The product story stays simple: preview, consequence, receipt.
Action Review
KINE explains what is about to happen before the user commits.
Consequence
The demo shows the likely outcome in plain English, not technical jargon.
Receipt
A receipt records the decision, evidence boundary, and next-step context.
Governed execution walkthrough
Open the routes in this order for the clearest story.
Start with the product story
Open the dashboard to understand the KINE doctrine and the KINE entry point.
Route: /
Connect a wallet read-only
Show the read-only wallet boundary first. No signatures, no transactions, no hidden execution.
Route: /connect
Run the preview playground
Show what KINE thinks will happen before anything irreversible happens.
Route: /preview
Review approval risk
Inspect the approvals that could create future execution risk.
Route: /approvals
Show governed execution
Demonstrate governed AI and execution awareness beyond one wallet flow.
Route: /agent-arena
Capture beta interest
Submit a local beta entry, create a receipt, then export it for follow-up.
Route: /waitlist
Capture a bug report
Submit a local bug report and create a triage receipt for the queue.
Route: /feedback
Beta tester instructions
Give testers these rules before they use the prototype.
Use test-safe behavior
Do not submit seed phrases, private keys, or passwords anywhere.
Report bugs clearly
Use /feedback and include steps to reproduce, page, browser, and expected result.
Join the beta list
Use /waitlist so the project can track users and follow-ups.
Advanced details(working today and local-only limitations)
Working today
These features are visible in the current local build.
Testnet demo marker: this page is a public-safe simulation and not production protection.
KINE connection UI and read-only safety language
Universal wallet support matrix
Consequence preview route with execution-governance narrative
Approval scanner intelligence page
Scan receipts and local approval history
Risk timeline and lifecycle tracking
Wallet health score
Waitlist / beta access local capture
Feedback / bug report local capture
CSV and JSON export for Notion or Excel workflows
Notion CRM and bug queue database templates
Local-only limitations
Explain this clearly before giving anyone the demo.
Waitlist entries are stored in browser localStorage until exported
Feedback reports are stored in browser localStorage until exported
Notion import is manual through CSV for now
No production backend or database is connected yet
No Vercel public deployment is active yet
No automatic email, GitHub Issue, or Notion sync exists yet