Skip to content
Join the waitlist

Humans approve the decisions that matter.

Plan. Scope change. Merge. Evidence. Release. Five named gates. Five named approvers. Five ledger entries per mission.

Governance layer Audit trails
Trust · HITL · a gate on one mission
  1. Propose: Plan approval · Sign off the mission plan before agents start work.
  2. Review: Evidence review · Operator drills into raw evidence pack before signing.
  3. Reject: Rejection · Operator rejects with reason. Mission re-enters rework loop.
  4. Rework: Rework loop · Agent receives rejection context, retries with constraint.
  5. Approve: Humans approve the decisions that matter. Five named gates. Five named approvers.
  6. Run: Five ledger entries per mission.
Uptime 99.98%
Latency 14.2ms
Nodes 128/128
trust · live Armed · 0 breaches
  • armed · 0 breaches ytd
  • soc 2 · iso 27001 · nist ai rmf · hipaa · gdpr
  • hardware-token gates · 412 audits / hour
  • tenant isolation · cryptographic boundaries
  • replayable decisions · tamper-evident ledger
Approval points

Where you intervene.

A mission moves left to right. At each of these five points it stops until a named person signs.

  1. Gate 1 / 5

    Plan approval

    Sign off the mission plan before agents start work.

    ledger entry 1 / 5
  2. Gate 2 / 5

    Scope change approval

    Approve any mid-flight scope change; ledger-logged.

    ledger entry 2 / 5
  3. Gate 3 / 5

    Code merge approval

    Protected branches require named reviewer attestation.

    ledger entry 3 / 5
  4. Gate 4 / 5

    QA evidence approval

    Sign the evidence pack before release readiness.

    ledger entry 4 / 5
  5. Gate 5 / 5

    Release approval

    Hardware-token gate on production releases.

    ledger entry 5 / 5
Model

How overrides + rework work.

When a person disagrees with an agent, these are the four things that can happen, and each one is written down.

Override

Operator can override agent recommendation; override + reason logged.

  1. agent recommendation
  2. operator overrides
  3. override + reason logged

You hold the gate.

Walk one mission through its five gates as the approver. Nothing passes a gate until you approve it. Reject it, and the work goes back to the agent with your reason.

  1. Plan
  2. Scope change
  3. Merge
  4. Evidence
  5. Release
Agent proposal · gate 1 / 5

Plan approval

Sign off the mission plan before agents start work.

Start a Software Factory pilot.

Connect one repository, one ticketing tool, and one mission. See evidence in days, not quarters.

Book a pilot Join waitlist