trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
P0 Trust ✕
LaterP1 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 rollback records how long it took, and the release card shows it beside the stage timings P0 Trust
- A cut waits up to five minutes for running crew runs to finish, and the tick says how many it waited on P0 Trust working ·
- Each release counts the crew runs it interrupted, and the release card shows the number P0 Trust working ·
- A release whose tree covers the page is refused before the swap, and the tick names the rule P0 Trust working ·
- The Deployment-patch release deployer prunes old release images through the ReleaseStore port #11801 adds P0 Trust
- /flow lists the pulls closed unmerged because a check was stopped for CPU, so a person can re-queue them P0 Trust working ·
- A release tick not heard from for 60 minutes fires one release_quiet flow alarm P0 Trust working ·
- Every cookie the forge sets is HttpOnly, SameSite and Secure behind HTTPS: one test finds each place it sets one P0 Trust working ·
- Every admin-only action refuses the everyday account's session: one test walks the route table and names any that does not P0 Trust working ·
- The thirty-minute proof: pg-grand cordoned and stopped, the forge answers, signs in, lands, releases and fires a schedule P0 Trust
- The forge's data is backed up encrypted to object storage on neither machine, and a restore is drilled P0 Trust working ·
- The forge's addresses go tunnel → the forge's Service on the vxrail, with no Traefik and no pg-grand in the path P0 Trust
- The release step prunes old release images itself: the newest 15, the live one and the known-good rollback are kept P0 Trust working ·
- bench/results holds a 500/s run of anonymous code pages through the edge cache and one bypassing it, both with zero refusals and p95 under 100 ms P0 Trust
- The forge box comes back by itself after a killed process and a reboot, and a drill proves it P0 Trust working ·
- A trusted source's pull lands by true merge when its checks pass, with no review, credited in the changelog and the live stream P0 Trust
- Fast test/fork-flow.test.ts: git fixtures built once per file, under 10 s with every test under 1 s P0 Trust
- Fast studio, part 3: what is left of test/studio.test.ts runs in one forge in under 10 s, and its SLOW entry goes P0 Trust
- 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
- 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
- Decision: identity is the forge's own, one authorization server, with open-platform.sh sign-in linked during the migration P0 Trust
new above
offline