CS-FIL-005 · FIL Files, scheduled batches and bulk transfers · 63 of 192
Resubmit a corrected or repeated file
Data Steward · Trigger: A producer re-uploads a file or issues a revision.
Simulated fixture data. Every record, receipt and timeline entry on this screen is demonstration material. It is never production evidence.
Acceptance
2 of 3 steps satisfiedRepeated and revised test files will receive distinct, traceable dispositions without silent overwrite.
Run the remaining steps below. The result is read back from record state — nothing here is a toast.
Normal path
A file batch is parsed, reconciled against its declared totals and confirmed as permitted to use.
Step 1. Parse the artifact with its declared schema.
satisfiedparsecompletereconciliationverifiedpermissiongranted
Moves the record and writes evidence. Permission: test.
Acceptance for this step: parse = complete
Step 2. Reconcile declared against parsed counts with evidence.
satisfiedOperates onINTA-028Supplier certificate 2026-09-28Intake batch· NORTHBRIDGE-ALLOY / Sheffield Bar Mill
parsecompletereconciliationverifiedpermissionunauthorised
Moves the record and writes evidence. Permission: remediate.
Acceptance for this step: reconciliation = verified
Step 3. Confirm permission to use the content.
not yet satisfiedparsecompletereconciliationverifiedpermissionreview
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: permission = granted
Exception path
A reused filename will not by itself establish sameness or authorize replacement.
Alternate path. Totals do not reconcile: hold the batch and propose a correction rather than admitting it.
not yet satisfiedholdingreleasedcorrectionpendingreleaseAuthoritypending
Moves the record and writes evidence. Permission: remediate.
Acceptance for this step: correction = proposed
Workflow as specified
CoreSync will distinguish identical content, a new version and an approved correction, preserving original intake outcomes and linking changed records to their predecessors.
Evidence written in this session
Nothing run yet in this session. Record state shown above may already satisfy steps from the seeded fixture history.