Administration | Masonic Ritual

Pack Builder

Turn an existing ritual source into a secure Nexus expansion pack without editing JSON by hand.

Private by design: the source ritual and degree access words are processed locally in this browser. The raw ritual text and access words are never sent to Supabase. Only the encrypted pack is sent to the Nexus signing function.

Add or update a ritual pack

Choose the signed .nxpack file. Nexus reads and validates the pack code, title and version automatically.

One-step upload: choose the signed .nxpack. Nexus uses the pack’s permanent identity to decide automatically whether this is a new product or a newer release. Existing customer ownership, price and publishing status are preserved automatically.

Manage ritual packs

Current pack releases are shown by default. Older and archived entries stay out of the way unless you choose to show them.

Publishing: choose Published / live to make a pack available for Buy / Open. Archive hides it from customers while preserving ownership. An archived pack with no customer ownership history can then be deleted permanently from the pack database.

Loading uploaded packs…

Customers & pack access

Grant complimentary or tester access to a ritual pack, restore revoked access, or revoke an existing entitlement.

Loading customers and pack access…

Authorised testers

Tester status gives free access to eligible packs in the catalogue. Packs are only added when the tester chooses them, and any claimed pack remains theirs permanently.

Customer	Ritual pack	Source	Status	Devices	Granted	Action

What happens when you upload

Your administrator account is checked.
The pack structure and Nexus digital signature are validated.
The version is checked against the current catalogue version.
The release is stored privately at its own versioned path.
The catalogue record is updated so authorised Readers can see the newer version.