Data to a Verified Action

Follow a synthetic record from a supported source through queryable data and agent access to an independently verified external integration outcome.

Use a synthetic record and an approved test destination to verify the whole data path. Obtain a configured source, supported mapping, permitted read access, and an integration whose test behavior and mutation permissions are understood. If any prerequisite is missing, complete provisioning before running the corresponding step.

For a hospital integration, first agree on the exchange pattern and interface scope. Inbound patient or scheduling notifications and outbound changes need separate access, tests, and confirmation. The steps below assume a supported, provisioned source and target.

Each arrow requires new evidence. Acceptance does not establish queryability, retrieval, or external completion.

Connect the Source

Configure a supported intake source or submit records through FHIR import. Connector syncs were retired with the connector runner on October 10, 2026. Record the source identifier and the submitted record's external identifier so that you can locate the same record later.

Authenticated dataset intake and browser Surfaces have different contracts. A Surface submission does not automatically create a dataset file. Source support and parsing must be confirmed for the chosen format.

Verify Queryable Data

Use Data → Records and the supported workspace data query path to locate the intended entity and inspect source attribution. Verify its identity and the fields needed by the workflow. World-model read views update asynchronously; acceptance of an input is not evidence that the corresponding projection is already queryable.

If the record is missing or stale, inspect source status, mapping, identity resolution, and freshness before resubmitting. Preserve the original identifiers. Caller recognition may require a separate external identity binding; a queryable record alone does not prove recognition is ready.

Verify Agent Access

Configure the test service with the intended graph, query/tool access, and subject context. Run the bounded interaction from First Verified Conversation against that configured test service. Check the retained answer and available tool evidence against the synthetic source record. A plausible answer does not establish that the agent retrieved the intended source.

Verify the External Outcome

Follow Verify an Integration Action for the authorized test mutation, expected failure, target acknowledgement or read-back, and reconciliation. Apply approval requirements only to the integration path that implements them. The connector write-back review workflow no longer stages or delivers proposals.

Milestone	Evidence to keep
Submitted	Source and request identifiers; input acceptance or rejection
Queryable	Intended entity, source attribution, required fields, and observed freshness
Used by the workflow	Service/version, conversation/run, and available retrieval or tool evidence
Authorized	Required permission and approval decision for the specific action
Completed externally	Target acknowledgement or independent read-back
Reconciled and cleaned up	Resolution of ambiguous attempts and cleanup of the permitted test resources

Stop at the last verified milestone when later evidence is missing. Use Troubleshooting for the next diagnostic rather than repeating an uncertain mutation.