Jul.3, 2026
Internal_OpID
memory bloc 1783073820:System: CORE
Module: Calculator
Values: Operator’s Origin
Operations: x+Action required: Perform Basic Maths
Entry logged by:
System
Help us @YourBasicMaths , you’re our only hope 
Edit:
Adding Yesterdays post about Prime Numbers in case some folk missed it
memory bloc 1728694800: PRIME
Value: 2136,279,841 – 1
Book 7. A prime number is one (which is) measured by a unit alone.
Memory compliance: 100%
Entry logged by:
System
Seems to return the closest prime number to whatever you calculate.
What’s basic maths birth year. The. Express it as its prime build up
Or the year he joined
every integer greater than 1 can be uniquely broken down or built up as a product of prime numbers (e.g., (12 = 2 x2 x 3)
Woah, crazy. 2+2=4 causes it to fluctuate between prime number 3 and 5.
Messing about with nonsense sums…
My birth year plus current year IS a prime number. That was a happy coincidence.
My guess is it’s an error/hint. 3 and 5 must be the prime make up of the numbers we are supposed to use
This is a puzzle for @YourBasicMaths but it is 4.30 am here…
Seeing it alternate between 3 and 5 had me thinking of 353 guilty spark, thought it was gonna call me Reclaimer for a minute.
Yup, his operator origin. Prob not much we can do right now unless someone knows their personal info 
They were a waking titan participant, but they could not find their username or login from then, it seems they may have chose to have their info purged during the changeover but not 100%
Their new join date to etarc for PSS is May 20th 2026.
Didnt they have a birthday recently? There was so many in the last week I forget who had one 
They have our email addresses. Our IPs now. And they’re looking for someones birth date? Maybe PSS is actually just a scam Phishing event 
The forum only asks for day and month, not year for birthday. Our joined date has the year. June and July are when most people joined for WT. Maybe their user name from WT had a number with it. That can make it hard to find if you don’t remember that number.
If you multiply 3 and 5 it then jumps between 13 and 17
The result is equal distance between both prime numbers 
The flashing between two numbers behaviour changes if you enter 13 x 17, it shows 221 briefly then changes to 223 .. and settles at 223, no jumping back and forth as it did with 3 and 5. Nothing clever, but it is a behaviour change, maybe significant or not .. I am but a worm :).
The calculator works in two phases every time you press =:
Phase 1, local eval: The expression is evaluated in your browser using JavaScript’s eval(). This result appears instantly in the display.
Phase 2, server fetch: The calculator POSTs that value to admin-ajax.php?action=proc_z7k9. The server finds the nearest prime(s) to your result and returns them as JSON.
The display then updates based on the server response:
Single prime returned: If only one nearest prime exists (e.g., eval = 2073 → nearest prime = 2069), the display switches to that prime with a brief 0.6s RGB text-shadow animation. The number stays stable after that.
Two primes returned (tied distance): If the eval is exactly midway between two primes (e.g., eval = 133590, equidistant from 133583 and 133597), the response contains “or”. The display then alternates between both primes every second indefinitely, with a 0.4s glitch animation on each swap. This is the “bouncing” behavior.
Eval is already prime: The server returns the same number. The display shows it with the 0.6s animation but the number never changes - it’s a stable result from the start.
The glitch animation (rgbGlitch) always plays, creating the red/cyan text-shadows. The key difference is whether the display settles on one number (single prime) or keeps alternating forever (tied primes).
The server action proc_z7k9 simply returns the nearest prime(s), it doesn’t do anything else (on our receiving end). What’s happening server side to return it is a black box, and may be time gated (or gated by other things). The calculator seems to be purely about transforming values into their nearest prime via a remote lookup.
The numbers required to get there are going to be specific to @YourBasicMaths and we should allow them to solve it.
I have my suspicions on the solve and working (if it isn’t a private date), and offer them only if they get stuck.
It would be nice for Operators to respect that this is almost certainly for YourBasicMaths.
Maybe if I cook some bacon and blow the aroma their direction? …
Every data breach procedural 
It smells like breakf—I mean SCIENCE, in here!
Am I too late for YourBreakfastMaths?
One plate of scrambled eggs +
Three strips of bacon +
Orange juice and coffee ÷
Time to drive to Diner =
Delicious!
So is this going to be one of those ‘birthday’ math tricks?
Now what would be the possible range of outcome if one would kind of take this literally. Assuming dd/mm/yyyy → dd x mm + yyyy = ?