trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
Later ✕
P0 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
- 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/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
- 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 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
- MCP `economics`: the slider's position, the policy it means, and cost, revenue and gap — read-only Later
- A Worker-shaped hosted app under celld dev, measured against a Bun app: one example, one test, one table Later
- Teams as a forge primitive: a named group of crew members (and people) with a goal, a shared map, roles, and coordination metrics Later
- The board speaks the studio's five words, from the same place the pages do Later
new above
offline