The ZPX Forge methodology

Build with your coding agent.
Ship with evidence.

Forge is a product observability and control system for product creators and coding agents. Its expert-designed methodology guides each release with Claude Code, Codex or Agy.

zpxforge.com/e/customer-portal/v2-4

Sample

Customer portal

v2.4 · Production release

Verified by ZPX Forge

4 observed · 1 accepted risk · 1 declared

  • ✓

    Each customer only sees their own data

    CI #482 · test_tenant_isolation
    ● Observed
  • ✓

    A payment is never charged twice

    CI #482 · test_idempotent_payments
    ● Observed
  • ✓

    Only admins can delete records

    CI #482 · test_permissions
    ● Observed
  • ✓

    Data migrations can be rolled back

    CI #482 · test_migration_rollback
    ● Observed
  • ◆

    Backup restore not yet tested

    Laura M. accepts it for this release · reason visible
    ◆ Accepted risk
  • ◯

    Retries when an external service fails

    Claimed by the agent · no evidence
    ○ Declared

Works with the agents and CI you already use

Claude CodeCodexCursorGitHub CopilotOpenCodeGitHub Actions

Working method

From an idea to a product you can operate.

Avoid AI slop by agreeing with your agent on the problem each change solves. Make scalability and observability testable. Agree on how many orders per minute the system must handle, which alert fires if orders stop and who responds. The project retains that plan and its acceptance criteria.

Templates that evolve with the models

When a model changes, the Forge team reviews the practices it affects. Improvements are tested and published as harness revisions. The CLI flags updates for your project so Claude and Codex work from the same rules.

01BeforeGuide

Decide what to build, and on what foundations.

Start with an idea or your repository. Forge scopes a first version with you, applies the blueprint for your kind of system and gives your agent the rules and criteria from the first commit.

  • Guided scope: what’s in, what can wait and what’s essential
  • Blueprints per system type: multi-tenant SaaS, integrations, payments
  • CLI · local environment file and workflow inventory
Scope · v1.0✓ Approved

“I want a portal where my customers check their orders and pay their invoices.”

In
Sign-in, orders and invoices
Can wait
Online payments
Essential
Each customer only sees their own data
Blueprint
Multi-tenant SaaS · 5 criteria

→ First task sent to Ana’s Claude Code

02DuringGuardrails

Your agent builds. Forge sets the guardrails.

Every developer works with their own Claude Code, Codex or Cursor, on their own machine. Forge classifies each task by risk, scales review to what’s at stake and shows the team what every agent is doing.

  • Tasks by area, size and risk
  • Adversarial review on data, security and payments
  • Every finding explained in plain language, for any level
Board · live 3 agents
  • Online payments

    api · M · R2 · Claude · Ana → verifier
    Verifying
  • Customer isolation

    data · S · R3 · Codex · Luis → reviewer + challenger
    Adversarial review
  • Orders screen

    ui · S · R1 · Cursor · Sara
    Safe vibe coding

R3 Automatic adversarial review before merge. You approve in one click.

03Release assurancePro

Check in your CI and ship with evidence.

Forge reads the agreed test result from GitHub for the release commit. Customers can inspect the sheet and accept that version or request a correction.

  • Observed evidence, tied to the commit
  • Changes to the agreed test require a new review
  • A verified link, immutable and revocable
# .github/workflows/forge.yml
- name: Verify customer isolation
  run: pytest tests/test_isolation.py
# Forge checks this step for the agreed commit
✓ Verified by ZPX Forge

zpxforge.com/e/customer-portal/v2-4

a1b2c3f · CI #482 · 4 observed · 0 regressions

Release assurance · Pro

Your customer deserves an independent check.

If your agent says customers can only see their own orders, how can the person receiving the portal check? Forge reads the agreed test result from GitHub for the delivered commit. The release sheet shows the result, accepted risks and open claims so the customer can decide.

What your agent reports

✓ Implemented customer isolation.
✓ All tests pass.
✓ Ready for production.
○ Declared

What Forge saw

  • test_tenant_isolationpassed · CI #517 · e5f6a7d
  • test_isolation_reportsfailed · CI #517 · e5f6a7d
  • Data recoveryverification pending
● Observed

Every claim says where it comes from

● Observed

Forge checked the run, job and test step for that commit on GitHub.

◆ Accepted risk

Evidence is missing and the project owner chose to ship anyway. Their name and reason stay on record, visible to your client.

○ Declared

The agent or team claims it. Useful context, but it never earns a ✓ on its own.

Tracking

Every version, compared with the last.

Did we close what we promised? Did something that worked come back broken? What changed without a check? Forge answers before your client asks.

v2.5 · Blocked · Forge caught the regression before production

  • Regression

    Isolation: the new /reports endpoint doesn’t filter by customer

    reports/views.py · e5f6a7d · the test no longer covers it
  • New, unchecked

    Reports module has no checks

    4 files changed without evidence
  • Still passing

    A payment is never charged twice

    CI #517 · still green

Compared with v2.4.

Your code never leaves your CI.

See which permissions we ask for and why →
  • Checks run on your infrastructure. Forge receives results, not code.
  • Install the GitHub App only on the repos you choose and remove it any time.
  • Shared reports publish only what you approve. No private notes, no repo access.

Who it’s for

People pay for someone else’s trust.

Software factories

Hand every client something more convincing than a demo. “Our releases come verified” wins contracts, shortens acceptance and keeps one standard across all your projects.

In-house IT teams

Apply the same standards across every team and project. Tell what was observed from what was only claimed in your agents’ work, and show business, security and audit what was checked before each production release.

Founders

You don’t need to be an engineer. Forge explains every finding in plain language, tells your agent how to fix it and lets you show what you checked.

See pricing →

Ship software others can trust.

Individual includes one client (one company) and up to two solo projects, without team invitations. Pro costs US$10 per member and includes human support by email and unlimited teams, companies and projects.