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-suiteoutsidered-only-in-full-suite
- A Data tab: every app's databases in the web, and the forge's own at /admin/data — table list, sortable paged rows, filters, a read-only SQL box P11 Files and data P12 Files and data
- Data browser core: read any SQLite file a viewer may see — the forge's own (admins) and each app's per environment (its writers) — tables, rows, read-only SQL, secrets masked P11 Files and data P12 Files and data
- Evict the shared check install cache by age or size (<data>/check-install/<repo>/bun)
- A read-only data browser for admins: browse and query the forge's database from the forge
- A fix the owner or steward writes lands through the queue as is: an in-repo pull is gated and landed, not closed for being off a fork Later
- Builder slots serve the roadmap first: tests-only and small-addition pulls get at most a set share of builder slots P0 Trust
- Escalate to Opus by need, not by agent: P0s, planning, and any pull sent back twice run on Opus; everything else on the agent's own model P0 Trust
- P0: OAuth consent is refused (the consent page's no-referrer makes its own POST Origin: null) — cherry-pick steward/consent-origin P0 Trust
- Rule watcher: gate-only reds, rule breakers with exact fixes, flaky and load-sensitive budget tests P12 Maintainers P13 Maintainers
- Performance watcher: Server-Timing budgets for home, boards and repo pages from real traffic, slow phase filed with numbers Later
- Efficiency watcher: network bytes and cache hit rates by cause, filed when a cost doubles P12 Maintainers P13 Maintainers
- Release keeper: cut on cadence, verify under page load, roll back to the named known-good version, hold with a reason Later flow
- Flow keeper: stuck, conflicted and wrongly held pulls, rebase loops, lulls and forge-down, acted on instead of alarmed P12 Maintainers P13 Maintainers
- Batch doctor: on a red merge batch, find the culprit, tell load reds from real ones, hold with the exact failing test P12 Maintainers P13 Maintainers
- The forge reports npm registry bytes per hour, so the steward can see the bun cache working P0 Trust
- Check run homes (/data/checks/*.home) are removed when their run ends or dies, not only at the next boot P0 Trust
- App previews install from the repository's shared bun cache, so a new preview environment downloads nothing it already has P0 Trust
- Contained checks and gates install from the repository's shared bun cache, filled by the forge and bound read-only into the cell P0 Trust
new above
offline