GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
GeezerVison is showing forgecode.dev — ForgeCode: your software factory Your software factory. |
| Issue | Status | Priority | Runs | Updated |
|---|---|---|---|---|
| LRK-412Token bucket store on Redis with per-key TTL | Done | High | Idle | 02:14 |
| LRK-413Middleware: 429 with Retry-After and RateLimit-* headers | In Progress | High | Running | now |
| LRK-414Per-tenant overrides read from the plans table | In Progress | Medium | Running | now |
| LRK-415Load test: 12k rps burst, p99 under 40 ms | To Do | Medium | Blocked by 413 | 01:52 |
| LRK-416Docs: rate limits page and SDK retry examples | To Do | Low | Idle | 01:52 |
Set it up once. It keeps shipping
What a normal day looks like, three months after setup.
Priya mentions @ForgeCode in a Slack thread
Gateway p99 back to normal after the 08:00 spike.
Rate limiter is still the old in-memory one...
1 reply Last reply 9:16 AMRate limiter is still the old in-memory one, so it resets on every deploy and customers on the Scale plan keep hitting 429s at 08:00 UTC. @ForgeCode rewrite it on Redis, keep the public headers, per-tenant overrides from the plans table, and load test it before you open a PR.
On it. Opened mission LRK-410 on larkspur-cloud-1 with 5 issues. I will report back in this thread when a PR is ready.
| Issue | Status | Priority | Runs | Updated |
|---|---|---|---|---|
| LRK-412Token bucket store on Redis with per-key TTL | In Progress | High | Running | 09:16 |
| LRK-413Middleware: 429 with Retry-After and RateLimit-* headers | In Progress | High | Running | 09:16 |
| LRK-414Per-tenant overrides read from the plans table | In Progress | Medium | Running | 09:16 |
| LRK-415Load test: 12k rps burst, p99 under 40 ms | To Do | Medium | Blocked by 412, 413 | 09:16 |
| LRK-416Docs: rate limits page and SDK retry examples | To Do | Low | Idle | 09:16 |
| LRK-412Token bucket store | Done |
| LRK-413Middleware: 429 + headers | In Progress |
| LRK-414Per-tenant overrides | In Progress |
| LRK-415Load test 12k rps | To Do |
| LRK-416Docs and SDK retries | To Do |
Gateway p99 back to normal after the 08:00 spike.
Rate limiter is still the old in-memory one...
2 replies Last reply 6:32 PMRate limiter is still the old in-memory one... rewrite it on Redis, keep the public headers, per-tenant overrides, load test before you open a PR.
PR #1187 is ready for review. 4 of 5 issues done; LRK-416 (docs) is open in review for you.
- Redis token bucket with per-key TTL, 0 allocations on the hot path
- 429 responses carry Retry-After (integer seconds) and RateLimit-Limit / Remaining / Reset
- Tenant overrides read from
plans.rate_limit_rps, cached 30s - Load test: 12,400 rps burst for 5 min, p99 31 ms, 0 dropped
31 files, +1,412 / -688. Tests 212 passed. Clippy clean. Reviewer agent: 2 findings fixed before opening. Merge policy for this repo is ask me, so #1187 waits for you. Want a walkthrough of the Redis bucket before you review? Reply here and I will post one.
| Title | Trigger | Last run | Next run |
|---|---|---|---|
| Production alert: open incident, find root cause, open PR | alert sentry prod | 02:10 | on alert |
| Nudge stalled issues: rerun from checkpoint after 6h idle | watch: issue idle 6h | 03:35 | on stall |
| Remind reviewer when a PR waits more than 8h | watch: PR waiting 8h | 07:00 | on wait |
| GitHub bug report: triage, reproduce, open issue | github issues | Mon 16:48 | on event |
| Forum post tagged bug: reproduce and reply | forum discourse | Mon 11:02 | on post |
| Slack message in #api-platform | slack @ForgeCode | 09:14 | on message |
| Nightly flaky test sweep, escalate if above 1% | schedule 02:00 | 02:00 | Thu 02:00 |
NullPointer in billing/invoice.rs:212, 38 events in 4 min. LRK-419 opened.02:33 RCA: refunded invoices have no customer since PR #1174 dropped the join. PR #1188 opened; merge policy
merge when gates pass for hotfix/*: merged 02:41.02:44 posted for Dev Okonkwo (owns billing): what changed, why, and how to verify.
| Issue | Status | Priority | Runs | Updated |
|---|---|---|---|---|
| LRK-412Token bucket store on Redis with per-key TTL | Done | High | Idle | 11:02 |
| LRK-413Middleware: 429 with Retry-After and RateLimit-* headers | Done | High | Idle | 12:48 |
| LRK-414Per-tenant overrides read from the plans table | Done | Medium | Idle | 15:20 |
| LRK-415Load test: 12k rps burst, p99 under 40 ms | Done | Medium | Idle | 18:19 |
| LRK-416Docs: rate limits page and SDK retry examples | In Review | Low | Idle | 18:31 |
| LRK-419Incident: NullPointer in billing/invoice.rs (alert). PR #1188 merged by factory | Done | High | Idle | 02:41 |
- Tests: 212 passed
- Clippy: 0 warnings
- Load test: p99 31 ms
- Security scan: 0 findings
- Staging smoke: 18 of 18
- Reviewer agent: 2 fixed
sent to #eng-leads 07:05Done Public API rate limiter rebuilt on Redis. Load tested at 12,400 rps, p99 31 ms.
Fixed Billing NullPointer from PR #1174. Hotfix merged under policy in 31 min.
Decide PR #1187 needs Priya's review to ship the rate limiter to Scale customers.
Better Flaky tests down to 0.6% from 1.4%. Review nudges now fire after 4h.
Next Thursday 02:00: Postgres 16 upgrade mission starts, merge policy ask me.
A coding harness makes one developer faster.
A factory raises organisational velocity
Your factory, your terms
Run factories on ForgeCode's cloud or bring your own cloud (BYOC), and bring your own model keys.
What teams run on a factory
Whole engineering roles and long-running programs, not single tasks.
Own every alert for a quarter
Each page becomes a root cause, a fix PR, a postmortem and a new guardrail in your gates. Merging follows your policy.
- ALR-2291p99 latency, checkout-api
- RCAN+1 query in cart totals
- PR #4417batched query, gates pass
- postmortemsent to owner, Slack #payments
- guardrailquery count check added to gates
- Q3 alerts
- 214
- resolved, no human paged
- 197
- median alert to PR
- 19 min
Every bug report gets a repro and a fix
GitHub issues and forum posts are deduplicated, reproduced as a failing test, fixed, and answered where they were reported.
- #3120webhook signature fails for keys with "+"
- dedupelinked forum post and #3098
- reprofailing test: base64 key decoding
- PR #5208url-safe decode, gates pass
- repliedon #3120 and the forum thread
- reports this month
- 286
- duplicates linked
- 61
- median report to PR
- 41 min
A PRD becomes a shipped, monitored feature
A Linear epic turns into one mission: API, migrations, UI, tests, docs and a flagged rollout run as parallel issues, then watched after deploy.
- issues
- 24
- parallel
- 5
- spec to 100% rollout
- 9 days
REST to GraphQL without a code freeze
Planned as a mission, landed as hundreds of small reviewed PRs, each one behind your gates.
- PRs merged
- 388
- median PR size
- 84 lines
- reverts
- 2
Be the QA team
Writes and maintains the suite, adds end to end tests for every PR, and reproduces every bug report as a failing test before fixing it.
- coverage61% → 84%goal 80%
- flake rate4.1% → 0.3%goal < 0.5%
- bugs reproduced first143 / 143this quarter
Run the platform team's backlog
Keeps CI fast, main green, and dependencies and toolchains current across every repo.
- CI build time23 → 9 mingoal 10 min
- repos current46 / 46weekly
- main red per week5.6 h → 25 mingoal 1 h
Patch advisories across every repo
A new advisory opens one mission with an issue per affected repo; each PR runs your SAST and tests before it asks for review.
- advisoryXML parser, 14 repos affected
- mission14 issues, one per repo
- 14 PRstests and SAST pass
- 12 merged2 waiting on code owners
- advisories this quarter
- 37
- median advisory to patch
- 6 h
- goal
- 24 h
Cut, verify and roll out every release
Writes the changelog from merged PRs, ships to a canary, watches error rates and rolls forward or back under your release policy.
- changelogdrafted from 63 merged PRs
- canary 5%error rate 0.02%, p99 steady
- 50%no regressions in 30 min
- 100%release notes posted to #deploys
- releases per week
- 11
- automatic rollbacks
- 2
- manual steps
- 0
Keep p99 and bundle size under budget
Profiles hot paths, fixes regressions in the PR that caused them, and adds a benchmark to the gates so they stay fixed.
- checkout p99480 → 190 msgoal 250 ms
- web bundle1.9 → 1.1 MBgoal 1.2 MB
- regressions caught in PR23this quarter
Docs and SDKs follow every API change
An API change regenerates the SDKs, tests every code sample and updates the reference before the PR merges.
- OpenAPI diffnew field: invoice.tax_breakdown
- SDKsTypeScript, Python, Go regenerated
- samples48 code samples run and pass
- docsreference and changelog updated
- stale doc pages
- 0 / 412
- SDK languages
- 3
- API change to SDK
- 2 h
Retire the legacy ORM, one call site at a time
Debt that never makes the sprint gets a mission of its own and lands as small PRs that each pass the gates.
- PRs merged
- 214
- dead code removed
- 38k lines
- reverts
- 0
Reach WCAG AA and stay there
Audits every page, fixes contrast, labels and keyboard paths, then adds an axe check to the gates for every new PR.
- axe violations412 → 9goal 0 serious
- keyboard reachable pages58 / 58all routes
- contrast fixes133light and dark
Book a demo to discuss yours
Bring the work your team never gets to; we map it to triggers, automations and gates on a factory with you.
- feature flag cleanup
- i18n string sync
- schema drift checks
- flaky test quarantine
- license audits
- API deprecations
- on-call handoff notes
- cost alerts to PRs
- test data refresh
- Terraform drift
- mobile crash triage
- SLO reports
01 / 12paused
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.