Compare the new supplier file with ours. Apply safe price and product updates, never delete a missing product automatically, and show unusual differences separately.
COMMAND
Project objective2%
MISSION NX-2403 · DATA + PURCHASING
Supplier Catalogue Reconciliation
Compare the new supplier catalogue with the current catalogue, apply safe changes and protect removals and anomalies.
OPERATIONAL LOGICWhat Nexus is actually doing behind the mission.
01Interpret & authoriseDefine which records may be read, changed, merged or held for human review.
02Connect & profileOpen the authorised source file and database workspace; inspect schema, record counts, identifiers and data quality.
03Match & classifyCompare records, separate safe corrections from ambiguous cases and calculate the impact before writing.
04Back up & applyCreate a recoverable checkpoint, then write only high-confidence changes inside the approved scope.
05Re-query & verifyRead changed records back from the database, reconcile totals and test that no new contradictions were introduced.
06Record the rulesRetain matching logic, exceptions, evidence and accepted decisions for the next import.
MISSION ACTIVITYConnections, inspection, actions and proof in one operational record.
15 / 15 eventsI understand the requested outcome. I am fixing the scope, constraints, authority and evidence required before work begins.
INTERPRET
Scope · constraints · authority · success test7%
Verified permission to update prices and prepare clear new products. Product deletion, identity merging and large price exceptions remain outside automatic authority.
AUTHORISE
Project permissions · capability scope · blocked actions12%
Opened the supplier file from the approved intake location and connected to the internal catalogue database. The source file hash and database identity were recorded.
CONNECT
Supplier source + Catalogue database + Matching index18%
Created a catalogue checkpoint and preserved the untouched supplier source so every proposed change can be traced back to its original row and value.
CHECKPOINT
Supplier source + Audit package24%
The new supplier catalogue and the current internal catalogue were normalised without altering the source files.
LOAD CONTEXT
Project rules · history · accepted decisions30%
The data worker is profiling columns, normalising codes and units, and matching supplier rows to internal products using identity, history and business rules rather than one field alone.
INDEX
Files · pages · records · linked business data37%
8,000 supplier rows were matched against product identities, codes, descriptions, prices and historical mappings.
DISCOVER
Authorised working environment45%
Nexus separated 731 routine price changes, 86 clear new products, 41 possible discontinued products and 17 conflicting records.
PLAN
Work graph · normal cases · exceptions55%
Approved price changes were applied, new products were prepared, and protected categories remained outside the write set.
EXECUTE
Authorised change set70%
The Reviewer checked duplicate identities, implausible price movement, missing required fields and contradictions introduced by the update.
VERIFY
Result against objective and project rules84%
The mission remains inside the approved scope and authority. Sensitive actions outside that boundary remain locked.
CONTROL
Permission and scope boundary91%
Fifty-eight items are ready in one purchasing review queue with the old value, proposed value, evidence and consequence of each choice.
DECIDE
Human attention queue97%
The catalogue is reconciled. Routine work is complete; possible removals and conflicts remain protected for purchasing judgement.
RESULT
Verified mission stateMission scope, evidence, decisions, changes and verification have been attached to the project for the next command.
STORE
Project history · evidence · decisionsATTENTION QUEUEReview protected catalogue exceptions
VERIFICATION
- Supplier source and internal catalogue remain traceable.
- No product is removed because it disappeared from one file.
- Routine price updates passed margin and identity checks.
- Every protected exception includes supporting evidence.
MISSION WORK
What Nexus coordinated.
- Compare the new supplier file with ours. Apply safe price and product updates, never delete a missing product automatically, and show unusual differences separately.
- I understand the requested outcome. I am fixing the scope, constraints, authority and evidence required before work begins.
- Verified permission to update prices and prepare clear new products. Product deletion, identity merging and large price exceptions remain outside automatic authority.
- Opened the supplier file from the approved intake location and connected to the internal catalogue database. The source file hash and database identity were recorded.
- Created a catalogue checkpoint and preserved the untouched supplier source so every proposed change can be traced back to its original row and value.
- The new supplier catalogue and the current internal catalogue were normalised without altering the source files.
- The data worker is profiling columns, normalising codes and units, and matching supplier rows to internal products using identity, history and business rules rather than one field alone.
- 8,000 supplier rows were matched against product identities, codes, descriptions, prices and historical mappings.
- Nexus separated 731 routine price changes, 86 clear new products, 41 possible discontinued products and 17 conflicting records.
- Approved price changes were applied, new products were prepared, and protected categories remained outside the write set.
- The Reviewer checked duplicate identities, implausible price movement, missing required fields and contradictions introduced by the update.
- The mission remains inside the approved scope and authority. Sensitive actions outside that boundary remain locked.
- Fifty-eight items are ready in one purchasing review queue with the old value, proposed value, evidence and consequence of each choice.
- The catalogue is reconciled. Routine work is complete; possible removals and conflicts remain protected for purchasing judgement.
- Mission scope, evidence, decisions, changes and verification have been attached to the project for the next command.
VERIFICATION
How the result was checked.
Supplier source and internal catalogue remain traceable.
Recorded with the mission evidence and compared with the original objective.
No product is removed because it disappeared from one file.
Recorded with the mission evidence and compared with the original objective.
Routine price updates passed margin and identity checks.
Recorded with the mission evidence and compared with the original objective.
Every protected exception includes supporting evidence.
Recorded with the mission evidence and compared with the original objective.
8,000Products compared
731Routine price changes
86New products prepared
58Review items
Review queue ready
The catalogue is reconciled. Routine work is complete; possible removals and conflicts remain protected for purchasing judgement.
What became true?
Compare the new supplier catalogue with the current catalogue, apply safe changes and protect removals and anomalies.
How control remained visible.
Apply approved routine updates · protect removals and anomalies
What the project remembers.
The accepted rules, decisions, outputs, exceptions and checks now inform every later mission in this project.
Continue from the result, not from an empty prompt.
The completed mission updates project history so the next order can build on what is already known.