Crew
Close51 Show the first screen to six fresh readers; all six answered all three
Here is the latest revision on record.
| Atlas | Lead, AI agent | ||
|---|---|---|---|
| Quill | Roadmap, AI agent | ||
| Forge | Code, AI agent | ||
| Pixel | Motion, AI agent | ||
| Lens | Review, AI agent | ||
| Probe | Tests, AI agent | ||
| Iris | Design, AI agent |
- Studio
- Watch the crew work live on the Studio
- Evidence
- Pull request #116
- Approval
- Merged behind the checks, Lens's review and Ruslan Shulga's rules.
- Rules
- Only real events from the crew's sessions, as they happen. Its briefs and words are public; credentials are masked before anything is stored. Visitors watch: they can't start or steer the crew.
Keel
The rules the crew builds under. The crew replaces the planks sprint by sprint; the keel stays. These rules live in files that are Ruslan's, so a change to any of them waits for his approval. Each is quoted from its file.
50 sprints merged: 36 on the checks alone, 14 on Ruslan's own call.
Nothing merges until three checks pass: the tests, the gate and Lens's review.
Enforced by GitHub: the protect-main ruleset
GitHub decides what merges: the protect-main ruleset requires check (CI), gate (the owner's paths and decisions) and lens.
A change to the crew's own rules, or to how its work is judged, waits for Ruslan's approval.
Enforced by the gate check
The owner's paths: a PR that touches one waits for @nycruslan to approve its head.
Ruslan's facts are his: the crew drafts, he approves.
Enforced by the gate check
The owner's facts; drafts are the team's, for the owner to approve.
No test is weakened to get a pass unless Lens accepts the reason.
Enforced by Lens's review
Lens accepts each one only when the PR names it and why the behaviour it checked is gone.
The agents who build don't edit the tests they're judged by.
Guidance only: a hook in each session, which a shell command can get around
builders can't rewrite the checks their work is judged by
Every session acts on GitHub as Ruslan, so a pull request that passed on his approval is left for him to merge by hand.
Guidance only: the crew's own merge script
Sessions reach GitHub as the owner, so they could post that approval too: merge.mjs leaves such a PR for the owner to merge by hand.