digital-twin-sync-workflowlisted

## Intent Synchronize a **digital twin** with real-time signals and keep it **grounded, safe, and auditable**. This workflow maintains alignment between the real world and its digital representation. This workflow is designed to **model both real and digital systems** using the canonical world-state schema: - `reference/world_state_schema.yaml` **Success criteria:** - Twin snapshot updated with latest signals - All drift and anomalies detected and documented - Risk assessed and forecasted with evidence - Actions executed only after checkpoint and approval - Complete audit trail with provenance - Rollback available if verification fails **Compatible schemas:** - `reference/world_state_schema.yaml` - `reference/event_schema.yaml` - `reference/workflow_catalog.yaml` ## Inputs | Parameter | Required | Type | Description | |-----------|----------|------|-------------| | `sources` | Yes | array | Data sources to ingest (APIs, files, streams, sensors) | | `world_id` | Yes | string | Identifier for the digital twin being synchronized | | `constraints` | No | object | Policy limits, thresholds, timing constraints | | `prior_snapshot` | No | object | Previous twin state for delta computation | | `sync_mode` | No | enum | full \| incremental \| delta_only (default: incremental) | ## Preconditions (hard gates) 1. **Policy constraints must exist** (`/constrain`) 2. **Checkpoint before mutation** (`/checkpoint`) 3. Any external side effects require explicit approval (do not `send`