Skip to main content

Module zone

Module zone 

Source
Expand description

The deployment-configured account zone (epic #1158, ticket #1162 / Phase A3).

The account zone is the DNS apex under which every host-form did:web this deployment mints lives — e.g. did:web:alice.acct.example.com. It is deployment-relative configuration: the operator picks it, in the metal repo, when deploying hyprstream. hyprstream never bakes a zone name in.

§No default — ever

A deployment that configures no account zone must degrade sanely: account minting is disabled with a clear error. It must not panic, and above all it must not synthesize a default zone name — a default would silently mint permanent DIDs under a domain the operator never chose (one-way door #1 in the epic). AccountZone therefore has no Default impl and no constructor that invents a name; the only way to obtain one is AccountZoneConfig::resolve_zone, which returns Err when the zone is unset.

§Label depth — the A2 seam (#1160)

A wildcard certificate matches exactly one DNS label: *.acct.example.com covers alice.acct.example.com and never a.b.acct.example.com. This module fixes the wildcard shape (one label below the apex). The grammar a single account label must satisfy (LDH, ≤63 chars, NFKC, no mixed-script, reserved list, never-reuse) is owned by A2 (#1160); B1 enforces it at mint time. A3 only guarantees the wildcard covers exactly one label, which AccountZone::wildcard_domain does structurally.

Structs§

AccountZone
A deployment-configured, validated account-zone apex.

Enums§

AccountZoneError
An error raised while resolving or parsing an account zone.