Plugin, hub, dashboard

Three pieces. The plugin makes the record, the hub keeps it, the dashboard shows it.

1. The plugin, in the session

The plugin runs inside a person's coding sessions. In each project it establishes an estate: a place where the work of that project is tracked. From then on it keeps an honest ledger of what was asked and what landed, and it gates every “done” on an exit code — a check that ran, not a claim that it did.

On each commit it banks two things to the hub: a map of the commit, and a product-management view of the build.

2. The hub, holding the record

The hub is a Cloudflare Worker running at portal.reach.rest. It stores each estate's snapshots, issues the identity your machine uses, and holds the tenancy:

An org is a cohort or a team, and carries a plan.
A member belongs to an org with a role: owner, mentor, manager or member.
A project is bound to one org and has one owner.

Two limits hold today: one person belongs to one org, and only the house creates orgs and binds projects to them.

3. The dashboard, for the person checking

The dashboard sits behind the sign-in and shows the org you belong to. The overview puts the cards in needs-attention order and carries a process headline and the last seven days of banks. Open one project and you get its detail view with a 33-signal build lens.

That is the whole reading surface. A mentor checks process; a manager checks progress; neither needs to read the code to do it.

Two doors

People sign in with an email code

Opening the portal sends a one-time code to your email address. There is no password to set and none to lose. Your email address is your identity here.

Machines hold a token

Your machine runs a device flow against the hub and receives a signed token that lasts 30 days and is refreshed at the start of each session. It is scoped to your org and the projects you own. Removing a member revokes every live token that person holds, at once.

Getting set up, as it works today

This is done by hand right now. Saying so is the point: the site does not claim a signup flow that is not built.

The house owner allows your email address at the door.
The house owner creates your org, adds you as a member with a role, and binds your project to the org with you as its owner.
You install the plugin, run its login, open the portal's activation page, pass the email code, enter the device code and approve. Your machine now holds its token.
In each project you establish the estate. From then on every commit banks to the hub and the dashboard shows the estate.
When someone leaves, the house owner removes the member and every live token of theirs is revoked.

Steps 1 and 2 are what signup and payment on this site are meant to replace, and step 3 is what a self-serve install is meant to make automatic. Neither is finished.