System map

31 units · gate PASS · 11 proven / 4 unproven

Green 31Yellow 0Red 0Unsigned 0Pink 0

A drill-down tree. The box on the left is where you are; its contents branch to the right. Click a container › to zoom into it, click the left box or ↑ Up a level to zoom out, and click a unit to open its spec, code & checks.

Recent changes

Commands

Every yay command and its flags. Passphrases/keys come from your .env; run yay help in the terminal for the terse version.

yay init [dir]

Guided setup: files → signing key → adopt → Constitution → optional System Plan. Signing key: local, mobile over your LAN, or mobile over relay.yaylayer.com (for off-LAN, end-to-end encrypted).

--key local|mobilesigning-key type (mobile = pair your phone)

--relay / --lanmobile transport: hosted relay.yaylayer.com (off-LAN) or your local network

--name <you>signer name on every seal

--adopt / --no-adoptscaffold specs over existing code

--constitution <keys|all>write the Constitution into AI-harness files

--plan / --no-planenable AI System Plan

--provider anthropic|openai|customplan LLM (+ --base-url, --model, --api-key)

yay keygen --name <you>

Create your ed25519 signing key (public → roster, private → encrypted keystore).

--passphrase <p>or the YAY_PASSPHRASE env var

yay pair [--name you]

Pair your phone as the signer — scan the QR; the private key stays on the phone. The FIRST pairing (no roster yet) makes the phone the trust root itself, so no local key is ever needed. Served over HTTPS by default.

--name <you>attach the phone key to this identity

--relay / --lanroute via relay.yaylayer.com (off-LAN, E2E) or the local network

--no-httpsdisable TLS (default: mkcert-trusted cert if available, else self-signed)

yay enroll --name X --pubkey <b64>

Enroll another signer via an OWNER-signed roster event.

--role owner|signerrole to grant (default signer)

--by <owner>which owner authorizes it

--phoneauthorize on an owner’s phone (no local key needed)

yay revoke --name X

Revoke a compromised/rotated key (or a whole identity) via an owner-signed event. Past approvals stay attributed; refuses if it would leave no owner.

--pubkey <b64>revoke just this key (omit to remove the whole identity)

--phoneauthorize on an owner’s phone

yay reroot

Retire the current trust root and establish a new one — recovery for a lost/compromised root key. A trust discontinuity: re-sign specs and repoint the CI pin afterward.

--phoneroot the new key on your phone (phone-as-genesis)

--name <you>new local owner name

--forceskip the confirmation prompt

yay adopt [path]

Scaffold draft (unsigned) spec blocks over existing code.

--drypreview what would be added

yay sign [--cell IDs]

Approve the current specs — appends a signed seal. Uses THIS project’s signing method automatically (phone or local); no flag needed. If a dashboard is running, the request pops up on the phone you already scanned.

--phone / --localforce the device (default = the project’s method)

--no-httpsdisable TLS for the phone (on by default)

--brief "<text>"the signed Brief — the human-owned headline over this change-set, REQUIRED by default (editable on the phone; you are prompted if omitted at a terminal)

--no-briefskip the Brief for a trivial re-sign

--relay / --lanphone transport override (project default is set at init)

--cell <ids>only these Cells (comma-separated)

--name <signer>which signer

yay verify [--strict] [-d]

The gate: paint every Cell + run the behavioural prover & mutation grading.

--strictnon-zero exit if blocked (for CI)

-d, --detailsprint each spec, code & checks

--problemsshow only non-green Cells

--no-mutateskip mutation grading

yay test [--test "cmd"]

Run the project’s OWN test suite (package.json "test" / config.test) — the runtime backstop for what per-Cell checks can’t reach. Non-zero exit on failure (for CI).

--test "<cmd>"the command to run (else package.json test)

yay adversary [--cell IDs]

Spec-only adversary: an LLM sees ONLY each Cell’s spec (never the code) and writes probes to BREAK it, run against the real code. A break is a genuine spec↔code violation. Needs an LLM key.

--cell <ids>only these Cells

--provider …same provider config as the System Plan

yay plan

AI-synthesize the high-level System Plan → .yaylayer/plan.json.

--provider anthropic|openai|customLLM provider (key from .env)

--base-url <url>custom / OpenAI-compatible endpoint (Ollama, LM Studio, vLLM — key optional)

--model <m>model id

yay map [-o file.html]

Write this HTML site (Map / Files / System Plan / Signers / Commands).

-o <file>output path

--no-planomit the System Plan entirely

--replanforce plan regeneration

yay dashboard [--port N]

Live control panel + phone relay: serves the map (auto-refreshes) with on-demand buttons — ✍ Sign changes (push a brief to your phone to approve), Changes, Run tests, Adversary, Regenerate System Plan — AND routes pair/sign/authorize to the phone you scanned ONCE. Has a Briefs tab (the ledger of what was ordered). Leave it running. HTTPS by default; the phone installs the cert from the /trust page for warning-free https.

--port <n>port (default 48757)

--openopen it in your browser

--no-httpsdisable TLS (default: mkcert-trusted cert if available, else self-signed)

yay gate [dir]

Write the CI gate workflow and print the branch-protection steps.

--hookalso install a local pre-push gate

--scope <dir>gate only a subfolder

--forceoverwrite existing files

yay constitution --for <keys>

Write the Constitution where an AI harness auto-reads it.

--for <keys|all>claude, agents, copilot, cursor, windsurf, cline, gemini, generic

--listlist the harnesses

yay status

One-line health summary of the project.

Generated by yay map · zoomable hierarchy · green = code proven to match a signed spec, pink = no spec · ▲N = Cells that depend on this (blast radius) · unused? = no callers found.