Skip to content

Latest commit

 

History

History
125 lines (88 loc) · 4.03 KB

File metadata and controls

125 lines (88 loc) · 4.03 KB

QUICKSTART.md - Try Dizzy Locally

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.

Before You Start

  • 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 start starts the API; set DIZZY_DASHBOARD_ENABLED=1 before start to serve /dashboard.

1. Install

git clone https://github.com/Simultech369/Dizzy-the-Polymath.git
Set-Location -LiteralPath ".\Dizzy-the-Polymath"
npm install

2. Start The Local API

npm start

Expected 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.

3. Check The API

In another PowerShell window:

Invoke-RestMethod http://127.0.0.1:3000/health
Invoke-RestMethod http://127.0.0.1:3000/prompt

The health endpoint should return ok. The prompt endpoint returns the local prompt bundle served by the runtime.

4. Start The Dashboard

Stop the previous server if needed, then start with the dashboard flag:

$env:DIZZY_DASHBOARD_ENABLED="1"
npm start

Open:

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.

5. Inspect The Latest Receipt

Get-Content -Raw .\reviews\oss_council_verdict_latest.json | ConvertFrom-Json
Get-FileHash .\reviews\oss_council_verdict_latest.json -Algorithm SHA256

Current 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.

6. Verify The Local Surface

npm run check:council
npm run test:dashboard-public-surface
npm run test:dashboard-safety
npm test

Useful focused checks:

npm run check:docs
npm run check:next
npm run check:production

npm 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.

7. What Is Not Claimed

  • Dizzy is not a hosted production service.
  • /api/a2a/incoming is 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.

Reading Path

  1. README.md explains what Dizzy is and what runs today.
  2. RUNBOOK.md shows operational commands and local recovery steps.
  3. NEXT.md separates completed work from remaining work.
  4. PR_W0068_DESCRIPTION.md summarizes the staging branch for review.
  5. reviews/oss_council_verdict_latest.json is the latest local machine receipt.