Wayglass

Wayglass decides, for each code change an agent proposes, who has to look at it before it lands. Routine changes land on their own or go to a reviewer agent; changes that touch auth, personal data or infrastructure go to a person. Every decision records the rule that matched and the reason, and that record travels with the commit as a git note.

It has two parts:

• The wayglass CLI, one Go binary. People use its commands and two terminal UIs (watch, review); agents add --json to any command and get a stable envelope and exit codes.
• A Cloudflare Worker that keeps the intent registry, decisions and audit log in a Durable Object, mints short-lived Artifacts tokens, and runs the policy on the server.

Each unit of agent work is an intent. Declaring one forks the project’s trunk repo in Cloudflare Artifacts and hands the agent a write token for that fork only. When the agent proposes its change, the Worker reads the fork, tags the diff by area, data class, risk and jurisdiction, and applies .wayglass/policy.yaml as it stands on the trunk.

Where to start

• Quick start: log in, initialise a repo, and take one change from intent to landed commit.
• Concepts: intents and forks, tags, policy, overlaps, landing.
• For agents: the JSON envelope, exit codes and a loop an agent can follow.
• Security model: what each token can do, how long it lives, and what the Worker refuses to trust.
• Command reference: every command and flag, generated from the CLI’s help.
• policy.yaml reference: the policy file field by field.