Independent IrregularNet realm planning worksheet Version: 1 (2026-11-03) Status: planning only. The deployed service is the Muse pilot; a supported independent-realm installer is not available. This file is not configuration. Downloading or completing it submits nothing and creates no access or trust. Keep your completed copy private. Include no passwords, RADIUS secrets, private keys, downloaded profiles, member records or raw incident logs. Independent realms do not automatically trust or roam with IrregularNet. For a shared community location, use the separate host-plan.txt worksheet. 1. Choose ownership and operating model Organization and proposed realm display name: [ ] Existing managed fleet / organizational PKI and device management [ ] Self-hosted issuer, enrollment and RADIUS service [ ] Managed certificate / authentication service Components operated locally versus by a provider: Primary and backup identity / membership owners: Primary and backup issuer / offline key custodians: Primary and backup RADIUS / network operators: Update, incident and off-host recovery owners: Private support contact and provider exit plan: 2. Define the realm contract (proposals, not deployable settings) Stable realm identifier: Your own HTTPS enrollment hostname: Exact authentication-server name(s) clients must verify: Separate pilot SSID: Identity provider and stable account identifier: Eligibility source, freshness and offboarding policy: Human / service-account eligibility rules: Administrator roles and approval process: Any location delegation, scope and required comments: Audit retention and access policy: 3. Define trust and credential lifecycle Client versus server trust boundaries: Protected online issuer and offline root custody: Approved private credential-delivery process: Per-device enrollment and device ownership policy: Certificate lifetime, renewal lead time and user support: Lost-device / account offboarding procedure: Target maximum access window after revocation: Policy for existing sessions, resumption and roaming: Backup retention and off-host restore owner: How restore preserves revocations made after a backup: 4. Plan one isolated deployment Access point / controller / router models and firmware: Actual NAS source and private authentication transport to verify: Member IPv4 / IPv6 segment and explicit allowed destinations: Staff, guest, private and management networks to protect: DHCP / DNS responsibility and time synchronization: Alternate management access and rollback owner: Exact source / image versions to qualify: Onsite tester, client OS versions and test window: 5. Record acceptance (leave blank until a reviewed test) [ ] Eligible enrollment and renewal work through the real identity provider [ ] Ineligible accounts fail under the chosen eligibility policy [ ] Each test device has a distinct credential and correct ownership [ ] A real client verifies the intended server and reaches allowed services [ ] An untrusted server, wrong-realm and revoked credentials are rejected [ ] IPv4 and IPv6 isolation protect private and management networks [ ] Staff and guest services remain usable [ ] Existing-session, sleep/wake and roaming access-loss window measured [ ] Enrollment / RADIUS outages and alternate management tested [ ] Off-host restore preserves newer revocations and rejects revoked access Actual source / image, hardware / firmware and client OS: Expected versus observed results and evidence reference: Measured maximum access window: Unresolved limitations and responsible owner: Realm owner / reviewer and activation decision: 6. Agree the next implementation milestone [ ] Complete policy-consumer inventory and versioned realm contract [ ] Nonsecret validation and configuration preview [ ] Isolated bootstrap and protected state / secret delivery [ ] Lifecycle, upgrade, monitoring and recovery qualification [ ] Physical pilot acceptance and operator handoff Named maintainer, next deliverable and acceptance evidence: Guides: https://wifi.irregulars.io/setup/hosting/#realm-plan https://irregularpedia.org/server-guides/irregularnet-realm/ https://irregularpedia.org/server-guides/certificate-wifi-organization/ Roadmap (repository sign-in may be required): https://git.juntogroups.org/irregulars/irregularchat-monorepo/-/blob/main/selfhost/irregularnet/ROADMAP.md