THE FACTORYHow Rigel works
STEP 1
You design with your design lead.A design is a doc in the Library. When you approve it, it produces Issues.
STEP 2
Build agents make Changes.A Change replaces the pull request; a Chain is a stack of them. Agents have no shell: every capability is a tool, and code runs only on Runners.
STEP 3
Checks run where the code is.The planner runs fmt, lint, build and test for the Components a Change touches, on warm Runners, with a shared build cache.
STEP 4
Review, then Land.Review agents check every Change. The queue lands it on trunk.
STEP 5
GitHub stays in sync.Trunk mirrors to GitHub. A full-history git export of your trunk is a committed feature; its timing is not set.
ALSO
Open build toolingThe planner that runs every Component's build, test and lint tasks is open source under AGPL-3.0, so exported code builds without Rigel.