IrregularNet host planning worksheet Version: 1 (2026-11-03) Current availability: limited Muse pilot. Additional-location provisioning, location operator controls and community-wide admission are not yet live. This is a planning document, not a supported installer. Purpose: prepare a discussion with the community infrastructure operator. Completing this worksheet does not apply for, approve or activate a location. Keep your completed copy private; agree separately what may be published. Never include passwords, RADIUS secrets, private keys, downloaded profiles, member lists, incident reports or raw network logs. 1. Choose your operating model [ ] Approved location in the shared IrregularNet realm Intended experience: members use a separate certificate for each device across approved locations. Community infrastructure manages identity, issuance and global revocation; the host manages local connectivity. [ ] Independent realm with your own identity, trust and access policy Requires your own issuer, enrollment, RADIUS, renewal, offboarding, monitoring and recovery. No automatic trust with IrregularNet. Chosen model: Proposed location or organization name: Primary operator and private contact: Backup operator and private contact: What location/contact details may be published, if any: 2. Inventory existing equipment Router model and firmware: Access point model(s) and firmware: Controller and version, if used: Confirmed external RADIUS / Enterprise Wi-Fi support: Member VLAN or equivalent isolation support: Switch / uplink requirements: Alternate management access if authentication fails: 3. Plan connectivity and service Permission to share the internet connection: Expected concurrent devices, coverage and available capacity: Proposed opening hours / availability: Private authentication transport to discuss with the platform operator: Actual RADIUS source identity to verify with that operator: Member IPv4 and IPv6 isolation plan: Staff, guest, private and management networks to preserve: DHCP / DNS responsibility: Local support and outage owner: 4. Agree approval, testing and recovery Who approves the location and activation: Onsite tester and test device operating systems: Proposed maintenance window: Configuration backup and alternate recovery path: Who can carry out rollback: Acceptance results (leave blank until an approved test): [ ] Eligible device connects and reaches intended services [ ] Revoked / ineligible credential fails fresh authentication [ ] Expected authentication server identity is validated [ ] Member devices cannot reach protected networks over IPv4 or IPv6 [ ] Existing staff / guest services still work [ ] Outage and recovery behavior checked [ ] Reauthentication, sleep / wake and access-loss deadline measured [ ] Shared-realm location restrictions tested across devices and locations (only once that capability is released) Evidence reference, unresolved issues and reviewer: 5. Handoff Discuss this plan privately with the Muse operator or your IrregularNet infrastructure contact. In the planned onboarding process, the platform operator would select and approve permanent site bindings and deliver credentials through a separate private process, after the provisioning release is qualified. Do not configure against Muse's service or reuse another site's credentials. Current pilot status and guide: https://wifi.irregulars.io/setup/hosting/ https://irregularpedia.org/community/irregularnet-hosting/ Implementation roadmap (repository sign-in may be required): https://git.juntogroups.org/irregulars/irregularchat-monorepo/-/blob/main/selfhost/irregularnet/ROADMAP.md