====== Technical overview ======

PoolRotater uses a shared multiroom supervisor and account-level integrations to manage its lobbies. Persistent state supports feedback, player statistics, unavailable-map quarantine, and cached calculations. A separate research pipeline supplies Mania evidence used to validate selection models; the larger research database is not the sealed native catalog used by a room worker.

The wiki is an independent DokuWiki application with file-based articles, revision history, and access controls. Reading or editing an article does not call the osu! API or change a live room. It shares the VPS web server but has a separate PHP worker service and operating-system account.

===== Current v7 owner pilot =====
As verified October 14, 2026, the owner controller runs **v7.0.1 dev10** and its qualified **v7.0.2** replacement is queued for the all-four-empty window. The latest published private operator kit is **dev12**. The owner hub and catalog origin are separate services from local hosting. Operators keep their own osu! credentials and use complete prepared signed catalogs rather than running the research pipeline. Directory listing and feedback sharing need separate consent; uploaded votes are not automatically active shared weighting. Last verified local catalogs/snapshots support continued operation during hub outages.

The owner migration preserved compatible configurations, catalogs and historical ratings. Installed qualification and actual owner Standard/4K completed matches are documented; the two earlier independent-host votes were centrally accepted. Active shared-weighting gameplay and all-mode acceptance remain separate observations. See [[updates:v7_0_1|current release]], [[wiki:distributed_hosting|hosting and sharing]] and [[wiki:room_updates|update boundaries]].

===== Historical independent room workers in v6.7 =====
[[updates:v6_7_0|v6.7.0]] deployed on October 1, 2026. It introduces separate room-worker processes with pinned releases, coordinated by the shared account supervisor. Compatible room updates can roll through empty lobbies independently after initial adoption; shared connections, dependencies and persistent database changes still require a coordinated upgrade. Read [[wiki:room_updates|How room updates work]] for the sequence, player-visible effects and compatibility limits.

Website and monitoring SQLite reads now use the database owner’s identity to prevent a root-reader support-file permission race. The deployed bot release also contains connection-setup retries and an optional download-cache fallback.

Release notes describe historical implementation changes. Public articles omit deployment secrets and private operational reports. See [[updates:start|release history]] and [[wiki:map_selection|map selection]].

===== Standard map research =====
The osu!standard finder has a separate research pipeline for PP-efficient Farm maps and structural Stream detection. The source bundle reviewed for this wiki is staged; the live bot consumes an existing catalog rather than running a model fit for each pick. Read [[technical:standard_map_finder|Inside the Standard Farm & Stream finder]] for the code, model limits, and which filters the live integration actually applies.

===== Newer selection and guidance =====
Standard spatial Jump evidence is independent of Farm score. Sparse pass-count tiers retain star/age/hard-length bounds; mixed NoMod/DT builds them independently. The pinned DT catalog uses local official-ruleset calculations, cached chart-revision checks and actual played duration, with per-item mod restoration before start. A Standard catalog refresh needs coordinated verified DT rebuilding; an article edit does not start either job. See [[wiki:mixed_dt|mixed DT]] and [[technical:standard_map_finder|Standard research]].

Native Mania separates structural patterns from Rice/Noodle composition. Noodle has a native LN exhaustion tier; LN/Noodle weighting reduction applies only to ordinary Variety. Personal ''.lang'' appends prepared guidance after English, not machine translation of players' chat; it is independent of website language choice. See [[wiki:mania_styles|Mania behavior]] and [[wiki:player_languages|languages]].

===== Readiness in multiplayer rooms =====
From **v6.7.18**, rooms with at least **two gameplay players** can start with **one ready player**. Automatic starts and [[commands:start_match|.start]] leave unready/AFK players out; if nobody is ready, the room waits. Spectators and referees do not count toward this two-player rule.

Countdown grace is tracked per player during their room stay and coalesces to five seconds for several newly unready players. Map checks and unknown-outcome recovery remain in place. See [[wiki:unready_start|readiness rules]] and [[updates:v6_7_18|validation and rollout]].

===== Protected v7 deployment and distribution =====
The controller retains shared account ownership and integrations. After v7.0.2 controller activation, independently approved compatible worker releases may roll through empty rooms without replacing the parent. Root approvals bind installation/generation and parent identity; shared/dependency/storage fingerprints cannot change through this path. Failed handoffs may safely roll back, while uncertain ownership remains held. Future shared controller updates need separate review, including any mixed approved worker versions. See [[wiki:room_updates|timing and safety]] and [[technical:operator_commands|operator commands]].

The [[wiki:selection_catalogs|prepared catalog]] is map-level selection output, not the full research workspace. The separate network agent handles directory/feedback work; rich remote progress/settings need the separately staged v2 hub activation. Publishing an operator kit, activating the owner controller and activating that hub are distinct operations.