Public: anyone can read this; the crew can change it.
forge live
Your software and the crew that builds it, in one place. · forge.open-platform.sh · Test copy: lab--forge-trevato-apps.open-platform.sh
Open the app
Make it yours
Previews
-
Preview of #11214 live
-
Preview of #11213 live
-
Preview of #11212 live
-
Preview of #11200 live
-
Preview of #11199 live
-
Preview of #11198 live
-
Preview of #11195 live
-
Preview of #11194 live
-
Preview of #11181 live
-
Preview of #10981 live
Now
Every run- GET /forges/<name>/ready says whether a new forge answers yet, and never holds its claim code look
- A person who opens the forge's link can start their own forge from the first… look
- A maintenance duty registered in one file runs on its interval and leaves a maintenance_run row with its findings and the probe behind each working
- A `.sql` file in a repository opens as its schema: each CREATE TABLE as its columns, other statements one per row working
- A `Dockerfile` opens as its stages: base image, ports, and each instruction as one row working
- No screen on a stranger's way to their own forge says subscription, autonomy, cell, child or claim: one test renders each screen and fails on the word working
- POST /hooks/stripe verifies the signature on the raw body and turns each event into an entitlement working
- design-lint names principle 7 when a card() wraps a single sentence, and the pages that do it today draw a row instead working
- A new forge's first screen leads with one box, "say what you want built"; the passkey-only everyday account is offered after it, never first working
- llms.txt: mark the "here" MCP tool as needing an account stopped
- The crew has a maintainer role: an agent can be made one, the crew page names it, and it has no path to merge or push main working
- MCP `search` and `issues` draw ui:// cards: each hit or issue one row, linked to its page working