PRODUCTS & SYSTEMS · 2026 · INTERNAL OPERATIONS TOOL · CURRENT OPERATION UNVERIFIED
Reading a status label was easier than deciding what it meant when the record vanished from the page. I built a personal monitor that revisited several submission portals and sent a short alert only when its stored state changed.
The code, transition rules, retry logic, ledger and backups survive. I have not verified that the system is still running, that its methods comply with every portal’s current terms, or that anyone else could use it. It also says nothing about the quality or outcome of the manuscripts.
A common table shape was a bad assumption
Each portal landed on a different page after login and used its own status language. An expired session could return a plausible page rather than an explicit error. In another case, the same state appeared twice and produced duplicate alerts. The monitor had to verify that it was reading the intended account view before trusting a matched phrase.
A terminal event could remove the record
The largest blind spot occurred when an item did not change to a new visible label but disappeared from the previous list. I added disappearance itself as an event, followed by a retry and a separate state for manual confirmation.
A file lock prevented two checks from issuing the same alert, while status storage was kept separate from capture and session renewal. These controls reduced omissions in my own operations. They did not validate an editorial decision or improve the underlying research.
A security audit comes before any public package
Manuscript titles, journal names, identifiers, accounts, cookies, sessions and alert tokens remain private. Any of them may also be present in logs and backups, so the surviving package is not publishable. Current automation permissions would need a separate portal-by-portal review.
Project record
Period: 2026
Role: status transitions, alert conditions, retries, backups and disappearance detection
Internal evidence: monitor code, state ledger, logs and backups
External validation: none
Final outcome: a personal internal tool was implemented; current operation, terms compliance and external use remain unverified