Registration authoring boundaries

UWS registration profiles are inert artifacts for governance and review. They describe selected flows, symbolic credential slots, typed input definitions, steps and success conditions. The supported operating model is human account creation in ordinary browsers. Profile validity and a reviewed humanVerification policy do not guarantee runtime automation capability or successful account creation.

Discovery is an authoring activity. OpenUdon owns its private candidate inventory, coverage limitations, owner corrections and review history; Browsertools supplies observations. An observed page is a candidate, not proof of a working recipe.

New authoring tools should export registration profiles without discovery. Keep coverage (unknown or partial) separate from owner review (pending or reviewed) in private authoring state. Neither review nor an empty limitation list guarantees discovery of every route: authentication, invitations, conditional content and unknown routes can hide additional registration types.

Registration 1.2 is the current profile and call supplement. It retains the 1.1 typed private inputs, checkpoints and one-attempt controls, and requires a reviewed humanVerification policy. Consumers must explicitly support the 1.2 profile and call supplement before browser execution; they must not strip the verification field to downgrade a recipe. See the registration 1.2 profile and 1.2 call supplement for the bounded provider, frame, request and submission rules. Runtimes that choose registration execution remain bound by the selected published profile and call supplement; this guidance changes none of their normative obligations.

The published registration 1.1 schema and accepted 1.1 wire contract remain unchanged, and existing profiles containing the optional discovery member remain valid. Its historical coverage: owner_reviewed value never promises completeness. Preserve such profiles through ordinary parsing and round trips. Do not strip metadata from an already reviewed or digest-bound profile; author a new profile and repeat its applicable reviews if changing those bytes is intended.

Registration types are named flows. Private input envelopes bind the selected flow and exact profile digest. Filled values, including optional fields and checkpoint updates, remain outside packages, Git, prompts and logs. Discovery review does not authorize target contact, submission, retries or account cleanup. This guidance does not introduce a crawler, alter version defaults, or add typed input or verification execution to consumers that have not adopted the corresponding registration version.