Expand description
Accepted-current browser/WebTransport recipient provisioning.
The wire document in this module is public discovery material, not an
authority token. Production documents are projected by Discovery only from
its opaque checkpoint-bound ResolvedService. Browser consumers validate
the complete context and build per-resolution stores from the result; they
never install the material in a process-global trust store.
Structs§
- Browser
Provisioning - Opaque, fully validated provisioning snapshot used for dial/seal.
- Browser
Provisioning Document - JSON document returned by the production provisioning endpoint.
- Browser
Provisioning Material - Raw public values used by the trusted server-side projection.
- Browser
Provisioning Request - Exact context requested by a browser consumer.
- Browser
Request Binding - Accepted-state evidence copied into the signed and HyKEM-sealed request. Dispatch verifies it against the live checkpoint source before handler work.
- Browser
Request Transcript - Authenticated browser-only transcript metadata exposed to the generated service dispatcher. The generated dispatcher independently decodes its request union and compares that schema discriminator with this commitment.
Enums§
- Browser
Carrier Profile - Carrier policy selected before any browser dial.
- Browser
Route Role - Route role bound into the provisioning context.
- Browser
Transcript Policy - Explicit dispatch profile for the inner extension. A browser extension is mandatory only on its browser carrier and is rejected as a misclassified payload on every other carrier.
- Browser
Transport Security - Honest transport-security classification. This is kept separate from the application HyKEM requirement so a classical relay cannot raise assurance.
Constants§
- BROWSER_
PROVISIONING_ VERSION - BROWSER_
RPC_ PATH - WebTransport CONNECT path whose accept boundary requires browser provisioning.
- MAX_
BROWSER_ APPLICATION_ BYTES - MAX_
BROWSER_ BINDING_ BYTES - MAX_
BROWSER_ EXTENSION_ BYTES - MAX_
PROVISIONING_ BYTES - MAX_
PROVISIONING_ LIFETIME_ MS
Traits§
Functions§
- bind_
request_ payload - Place accepted-current evidence and the application request in one bounded, canonical transcript before the normal hybrid signature and request HyKEM seal are constructed.
- canonical_
method_ discriminator - Independently decode the canonical top-level Cap’n Proto request-union discriminator from a fully decoded request. Generated service dispatch uses this value; the browser extension only carries the client-side commitment.
- recover_
request_ payload - Recover authenticated evidence after signature verification and HyKEM open. Canonical reserialization rejects alternate encodings as well as Serde’s unknown/duplicate-field rejection.