Verify this release.
A pull request fetched, reset to its merge base, tested in a sandbox and reviewed by a model that did not write it.
What you give it.
A sentence, and what the Brain already holds. Boomship asks for a repository or a file only when the Mission needs one.
Verify pull request northstar/web#128 before I merge it.
Northstar Supply, a fictional company · Illustration
What it does with it.
Each step names what it makes. Every step that ran is on the receipt; one that could not run is written as not run.
- 01Fetch the pull requesta checkout reset to the merge base, so the diff is exactly the PR
- 02Install with scripts disableda sandbox with no network and no token
- 03Run the checksfresh tests, a typecheck, a secret scan
- 04Review it independentlya verdict from a model the author did not use
- 05Write the receiptpass, concerns or fail, with findings
What comes back.
- A Work Receipt with a verdict and up to twelve findings, each with a file
- An adversarial security review when the change is high or critical risk
- Nothing merged, nothing pushed
What it needs connected.
Each one says how it connects and what Boomship may do with it. A connection on its own puts nothing into a Mission; only what you add to a project’s Files does.
Where you come in.
A steer is received at the next turn. A failed check holds a chain. The merge is a button Boomship does not press.
- Reviewwhen the receipt arrives
A verdict of concerns or fail names the files. You decide what it means.
- Mergeat the end
Boomship does not merge. The button stays yours.