Dizzy is a local-first operator console and control-plane prototype for bounded memory, trust zones, receipts, and agentic work. This guide proves what runs locally today.
It does not claim a hosted production product, public A2A interoperability, or finished commercial application.
- Node.js 20.18.1 or newer is recommended.
- PowerShell examples assume Windows.
- Redis and external model keys are optional for this walkthrough.
- The dashboard is opt-in.
npm startstarts the API; setDIZZY_DASHBOARD_ENABLED=1before start to serve/dashboard.
git clone https://github.com/Simultech369/Dizzy-the-Polymath.git
Set-Location -LiteralPath ".\Dizzy-the-Polymath"
npm installnpm startExpected shape:
Dizzy agent server listening on http://127.0.0.1:3000
[health] http://127.0.0.1:3000/health
Exact ports and timestamps may vary with your environment.
In another PowerShell window:
Invoke-RestMethod http://127.0.0.1:3000/health
Invoke-RestMethod http://127.0.0.1:3000/promptThe health endpoint should return ok. The prompt endpoint returns the local prompt bundle served by the runtime.
Stop the previous server if needed, then start with the dashboard flag:
$env:DIZZY_DASHBOARD_ENABLED="1"
npm startOpen:
http://localhost:3000/dashboard
If DIZZY_AUTH_TOKEN is set, use:
http://localhost:3000/dashboard/login
Enter the token there. Do not put tokens in URLs or browser storage.
Get-Content -Raw .\reviews\oss_council_verdict_latest.json | ConvertFrom-Json
Get-FileHash .\reviews\oss_council_verdict_latest.json -Algorithm SHA256Current local receipt after the W-0105 public-view readiness guard:
VERIFIED_PASSED
2026-09-02T01:55:02.622Z
113 syntax targets / 56 deterministic execution suites / 2 governance checks
SHA-256: F1236DF4DFFC1B15BC9958A50D001BA0C0B9B291C887854B34FBF144D4C69C56
Receipts are local evidence, not a promise about every future machine. Rerunning the council audit writes a fresh timestamp and hash.
npm run check:council
npm run test:dashboard-public-surface
npm run test:dashboard-safety
npm testUseful focused checks:
npm run check:docs
npm run check:next
npm run check:productionnpm run check:staging-boundary is an internal staging-deck guard. In public
checkouts it passes only when the private triage ledger is absent and the tree is
clean, or when an internal triage ledger is present and every dirty tracked file
has an explicit disposition.
- Dizzy is not a hosted production service.
/api/a2a/incomingis a single-runtime, shared-secret signed JSON ingress proof. It does not prove external peer identity, signed responses, distributed replay protection, or cross-runtime interoperability. The local signed A2A ingress boundary is verified by deterministic tests; public interoperability remains future work.- The Python Council Engine remains a quarantined proving sidecar, not production authority for this repo.
- Redis, external providers, and model backends can be offline; the dashboard should show unavailable or unverified states instead of pretending they are healthy.
- Operator captured the W-0106 walkthrough screenshots offline. No repository path or PR attachment is recorded in this checkout, so this is operator-observed evidence rather than a repository-verifiable launch artifact. W-0106 is operationally resolved. Source, API, and route guards passed.
README.mdexplains what Dizzy is and what runs today.RUNBOOK.mdshows operational commands and local recovery steps.NEXT.mdseparates completed work from remaining work.PR_W0068_DESCRIPTION.mdsummarizes the staging branch for review.reviews/oss_council_verdict_latest.jsonis the latest local machine receipt.