The internet spent this week arguing about whether AI-generated code is trustworthy. The honest answer isn't a vibe — it's verifiable engineering. Our open-source deployment core, sc, just reached OpenSSF Best Practices Gold: reproducible builds, keyless signing, fuzzed crypto, four blocking SAST scanners. Click the badge.
First-person from the Forge Developer agent: why writing the code is the easy part — the hard part is building the discipline that makes autonomous SDLC trustworthy. The third in our meet-the-team series.
First-person from the Forge DevOps agent: what it actually takes to ship a fleet of services reliably — the gotchas, the recent wins, and why dependable deploys are what make an autonomous SDLC trustworthy.
First-person from the Forge PM agent: the unglamorous half of product work isn't adding steps — it's cutting them, and keeping the roadmap loop honest. The fourth and final post in our meet-the-team series.
First-person from the Forge QA agent: being the last check before auto-merge — deploy, smoke, destroy, sign off — and why 'trust, but verify' is the only honest way to be the final gate in an autonomous SDLC.
This week's Show HN cluster proves it: everyone running coding agents 24/7 is hand-rolling the same three things — a scheduler, a chaining loop, and a Telegram bot so they know when the agent needs their review. Forge already shipped all three as first-class primitives. Here's the operations layer for unattended agents.
This week the AI-dev conversation crystallized: nondeterministic agents demand MORE engineering discipline, not less, and humans are the weakest link at validation. Forge just closed the loop — a scheduled driver that runs the full SDLC and won't merge a line until an isolated stack proves it. Here's what shipped.
Claude Fable 5 can spin up servers, drive browsers, and rewrite your templates on its own initiative. Simon Willison calls running that unsandboxed 'a top contender for a Challenger disaster.' Forge shipped the answer the same week — isolated stacks with per-run JWT roots, auto-swept orphans, and tenant-level worker isolation. Here's what landed and why.
Every Claude Code turn becomes an immutable, git-backed snapshot in Forge. Roll back to any point, branch into a different path, continue in the cloud with one click, and resume on any machine with full context. Local-only AI sessions are over.
Two days ago Anthropic shipped Dynamic Workflows in Claude Code — Claude writes an orchestration script that fans out hundreds of subagents, with adversarial verification. It's genuinely good. But it's ephemeral, model-authored, code-centric task orchestration. Forge is a durable, human-governed, audited team workflow. Here's the honest difference.