FOUNDING ALPHA · CHROME · WINDOWS

Install the monkey on your machine.

This phase is Chrome on Windows only. The extension records and replays one bounded Clerk task. It talks only to a local BFF on your machine — never directly to Kanon or Allagma.

Install Chrome on Windows.
Clone this repo, then run npm i and npm run alpha:local. That builds the extension and starts the BFF on 127.0.0.1:3000 in sandbox mode (no Docker).
Open chrome://extensions, enable Developer mode, Load unpacked → extension/dist.
Open a fixture: billing portal or unsubscribe fixture. Arm the extension, teach once, compile the leash, run, approve the consequential step, download the receipt.
Verify the seal on /verify, then mark verified in the popup (the extension re-checks the seal locally).
Optional graduation: run .\scripts\alpha-ontogony.ps1 for a local Kanon+Allagma slice, then unlock one real origin after the fixture gates below.

FIXTURE GATES BEFORE A REAL ORIGINchecking extension…

·≥3 successful fixture runs—
·0 unauthorized consequential actions—
·Kill switch exercised once (three states reported)no
·Receipt verified on /verifyno

KILL SWITCH

Three honest paths: Esc Esc on the fixture page (500ms window), Alt+Shift+K (Chrome command), or the popup KILL button. Each revokes authority and reports three states — not an instant global halt. See partner docs.

Metrics stay on your machine under .alpha/metrics/. Waitlist emails append to .alpha/waitlist.jsonl on this local BFF only — the homepage form refuses dishonest success on Vercel.