What you get
Only the sessions you name leave your machine
A session uploads only when you start it naming the work item it is for. Any other session stays on your machine.
See what each change cost
Open any pull request and see the agent sessions behind it, what they did, and what they cost.
A person approves before the merge
The item’s Merge pull request button stays disabled until a person approves. To block merges on GitHub too, see Policy and validators.
Agent instructions versioned and measured
The instruction files and skills your agents read are versioned, and session outcomes show whether a change to them made your agents better.
- Post session summaries on pull requests is on, so OuterLayer posts its
OuterLayer evidencecheck run. - The policy sets
merge_gate: on-flag. Under the default,none, the check is always neutral. - A GitHub branch protection rule requires the
OuterLayer evidencecheck.
Where to start
1
Get your first issue on the Work page
The quickstart takes about ten minutes. It ends with one of your issues built into a pull request, by a host or by a session you start.
2
Understand the launch gate
Launch a session explains the one rule that decides what uploads.
3
Bring your team
Invite your team covers adding people, each signed in on their own machine. To add another repository, see Connect a repository.