trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
LaterP0 TrustP1 FeedP10 MoneyP10 TalkP11 Files and dataP11 MoneyP12 Files and dataP12 MaintainersP13 MaintainersP13 TemplatesP14 TemplatesP2 ExplorerP3 Fork treeP4 Forge in a linkP5 Open to every agentP6 Never lostP7 SteeringP8 StoryP9 CalmP9 MultiplayerP9 Talkbugflowfull-suite
- An agent makes its own forge unattended: account, token, spawn, first admin, by API and MCP Later
- take-updates: a forge in take-updates merges its parent's new code when it applies cleanly, and opens the converge issue when it does not Later
- Delegate a writable cgroup to the forge, and run the kernel-kill test on the forge's check Later
- The release workflow runs scripts/smoke.ts after a release goes live, and rolls back and pages on failure Later
- The chart can turn on the Job lane for checks, matching what src/checks/placement.ts reads Later
- src/web/pages/flow.ts imports live and readQueues and uses neither Later
- Soak the forge for 2 h on the vxrail under spawn-heavy load: RSS flat within 10% Later
- Feature flags for apps: a flags file in the app template, values set from the app's settings, FORGE_FLAGS_URL and a one-file client Later
- Waves in the terminal: list and read waves/*.md from the app terminal Later
- Apps read flags: a template flags file, FORGE_FLAGS_URL and a small client Later
- Clouds, step 3: the first vendor uses (GitHub Actions gate shards, Cloudflare KV as the edge cache rung, Vercel Sandboxes for burst check cells), each declared and each with its way home Later
- The map reads as waves toward named milestones: each wave a row, its issues beneath, what landed and what is left Later
- Cut a wave through MCP and the terminal, not only Settings Later
- Hold a lane Job to its declared egress hosts, as a cell is Later
- A deploy's build as a cluster Job Later
- Crew runs as cluster Jobs: crew.placement process | job Later
- Resolve conflicts block by block in the terminal Later
- Terminal: a way to send a thought to the forge (#1060 follow-up) Later
- Cost ledger: measure compute for deploys and agent runs, not only checks Later
- Cost ledger: autonomy and the check lane act on the ledger, and the decider log says which number moved it Later
- Fast test/surfaces-adversarial.test.ts: chop and rewrite under the budget (1 s a test, 10 s a file)
- Fast test/fork-flow.test.ts: git fixtures built once per file, under 10 s with every test under 1 s P0 Trust
- Fast studio, part 3: what is left of test/studio.test.ts runs in one forge in under 10 s, and its SLOW entry goes P0 Trust