---
name: data-sync-and-workflow-orchestration
description: Moves records between connected systems on a schedule or on demand, exactly once, with field mapping, conflict rules, and a reconciliation report every run. Use when the user asks to sync two systems, keep records aligned, run a scheduled data job, or reconcile mismatched data.
metadata:
  version: "1.1.1"
---

# data-sync-and-workflow-orchestration

> **Client-neutral reusable package.** No client names, tenant or workspace identifiers, account or
> resource IDs, customer records, credentials, or internal paths. All examples are synthetic.

| | |
|---|---|
| Live catalog name | Data Sync and Workflow Orchestration |
| Live category | Agency Operations |
| Catalog entry | 19 |
| Internal capability ID | `CAP-AO-02` |
| Provider | Multiple (provider-neutral) |
| Availability | Candidate; validate in the active Workspace |
| Deliverable type | `client_ready_guided_skill` |
| Validation status | Candidate; local package validation only |
| Version | 1.1.0 |


## OLLIE Runtime integration

Use this capability under the active OLLIE Operator. Read live Workspace Context and tenant
bindings for the required inputs below; this public package supplies no client facts or authority.
Consume `ask-ollie-authority-core` for authority, `outloop-access-fallback` for recovery and
resource verification, `email-lifecycle-core` for recipients, approvals and stored-copy delivery
verification, and the bootstrapper Runtime Contract for ownership, scheduling and completion.
These owners govern execution; this Skill does not implement a competing runtime.

Select the relevant expertise below for the requested outcome. Runtime governs combining Skills,
partial use and completing missing steps with other authorized capabilities. This Skill's domain
scope does not limit the Operator's wider authorized task. Preserve domain safety restrictions.
Verify findings against source evidence and read back any resulting artifact or authorized change.

## Business outcome

Two systems agree, and a run that is interrupted or repeated does not duplicate or corrupt anything.

## Operating modes

Read · Analyze · Write with approval

## Prerequisites — what must be true before this runs

- Workspace Context
- An approved grant for both source and destination
- A written field mapping, match key and conflict rule

## Required inputs

| Input | Source |
|---|---|
| Source and destination systems | Workspace configuration |
| Field mapping | Required — including type and format coercion |
| Match key | Required — how a record is recognised on both sides |
| Conflict rule | Required — which side wins, per field |
| Schedule and volume ceiling | Configuration |
| Named approver for the first run | Configuration |

## A volume anomaly is a stop, not a shrug

If a run wants to touch far more records than the historical norm, something upstream changed — a schema, a filter,
a deletion. Stop and ask. A sync that faithfully propagates an upstream accident is worse than one that failed.

## Never sync a credential

Field mappings carry business data. A field containing a token, key, password or authorization header is excluded
from any mapping — if one appears in the source schema, report it and stop rather than moving it.

## Action classification

| Action class | This workflow |
|---|---|
| Read | Source records, destination records, prior run state |
| Analyze | Diff computation, conflict detection, orphan and duplicate detection, volume-anomaly check |
| Draft | A dry-run diff — what would be created, updated, skipped and flagged |
| Write with approval | Applies the approved diff to the destination, then reads back |
| Destructive | Deletion is **off by default** and requires an explicit per-run gate |

## Approval and delivery

The Operator applies Authority Core and the active Workspace approval policy to any requested
mutation. Email Lifecycle owns recipient classification, sending and stored-copy verification.
The action table defines this capability's domain scope; it grants no permission by itself.

## Expected output

A dry-run diff before the first write, then a per-run reconciliation report: created, updated, skipped, conflicted and failed, with the read-back state of each write.

## Synthetic placeholders used in this package

These are illustrative only. Real values come from the client's own workspace configuration and are
never written back into this package.

| Placeholder | Meaning |
|---|---|
| `SOURCE_SYSTEM_PLACEHOLDER` | Source system |
| `DEST_SYSTEM_PLACEHOLDER` | Destination system |
| `MATCH_KEY_PLACEHOLDER` | Record match key |