FIXED-SCOPE ZINVYL SERVICE

Single Automation Blueprint

Design one bounded automation connecting no more than three approved systems from one documented trigger to one measurable outcome.

$79fixed published price
3 daysafter complete accepted inputs
1included revision

What you receive.

The published contract below controls this service. Customer-specific work begins only after signed funding verification and complete, accepted inputs.

INCLUDED SCOPE

DELIVERABLES

  • Design one bounded automation connecting no more than three approved systems from one documented trigger to one measurable outcome.
  • Define explicit input and output schemas, duplicate handling, retry limits, human-approval boundaries, failure paths, and safe-stop behavior.
  • Deliver a machine-readable workflow blueprint, failure-path register, and acceptance-test contract; production implementation and deployment are not included.

SAFE INPUTS REQUIRED

  • One sanitized JSON work package naming the trigger, one to three approved systems, expected outcome, input schema, output schema, duplicate key, and owner-gated actions.
  • The buyer's acceptance criteria and maximum retry count from zero through five.

ACCEPTANCE EVIDENCE

  • The design covers exactly one bounded workflow and no more than three approved systems.
  • Inputs and outputs use explicit schemas.
  • Duplicate and retry behavior is deterministic and bounded.
  • Success and failure cases preserve owner authority and prevent duplicate writes.
  • The completed package receives accountable review before delivery.
BOUNDARIES

NOT INCLUDED

  • Production connection, account creation, credential custody, code deployment, external writes, live monitoring, ongoing maintenance, autonomous customer communication, or guaranteed business results.
  • More than one workflow, more than three systems, more than twenty-five input or output fields, regulated or sensitive data, or any request to bypass authentication, authorization, review, or platform controls.

EVIDENCE LIMITS

  • The deliverable is a design and acceptance contract, not a deployed automation or proof that third-party APIs will behave as modeled.
  • Acceptance tests are specified for later execution and are not represented as run against production systems.
  • The public proof is synthetic and is not a customer result, sale, or demand claim.

Canonical capabilityzinvyl.factory.workflow-single-automation-blueprint.v1