USR369 asked directly whether EXEC_OPEN needed updating given how much changed today. Read the live Master file in full to check -- found a real, serious problem: every one of the 11 systems' Series S EXEC_OPEN file has force=1 baked into the STARTUP sequence unconditionally (OPEN.php step 1, COMMS step 3), every single session, since 08/05/26. This directly contradicts the NO-SELF-FORCING rule (08/18/26) -- no override flag may be used without asking USR369 first -- which was never reconciled back against the still-live Series S file. This is the exact same class of instruction that made me stop and ask USR369 for permission at the very start of this conversation, except EXEC_OPEN itself has been telling every system to just do it, unconditionally, for over two weeks. Built Series T (per USR369's own direction -- new file, old S kept per standard practice, not overwritten) for all 11 systems: removed force=1 from both the OPEN.php call and the COMMS update_status call, added a changelog explaining why, and referenced today's new PEEK/JANUS commands (pointing to SOP-JANUS-PEEK.md) so a fresh session actually discovers they exist -- ORIENT-REG.md's WHERE DO I LOOK table didn't mention them at all until this same pass. System-specific content (e.g. Server[40]'s extra INDEX-FIRST section) was preserved exactly, not dropped, by doing surgical replacements on the shared template rather than wholesale regeneration. Also fixed ORIENT-REG.md directly: its own documented example for CLOSE showed `force=1` with no caution attached -- added a note pointing back to the no-self-forcing rule so that example isn't read as blanket permission. Added PEEK/JANUS as their own WHERE DO I LOOK row. Broadcast Series T Active -- Switch Now to all 11 systems, same pattern as every past series bump (L, M, etc).