14-day read-only facilitator pilot
Design and test the reliability, preflight, and signed-outcome layer around a bounded facilitator surface. No production mutation, automated payout, or wallet control.
Pilot boundary
The pilot determines whether MAKO evidence can improve route selection and post-payment accountability without entering the settlement path.
| Workstream | Included | Artifact |
|---|---|---|
| Surface map | Up to eight verify, settle, discovery, or demo routes in one facilitator environment; public or client-provided read-only documentation. | Versioned route and data-flow map. |
| Reliability feed | Field mapping for route status, observed price/network, latency, evidence timestamp, expiry, and confidence limits. | Feed contract and sample payloads. |
| Preflight comparison | Compare current route selection inputs with a MAKO evidence-enriched decision across agreed scenarios. | Decision matrix with before/after behavior. |
| Outcome receipt | Canonical fields, signing boundary, nonce/replay handling, response evidence, and reconciliation linkage. | Signed outcome-receipt design and verifier pseudocode. |
| Implementation findings | Integration cost, trust boundary, missing evidence, operational owner, and failure handling. | Go/no-go memo and prioritized backlog. |
| Recurring product | Recommended route ceiling, refresh cadence, alert conditions, evidence retention, and review rhythm. | Recurring-feed proposal; commercial terms not included. |
Fourteen-day schedule
Access stays read-only. Any request for production credentials, custody, or transaction execution is out of scope and stops the affected workstream.
60-minute technical kickoff. Confirm the eight-route ceiling, current decision inputs, evidence owners, and one integration hypothesis.
Document verify/settle/discovery paths, available response fields, signer boundaries, timestamps, and current observability gaps.
Draft reliability-feed fields and canonical outcome-receipt contract with expiry, replay, and verifier behavior.
60-minute working session to challenge the contract against real routes and revise the smallest viable integration.
Run agreed no-payment route/preflight scenarios and produce the before/after decision matrix. Paid paths remain excluded.
Finalize artifacts and deliver a 60-minute findings session with explicit continuation, redesign, or stop criteria.
Required access
The client names a technical owner and supplies the minimum material needed to map the facilitator boundary.
| Required | Route list, current public or redacted API schemas, existing selection logic, sample non-sensitive responses, signer/verifier documentation, and a technical owner. |
| Read-only | Public endpoints, documentation, exported logs with secrets removed, and a sandbox or fixture surface if available. MAKO does not write configuration or initiate settlement. |
| Never requested | Private keys, custody, payout authority, production write credentials, unrestricted customer payloads, or permission to deploy. |
| Technical sessions | Three sessions maximum: 60-minute kickoff, 60-minute contract review, and 60-minute final readout. |
Sample deliverable
The sample shows structure, not a claim that the same fields are live on every facilitator.
Outcome contract / draft
{
"route_id": "[redacted]",
"observed_at": "2026-07-22T00:00:00Z",
"payment": { "network": "eip155:8453", "amount_atomic": "[redacted]" },
"delivery": { "state": "delivered", "response_hash": "[redacted]" },
"nonce": "[redacted]",
"expires_at": "[redacted]",
"signer": "[redacted]"
}Verifier checks: canonical serialization, allowed signer, expiry, nonce uniqueness, payment reference, and delivery-state evidence.
Acceptance and stop rules
A continuation is justified only if the evidence layer changes a real decision at acceptable integration cost.
| Acceptance criteria | All eight or fewer routes are mapped; the feed and receipt contracts are internally consistent; agreed scenarios have recorded comparison results; open risks have owners; all three technical sessions and final artifacts are delivered. |
| Go | At least one agreed scenario produces a clearer allow/review/deny decision or a materially better outcome record; required data is obtainable read-only; verifier ownership and recurring refresh cost are acceptable. |
| No-go | The needed evidence cannot be obtained without custody or production writes; it duplicates current evidence without changing a decision; signer or replay boundaries cannot be owned; or maintenance cost exceeds the agreed value. |
| Recurring product | If go, the next proposal defines an exact route ceiling, refresh cadence, drift alerts, evidence retention, and monthly review. No recurring service is implied by this pilot. |
| Exclusions | Production implementation, SDK ownership, payout automation, custody, refunds, uptime promises, security certification, legal/compliance advice, and paid transaction execution. |