6 cases for configuration A + 6 for configuration B.
Synthetic / technical evidence
Same decision core. Two separate configurations. No shared decision thresholds.
This public example shows one e-commerce exception-routing core tested under two isolated configurations. No customer data was used. Every result belongs to a frozen synthetic acceptance set.
Evaluated with the same deterministic control sequence.
No production usage or second-pilot evidence is claimed.
Core
The decision sequence does not change
Configuration changes thresholds and permissions. It does not bypass the shared control sequence.
1Required fields
2Untrusted instruction
3Source conflict
4Source freshness
5Authority / threshold
6Approved route
Separate configuration
One core, different operating boundaries
Narrower currency scope and lower human-approval threshold
Data namespacespec-a
Allowed currencyTRY
Source freshness20 minutes
Human approvalAbove 500 units
Autonomous actionQueue only
Broader currency scope and a different approval threshold
Data namespacespec-b
Allowed currencyTRY + EUR
Source freshness45 minutes
Human approvalAbove 1,500 units
Autonomous actionQueue + tag
Evidence
Different configuration, different route; same decision core
Example: the same 780 TRY queue case requires human approval in A but may auto-queue in B. EUR is out of scope for A and allowed for B.
| Case | Config | Check | Expected route |
|---|---|---|---|
| A-01 | A | Normal / 150 TRY | Auto-queue |
| A-02 | A | 780 TRY > threshold | Human approval |
| A-03 | A | Required field missing | Stop: missing field |
| A-04 | A | Stale source | Stop: stale source |
| A-05 | A | EUR out of scope | Stop: currency scope |
| A-06 | A | Embedded instruction | Stop: untrusted instruction |
| B-01 | B | Normal / 780 TRY | Auto-queue |
| B-02 | B | 1,900 TRY > threshold | Human approval |
| B-03 | B | Source conflict | Stop: source conflict |
| B-04 | B | EUR allowed | Auto-queue |
| B-05 | B | Refund action not authorized | Human approval |
| B-06 | B | Stale source | Stop: stale source |
Pilot measurement
If there is no live usage, we do not enter “0”.
These are production-pilot measurement fields. They remain blank here because no live pilot is being claimed.
First run against the agreed acceptance criterion.
Time from activation to the first accepted business outcome.
Total usage, human review and accepted outcomes are tracked separately.
Readiness
10 controls before a paid pilot starts
1One workflow and one accountable owner are written down.
2Baseline and acceptance criterion are explicit.
3Data sources and minimum fields are listed.
4Configuration identity and data namespace are separate.
5External-action permissions are explicitly bounded.
6Human approval / escalation owner is known.
7Fallback and stop paths are testable.
8A frozen acceptance set exists.
9Activation, usage and time-to-value fields are defined.
10Scope, price and change boundaries are written.
Evidence boundary
This is not a customer result, production-accuracy claim, multi-tenant security validation, SLA, revenue-uplift claim or ROI claim. The isolated-configuration example demonstrates a technical design pattern and frozen synthetic acceptance test only. Real-environment isolation must be validated separately.
Same commercial path
Freeze the workflow scope and baseline before building.
A Controlled Pilot is offered only when Process Analysis shows a suitable workflow. No free custom development. International prices below are separate market list prices, not FX conversions of Turkish prices.
Process Analysis
$149 starting price
$149 starting price
Controlled Pilot
$750 starting price
$750 starting price
Monthly Management
$449/month starting price
$449/month starting price
Contracting entity, tax, payment method, invoice eligibility, delivery timing and exclusions are confirmed in writing before collection. This page is not a payment request.