Promtact Enterprise

See a failure become a test.

Promtact runs the behavior that matters under deterministic virtual time and declared faults. If a property fails, the seed, step and trace turn that execution into a result another engineer can run again.

seed: 0x4A2C
step: 318
trace: 7B3A
result: violation reproduced

Verification model

Four explicit parts

Connect the behavior that matters, state the safety boundary, choose the faults and preserve the resulting execution.

System

Adapt the messages, nodes and transitions inside the verification boundary.

Properties

Evaluate invariants after each step and name the exact violation.

Faults

Exercise partitions, isolation, one-way links and bounded fault windows.

Evidence

Retain the seed, step, trace, version and bounded result for replay and review.

Concrete input

A scenario is reviewable data

Version the seed, node count, step budget and declared faults. The same input can run locally, in controlled CI and during review.

{
  "seed": "0x4A2C",
  "nodes": 5,
  "steps": 1200,
  "faults": [{
    "type": "split",
    "start": 200,
    "end": 700
  }]
}

Operating boundary

Self-hosted and explicit about its limits

Execution remains in the customer environment. A result establishes only the properties, faults, versions and execution boundary recorded with it; it is not a blanket proof that a system cannot fail.