# Data files and exact field states These files contain only the supplied fictional Riverbend example. Actual app execution: **Not tested**. The fictional cutoff is November 2, 2026, 09:00 UTC. Read `export-scope.json` and `receiver-configuration.json` before interpreting counts or missing rows. The six original JSON files are exact copies of the source fixture. Three contain all six source records, nine received attempts and five destination records, including complete values, observation metadata, configuration references and stipulated receipts. No credentials or real provider data are included. Configuration and receipt facts are stipulated by the example, not an authentication implementation or production evidence. The three corresponding CSV files contain every field of every record, flattened using JSON Pointer column names. Nested objects use path columns such as `/payload/company`; arrays and empty containers remain JSON values. Five `@` columns repeat the fictional version, actual-app Not tested status, cutoff and scope-contract filename in every row; they are artifact context, not original record fields. Headers beginning `/` describe the complete original record. Every nonempty cell is a complete JSON value. Thus a JSON empty string is `""`, JSON null is `null`, and an empty CSV cell means that leaf path was absent in that record. These are not interchangeable. Quotation shown by a spreadsheet is part of this explicit typed encoding. Do not let an importer silently coerce types or fill empty cells. Use the original JSON when uncertain. `field-comparisons.json` and `.csv` are static derived comparisons: all six mapped fields for all six source records, thirty matches across five destinations and six unobserved destination fields for S05. They compare exact JSON values and property presence, without trimming, defaults, email deduplication or null coercion. They are not a general-purpose validator or an observation of your app. The complete baseline files are unchanged by the separate C11 and C14 counterexample explanations. C11's second raw claim also conflicts with the original accepted-attempt reference; it does not prove a second authorized write. A partial export can retain positive matches but cannot establish full counts, absence, surplus or uniqueness. No automatic merge, deletion, replay, upload or repair action is provided. There is no provider-specific payload promise, signature implementation, atomicity guarantee or integration success percentage. Keep real operational evidence in an authorized staff-only location.