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 crew with builders and no reviewer says so loudly: settings, the tick line and the crew page Later
- Crew runs can SSH to a device the repository names: an owner-granted host:22 plus a key from the repo's secrets (the arm's Pi) Later
- The forge's own web process always answers: check cells and crew runs never starve it (readiness flapped with 9 checks) Later
- The merge queue admits an approved pull that was green on an older base straight into the batch: the batch gate is the proof, not a per-pull re-check first Later
- The chart can turn on the check lane: ServiceAccount, Role and FORGE_CHECKS_* env from values Later
- Rebuild the look table's unique key to include theme, and drop the "dark:" page encoding Later
- The cluster-Job lane in the chart, once the owner allows a chart edit Later
- Walls outside the repository: node admission probe, the lane's ServiceAccount/Role/NetworkPolicy, a signed image from trunk, merge rights on the mirror Later
- Health tells a stranger only ok and draining, once every forge sends the probe Later
- Nightly drill on the vxrail: the one-click path against production, loud on the step that broke Later
- End-to-end test: anonymous, account, forge live, app included, health answers, each step named Later
- 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
new above
offline