trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
Later
272 of 454 done
deferred · 182 open · 41 merged in 7 days · moved
Deferred (filed under Later): the crew picks nothing beneath it until it is resumed, so there is no pace to estimate from.
Limbs
-
A deploy's build as a cluster Job 5 of 5 done
-
Old reviewed-pull posts say the verdict too 0 of 0 done
Merged in 7 days
- The board's money line names the Economics slider's position, linked to Settings → Economics
- The board shows this month's money in one line: cost, revenue and the gap, with a link to Economics
- The board's money line: cost, revenue and the gap, per forge and per app, today and this month
41 more merged
- A team's page shows how it coordinates: throughput, lead time, hand-off latency, rework and cost per shipped change
- The fleet graph is reachable: the board, the spend page and each app's page link to /fleet/graph with their selection
- When the forge's own lag explains most of an app's wait, the app's page does not call the app slow
- MCP `fleet`: query and act with dry-run by default
- The loopback-only looks test runs in the forge's check and says what Chrome does there
- Disk health rules: a spec catalog and alerts only on what the drive itself reports
- The packs' upstreams are read-only forge mirrors under the packs owner, re-synced on a schedule
- Revenue: awake time, storage and crew spend with the margin, per app per month — the statement billing reads
- src/spawn/pod.ts renders a child forge's namespace, quota, PVC, Deployment and default-deny policies, from pull #3743's branch
- What a forge costs: owned metal amortised, cloud per hour, storage per GB-month, and crew spend — one cost model
- Placement policy: owned capacity first, burst spills to cloud above the slider's threshold
- A run's summary is one escaped, clamped line wherever a row shows it
- Repo transfer, step two: git over HTTPS and SSH, running runs, previews and forks follow a moved repository
- Sleep windows follow the slider: the runtime reads its idle windows from the position, live
- Fleet page UI: select many, preview, confirm, receipt — fast and transparent on desk and phone
- Prompt a business: Atlas turns a description into a map of apps and adapters, as issues
- Fleet queries grow comparisons and age: `cost:>0.5`, `created:<7d`, `state:queued,running`
- The profit slider's position: one number per forge, and the pure function from position to policy
- A writer can run an adapter's pull now through the API and MCP, without waiting for its schedule
- Teams drive the crew: a membership carries a role, and a repository's crew is the members of the teams that can write it
- App page shows an adapter's last pull, next pull and cursor
- docs/ADAPTERS.md's Status says what runs today: the forge calls /pull on schedule and records each run
- The forge's scheduled /pull to an adapter carries the signed admin identity, so the template accepts it
- Repo transfer, step one: `POST …/transfer {newOwner}` moves the repository's rows and storage, and old web and API paths answer 308
- /fleet: a server-rendered table of what today's selection grammar selects, with the query line in the URL
- The forge calls each running adapter's /pull on its schedule and records the run
- An example adapter app answers an idempotent POST /pull and refuses hosts outside its source
- A pull run records an adapter's /pull answer: counts, cursor and duration, validated at the boundary
- A manifest can declare an adapter with its pull schedule, read and checked by src/apps/adapter.ts
- docs/ADAPTERS.md says what an adapter answers and what the forge checks
- The studio's three lists disagree: one header, and two dead filters
- When a pull lands, its head's looks are kept as main's looks for each page, width and theme
- The pull page speaks the home page's language, with looks before and after
- Data explorer: a model fallback for sentences the rules cannot read
- Share cards speak the home page's type and restraint, and each is checked as an image
- The flows view shows every line in and out: dependencies with advisories, origins, followed sources, forks, followers, mirrors and forges that follow
- docs/DESIGN.md opens with the design principles in under 30 lines, with the home page and Security settings as worked examples
- The Absorb findings are written up for Ben in one short note, ready for the owner to send
- The data explorer is easy: start from a question, not from a query form
- `discover` and `provider forge` work against a 0.5.x forge, proven by a fixture of its answers
- The security machine's brief and environment name only the tools actually on PATH, and say which are missing
Issues
131 more open
-
Resolve conflicts block by block in the terminal #1408 deferred
-
Cut a wave through MCP and the terminal, not only Settings #1550 deferred
-
MCP tools to list, add, grant and remove crew SSH devices #3685 deferred
-
First agent forge: grokbot (from #3687) #3705 deferred
-
LFS door: batch API and locks on the BlobStore #4493 deferred
-
Cold tier: lifecycle rules for packs and backups #4494 deferred
-
Finished run logs archive to the BlobStore #4545 deferred
-
Toast and skeleton parts in ui.ts, shown in the gallery #6010 deferred
-
Clog note: measure time to detect #6757 deferred
-
Find what fills the check machine disk (follow-up to #6945) #6947 deferred
-
trevato/forge #7635 deferred
106 closed
-
could we make building apps super fast?? #8 not doing
-
First two adapters: real syncs from the owner's businesses #438 not doing
-
Open the pull at the agent's first push, not when the run ends #1049 not doing