Manifests

A manifest can identify and verify policies before loading them. The current TypeScript/JavaScript wrapper does not expose that loading path. Its only policy-loading operation receives inline source; the page is kept in the same topical position as C and Python so the absence is explicit rather than hidden.

Loading path

loadPolicy(domain, id, source) uses the public inline loader, computes the UTF-8 source length and creates a reference session. A failed load preserves the previous policy/session. Loading is rejected while a result is alive. An accepted replacement clears the input buffer.

This JS surface does not expose manifests, in-memory bundles, custom backends or window adapters. Those APIs require separate binding work; low-level C exports are not an alternative JS path. For native manifest loading, use the C Stable API or the Python binding.

The domain's atoms list still constrains quoted constants in inline policy source. It does not turn inline source into a manifest or add manifest metadata, SHA verification, a query whitelist, or multiple policy selection.