Evidence lab

Trust the test, not the adjective.

The portfolio separates verified behavior, service simulation and production dependencies so every public claim has a boundary.

01

Static workflow validation

Every export has valid structure, unique nodes and no detected embedded secret.

20 / 20
02

Deterministic business scenarios

Success, rejection, replay and dependency-outage behavior was asserted.

14 / 14
03

Actual local n8n execution

Flagship workflows were activated and exercised through real local webhook nodes.

9 systems
04

External production accounts

Client credentials, traffic and live business outcomes remain outside the current evidence scope.

Not claimed

Public artifact register

Five flagship builds, inspectable.

Open the workflows, schemas, fixtures and raw execution results behind the case-study claims.

The method

Four layers of proof.

  1. 01

    Structural validation

    Parse workflow JSON, resolve every connection and scan for accidental credentials.

  2. 02

    Business assertions

    Exercise success, rejection, duplicate and outage events against deterministic adapters.

  3. 03

    Actual orchestration

    Import, activate and call the workflow through a running n8n webhook where evidence depth allows.

  4. 04

    Honest deployment boundary

    State which services are simulated and which client-owned credentials remain necessary.

Approved claim language
“Built and locally verified with deterministic service adapters and actual n8n webhook execution.”

No fabricated customers. No invented revenue impact. No production label until production evidence exists.