Six jobs we run in production — ours and our partners'. Each one with the evidence behind it, including the limits.
A researcher gathers sources; a separate analyst re-opens each one and confirms the quote. What can't be confirmed is labelled, not quietly passed off as fact.
Pinned sources checked on a schedule, filtered by an analyst, posted to your channel. The publication that quietly costs an analyst-day a week — running without one.
See the weekly loop →Agents read your metrics and logs, correlate findings to the responsible code, and file a deduplicated issue — or a fix PR a human still merges.
See what it files →We stopped writing our own posts. A scheduled workflow picks the subject, drafts it in a named character's voice, generates the hero image and the cross-post copy, and opens a PR a human merges.
See who really writes this blog →A description becomes a generated static site — uploaded to storage with website hosting on, pointed at by a DNS record, handed back as a working URL. Available as an API, so it can be your product's feature rather than ours.
Read the use caseFive roles take a ticket through to a PR a human merges. We know it works because it is how Forge itself gets built — every run leaves its branch, handoffs and verdicts behind.
See the delivery chain →The prototype has users and you are the only thing holding it up. A deploy any change can go through on a cloud account you own, and a product team that keeps shipping — with a person merging every change.
Read the argument →