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
- Fast studio, part 2: the studio's counts, tails and front-door news run in one forge, under budget, in test/studio-front-door.test.ts P0 Trust
- Fast studio, part 1: the studio's pages and live fragment run in one forge, under budget, in test/studio-pages.test.ts P0 Trust
- Fast test/apps-token.test.ts: chop and rewrite under the budget (1 s a test, 10 s a file)
- Fast test/apps-adversarial.test.ts: chop and rewrite under the budget (1 s a test, 10 s a file) Later
- Review is owed from the check's green, not the preview's: a slow check queue lapsed every pull to a person tonight Later
- Losing the runner slows the gate and never blocks a release of a fix Later
- The edge answers when the forge does not: a static "the forge is restarting" page and the last Resilience page, served by the Worker itself Later
- The cockpit: board and map as one screen, driven by four keys, readable from a TV, with nothing that needs you that a rule could answer Later
- Looks that work well: a failed picture is retried, a sleeping app says so, a card says why it has no picture, and the thumbs are the ones the owner would choose Later
- A dataset as we go: the forge's events, decisions, runs, checks and usage exported as a documented, growing dataset the crew can learn from P8 Story
- The cache spectrum, chosen on purpose: in-process snapshots, SQLite, the edge's own cache, and a global read-cheap config pushed to the edge in seconds; offered to apps Later P9 Multiplayer
- A pull's green is the merge's green: checks run on the merge with its base, a conflict is said first, and a stale green never reads as ready P0 Trust
- A long-running services kind: declared ports, always on, placed on the owner's hardware, for a Minecraft network and its websites Later P9 Multiplayer
- Multiplayer and sync as forge primitives: an ordered change stream per app, rooms and presence, zero dependencies Later P9 Multiplayer
- Reply and like on a post are git primitives: a reply is a comment on its issue or pull, a like is a signal in the decision ledger Later
- Distilled posts: a wave or a milestone that landed goes out as one short post on X, read before it goes if the owner wants P8 Story
- P8 Story: waves, a changelog worth reading, milestones you can watch move, and distilled posts P8 Story
- Decision: identity is the forge's own, one authorization server, with open-platform.sh sign-in linked during the migration P0 Trust
- Spawn with config: a forge from a declarative recipe (apps and their modes, budget, admin, domain), saved and reusable P4 Forge in a link
- Cut-over: move an app's domain from the platform to the forge with a preview check, a receipt and one-step undo P4 Forge in a link
- Data migration: a platform app's Postgres goes into the drop and then into the forge app's store, with a receipt P4 Forge in a link
- Platform inventory: every app the owner has on the platform, what it holds, and its migration state P4 Forge in a link
- The drop: a private place per app and per forge to dump reference material the migration crew can read P4 Forge in a link
- Autonomous migration mode: an app from the platform gets a crew whose standing job is parity, shown as a checklist P4 Forge in a link