Use this new pricing rule everywhere it belongs. Keep the current design, do not overwrite genuine exceptions, and ask me before anything is published.
COMMAND
Project objective2%
MISSION NX-2401 · WEBSITES + COMMERCE
Regional Pricing Update
Apply the accepted installation-price rule everywhere it belongs, preserve real exceptions and publish only after approval.
OPERATIONAL LOGICWhat Nexus is actually doing behind the mission.
01Interpret & authoriseLoad the project rules, confirm the requested outcome and fix the permitted website scope.
02Connect & discoverOpen the authorised HTTPS, SFTP and content connections; identify the active web root and map URLs to their sources.
03Read & compareWalk the relevant files, pages, forms and records; compare the current state with the accepted project rules.
04Protect & executeCreate a snapshot and change manifest, then perform only the changes that fall inside mission authority.
05Read back & verifyRe-read server sources and public URLs; test the affected paths and compare the result with the objective.
06Record & continueStore evidence, decisions, changed items and rollback references in the continuing project history.
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 read access to all pricing sources and write access only to the approved page and product fields. Public publishing remains locked behind the named approval.
AUTHORISE
Project permissions · capability scope · blocked actions11%
Opened the authorised HTTPS and SFTP connections to the production domain. The public site root, mapped project folder and server identity were confirmed before inspection.
CONNECT
Website endpoint + SFTP hosting + Product database17%
Captured a before-state package with file hashes, a product-data checkpoint and representative page renders so every later change can be compared or reversed.
CHECKPOINT
Before-state snapshot23%
Project memory loaded the accepted installation-price rule, protected regional exceptions and the current publication boundary.
LOAD CONTEXT
Project rules · history · accepted decisions28%
The crawler is traversing templates, generated pages, product records and sales documents. Inherited values, duplicates and regional overrides are being indexed separately.
INDEX
Files · pages · records · linked business data35%
The website and product sources are being scanned as one pricing surface. 2,143 authorised items are in scope.
DISCOVER
Authorised working environment42%
326 items contain the old rule. 321 match the normal pattern; five use conflicting legacy logic and have been isolated.
PLAN
Work graph · normal cases · exceptions52%
The Website Worker updated the routine page content while the Data Worker aligned the product records and generated a change manifest.
EXECUTE
Authorised change set66%
The Reviewer compared all 321 routine changes with the pricing rule, page structure and preserved content. No unrelated text changed.
VERIFY
Result against objective and project rules79%
The mission remains inside the approved scope and authority. Sensitive actions outside that boundary remain locked.
CONTROL
Permission and scope boundary86%
Five legacy cases need a business choice: keep the local exception, convert it to the new rule, or define a new regional rule.
DECIDE
Human attention queue91%
321 verified changes are ready. Five decisions remain. Publication is locked until approval.
RESULT
Verified mission state94%
Mission scope, evidence, decisions, changes and verification have been attached to the project for the next command.
STORE
Project history · evidence · decisions94%
DECISION REQUIREDResolve five legacy pricing conflicts
VERIFICATION
- Every changed item matches the accepted pricing rule.
- Page structure and unrelated content remain unchanged.
- Product records and public page values agree.
- Publication remains a separate authorised action.
MISSION WORK
What Nexus coordinated.
- Use this new pricing rule everywhere it belongs. Keep the current design, do not overwrite genuine exceptions, and ask me before anything is published.
- I understand the requested outcome. I am fixing the scope, constraints, authority and evidence required before work begins.
- Verified read access to all pricing sources and write access only to the approved page and product fields. Public publishing remains locked behind the named approval.
- Opened the authorised HTTPS and SFTP connections to the production domain. The public site root, mapped project folder and server identity were confirmed before inspection.
- Captured a before-state package with file hashes, a product-data checkpoint and representative page renders so every later change can be compared or reversed.
- Project memory loaded the accepted installation-price rule, protected regional exceptions and the current publication boundary.
- The crawler is traversing templates, generated pages, product records and sales documents. Inherited values, duplicates and regional overrides are being indexed separately.
- The website and product sources are being scanned as one pricing surface. 2,143 authorised items are in scope.
- 326 items contain the old rule. 321 match the normal pattern; five use conflicting legacy logic and have been isolated.
- The Website Worker updated the routine page content while the Data Worker aligned the product records and generated a change manifest.
- The Reviewer compared all 321 routine changes with the pricing rule, page structure and preserved content. No unrelated text changed.
- The mission remains inside the approved scope and authority. Sensitive actions outside that boundary remain locked.
- Five legacy cases need a business choice: keep the local exception, convert it to the new rule, or define a new regional rule.
- 321 verified changes are ready. Five decisions remain. Publication is locked until approval.
- Mission scope, evidence, decisions, changes and verification have been attached to the project for the next command.
VERIFICATION
How the result was checked.
Every changed item matches the accepted pricing rule.
Recorded with the mission evidence and compared with the original objective.
Page structure and unrelated content remain unchanged.
Recorded with the mission evidence and compared with the original objective.
Product records and public page values agree.
Recorded with the mission evidence and compared with the original objective.
Publication remains a separate authorised action.
Recorded with the mission evidence and compared with the original objective.
2,143Items inspected
326Changes prepared
321Verified routine changes
5Decisions required
Waiting for approval
321 verified changes are ready. Five decisions remain. Publication is locked until approval.
What became true?
Apply the accepted installation-price rule everywhere it belongs, preserve real exceptions and publish only after approval.
How control remained visible.
Inspect, prepare and verify · publication approval required
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.