Purpose and scope This handbook draft describes normal import of inventory-demo.csv in the existing local Inventory Fixture Console, using PostgreSQL. It applies to new operations staff with Run operator permission. No code changes are involved. The purpose is to account for all 200 raw CSV rows without duplicates or overwrites. In the selected normal scenario, validation reports 200 valid rows. Successful execution requires: Commit status Completed. Unresolved count zero. Inserted, identical-existing, rejected, conflicting and unresolved counts summing to 200. An exported report for the current run ID. This draft documents the supplied workflow. It does not establish that the process has been implemented or tested. Prerequisites Required: Access to the local Inventory Fixture Console with Run operator permission. PostgreSQL available to the importer. inventory-demo.csv encoded as UTF-8, with columns record_id,label and 200 raw rows. Integer record_id values and nonempty labels. Supervisor availability for conflict acknowledgement or recovery approval. The approved local Reports folder as the export destination. Permission boundaries: Only the supervisor can approve replay. Operators cannot restore credentials. Conflicting labels must never be edited or overwritten. The single-run lock must not be bypassed. Open prerequisite: Access setup and system availability checks are not specified. Confirm readiness with the supervisor if access or availability is uncertain. Understandable step-by-step instructions Open the Inventory Fixture Console and select Fixtures. Expected result: Fixtures is selected. Choose inventory-demo.csv. Expected result: inventory-demo.csv is the selected input. Click Validate. Expected result: validation completes without writing to PostgreSQL. Open Validation report. Expected result: the normal scenario reports 200 valid rows. If conflicting rows are listed, stop for supervisor acknowledgement using Acknowledge conflicts, as described in section 5. Click Run once. Expected result: the import starts under the single-run lock. Identical-existing rows cause no writes, and conflicting labels are never overwritten. Open Run report. Expected result: the report shows the run ID, raw row count, inserted, identical-existing, rejected, conflicting, unresolved and commit status. Reconcile all raw rows by checking the report counts. Expected result: raw row count is 200; the five row categories sum to 200; unresolved is zero; commit status is Completed. Each raw CSV row belongs to exactly one category. If these checks fail, stop and follow section 5. Click Export report. Expected result: the console confirms Saved to approved local Reports folder. Use the console Open reports folder control and check the exported file for the current run ID. Expected result: the saved file identifies the same run ID as Run report. Workflow overview Open console > select Fixtures > choose inventory-demo.csv > Validate > open Validation report > supervisor acknowledges conflicting rows if present > Run once > open Run report > reconcile all 200 raw rows > Export report > open Reports folder and verify run ID. System boundaries and handovers: The local CSV supplies the input to the console. Validate checks the input without database writes. Run performs the import into PostgreSQL. Conflict acknowledgement and recovery approval belong to the supervisor. Export report saves the report to the approved local Reports folder. Error handling Invalid rows: Detection: Validation report shows 190 valid rows and 10 rejected rows with line numbers, with no conflicts. Reaction: preserve the 190 valid rows for import. Account for the 10 rejected rows in the final report. Do not discard valid rows because other rows were rejected. Check: the five final categories must still sum to 200. Conflicting labels: Detection: Validation report lists conflicting rows. Reaction: the supervisor uses Acknowledge conflicts on Validation report before the operator proceeds. Result: acknowledged rows remain in the conflicting category and are skipped without writing. No label edit or overwrite is permitted. Timeout or uncertain commit: Detection: Run report shows commit unknown. Reaction: stop. Commit unknown is not success. Do not replay automatically. Supervisor recovery: on Run report, the supervisor selects Reconcile run and checks stored IDs against the CSV. Reconciliation refreshes the same report, preserves raw-row identities and moves unresolved rows into the appropriate final categories. Approval: the supervisor checks the sum and commits before Approve replay becomes available, then may click Approve replay. Operator recovery: click Replay approved run only after approval is displayed. Result: replay processes only unresolved or not-yet-inserted rows. Already stored identical rows are classified once. The same report refreshes automatically. Recheck all success criteria. Authentication failure: Detection: HTTP 401 occurs before input fetch; the console shows Authentication failed and disables Run. No writes occur. Reaction: stop and notify the supervisor through Incident log. Never expose tokens. Recovery: the supervisor follows the approved local credential maintenance procedure outside this handbook and records Restored in the incident entry. The operator may start a new run only after Restored and approval are displayed. Operators cannot restore credentials. Blocked single-run lock: Detection: the lock blocks overlap or remains blocked. Reaction: stop and log an incident. Do not bypass the lock. Incident notification: Open the console Incident log page. Click Add incident. Enter the run ID, or the fetch attempt ID for a pre-fetch failure, the error code and a brief non-sensitive summary. Choose supervisor as recipient and click Save incident. Expected result: visible Saved confirms notification. Points to review: Recovery for unexplained count discrepancies or export failures is not supplied. Stop and refer these issues to the supervisor; do not claim success. Final check Verify: The report identifies the current run ID. Raw row count is 200. Inserted + identical-existing + rejected + conflicting + unresolved equals 200. Unresolved is zero. Commit status is Completed. Export confirms Saved to approved local Reports folder. The exported file contains the current run ID. The categories are mutually exclusive and exhaustive: each raw CSV row is counted once. Validation reporting 200 valid rows does not alone prove a successful commit. Documentation maintenance Owner: operations supervisor. Review this handbook monthly and after console changes. Update it when supplied controls, report categories, permission boundaries, recovery procedures or export behaviour change. Keep revisions aligned with the approved operating specification. Record unresolved operational details as review points until confirmed.