Documented release
v47.3.0
custom-domain continuity and sign-in experience
Release date 2026-04-09
Outcome
Outcome
v47.3.0 is the custom-domain continuity and sign-in experience release. It keeps the current v47.x product truth intact while making business custom domains behave like Receiz-authenticated surfaces instead of isolated public mirrors, and it removes the dead-end passkey experience inside in-app browsers by opening the email path immediately with accurate guidance.
Changes
What changed
a signed-in Receiz user can arrive on a verified custom…
a signed-in Receiz user can arrive on a verified custom domain and reuse that existing Receiz authority
Technical and authority boundary
a signed-in Receiz user can arrive on a verified custom domain and reuse that existing Receiz authority
- Why
- v47.3.0 is the custom-domain continuity and sign-in experience release. It keeps the current v47.x product truth intact while making business custom domains behave like Receiz-authenticated surfaces instead of isolated public mirrors, and it removes the dead-end passkey experience inside in-app browsers by opening the email path immediately with accurate guidance.
- Capability enabled
- a signed-in Receiz user can arrive on a verified custom domain and reuse that existing Receiz authority
- Compatibility
- The v47.3.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v47.3.0 migration record remains the exact adoption boundary for this outcome.
the custom domain mints its own local session without weakening…
the custom domain mints its own local session without weakening the canonical Receiz identity, passkey, or signing model
Technical and authority boundary
the custom domain mints its own local session without weakening the canonical Receiz identity, passkey, or signing model
- Why
- v47.3.0 is the custom-domain continuity and sign-in experience release. It keeps the current v47.x product truth intact while making business custom domains behave like Receiz-authenticated surfaces instead of isolated public mirrors, and it removes the dead-end passkey experience inside in-app browsers by opening the email path immediately with accurate guidance.
- Capability enabled
- the custom domain mints its own local session without weakening the canonical Receiz identity, passkey, or signing model
- Compatibility
- The v47.3.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v47.3.0 migration record remains the exact adoption boundary for this outcome.
logout and signing flows remain symmetric across the business host and receiz.com 2
logout and signing flows remain symmetric across the business host and receiz.com 2. In-App Browsers Stop Dead-Ending Passkey Sign-In Receiz now handles embedded browser reality directly:
Technical and authority boundary
logout and signing flows remain symmetric across the business host and receiz.com 2. In-App Browsers Stop Dead-Ending Passkey Sign-In Receiz now handles embedded browser reality directly:
- Why
- v47.3.0 is the custom-domain continuity and sign-in experience release. It keeps the current v47.x product truth intact while making business custom domains behave like Receiz-authenticated surfaces instead of isolated public mirrors, and it removes the dead-end passkey experience inside in-app browsers by opening the email path immediately with accurate guidance.
- Capability enabled
- logout and signing flows remain symmetric across the business host and receiz.com 2. In-App Browsers Stop Dead-Ending Passkey Sign-In Receiz now handles embedded browser reality directly:
- Compatibility
- The v47.3.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v47.3.0 migration record remains the exact adoption boundary for this outcome.
sign-in popovers and pages detect likely in-app browsers before prompting for passkeys
sign-in popovers and pages detect likely in-app browsers before prompting for passkeys
Technical and authority boundary
sign-in popovers and pages detect likely in-app browsers before prompting for passkeys
- Why
- v47.3.0 is the custom-domain continuity and sign-in experience release. It keeps the current v47.x product truth intact while making business custom domains behave like Receiz-authenticated surfaces instead of isolated public mirrors, and it removes the dead-end passkey experience inside in-app browsers by opening the email path immediately with accurate guidance.
- Capability enabled
- sign-in popovers and pages detect likely in-app browsers before prompting for passkeys
- Compatibility
- The v47.3.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v47.3.0 migration record remains the exact adoption boundary for this outcome.
email fallback expands automatically instead of waiting for a WebAuthn failure
email fallback expands automatically instead of waiting for a WebAuthn failure
Technical and authority boundary
email fallback expands automatically instead of waiting for a WebAuthn failure
- Why
- v47.3.0 is the custom-domain continuity and sign-in experience release. It keeps the current v47.x product truth intact while making business custom domains behave like Receiz-authenticated surfaces instead of isolated public mirrors, and it removes the dead-end passkey experience inside in-app browsers by opening the email path immediately with accurate guidance.
- Capability enabled
- email fallback expands automatically instead of waiting for a WebAuthn failure
- Compatibility
- The v47.3.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v47.3.0 migration record remains the exact adoption boundary for this outcome.
the UI tells the truth
the UI tells the truth: continue with email here, or open the page in Safari, Chrome, or the default browser to use passkeys 3. Custom-Domain First Paint Matches Receiz More Closely The profile route on a custom domain now trusts its own branded host for proxied hero media fetches, which prevents the first avatar / header render from intermittently falling into a broken state until reload.
Technical and authority boundary
the UI tells the truth: continue with email here, or open the page in Safari, Chrome, or the default browser to use passkeys 3. Custom-Domain First Paint Matches Receiz More Closely The profile route on a custom domain now trusts its own branded host for proxied hero media fetches, which prevents the first avatar / header render from intermittently falling into a broken state until reload.
- Why
- v47.3.0 is the custom-domain continuity and sign-in experience release. It keeps the current v47.x product truth intact while making business custom domains behave like Receiz-authenticated surfaces instead of isolated public mirrors, and it removes the dead-end passkey experience inside in-app browsers by opening the email path immediately with accurate guidance.
- Capability enabled
- the UI tells the truth: continue with email here, or open the page in Safari, Chrome, or the default browser to use passkeys 3. Custom-Domain First Paint Matches Receiz More Closely The profile route on a custom domain now trusts its own branded host for proxied hero media fetches, which prevents the first avatar / header render from intermittently falling into a broken state until reload.
- Compatibility
- The v47.3.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v47.3.0 migration record remains the exact adoption boundary for this outcome.
Purpose
Why it matters
v47.3.0 is the custom-domain continuity and sign-in experience release. It keeps the current v47.x product truth intact while making business custom domains behave like Receiz-authenticated surfaces instead of isolated public mirrors, and it removes the dead-end passkey experience inside in-app browsers by opening the email path immediately with accurate guidance.
Available outcomes
Capabilities now available
a signed-in Receiz user can arrive on a verified custom…
a signed-in Receiz user can arrive on a verified custom domain and reuse that existing Receiz authority
the custom domain mints its own local session without weakening…
the custom domain mints its own local session without weakening the canonical Receiz identity, passkey, or signing model
logout and signing flows remain symmetric across the business host and receiz.com 2
logout and signing flows remain symmetric across the business host and receiz.com 2. In-App Browsers Stop Dead-Ending Passkey Sign-In Receiz now handles embedded browser reality directly:
sign-in popovers and pages detect likely in-app browsers before prompting for passkeys
sign-in popovers and pages detect likely in-app browsers before prompting for passkeys
email fallback expands automatically instead of waiting for a WebAuthn failure
email fallback expands automatically instead of waiting for a WebAuthn failure
the UI tells the truth
the UI tells the truth: continue with email here, or open the page in Safari, Chrome, or the default browser to use passkeys 3. Custom-Domain First Paint Matches Receiz More Closely The profile route on a custom domain now trusts its own branded host for proxied hero media fetches, which prevents the first avatar / header render from intermittently falling into a broken state until reload.
Primitive boundary
Primitives affected
- identity
- provenance
- media
- verification
- public-witness
- continuity
- note
Compatibility
Compatibility
Archive compatibility evidence boundary
No dedicated compatibility record is bound to this projection.
Treat compatibility as unknown; version or date proximity is not evidence.
Migration
Migration
Required: unknown
No explicit migration source is bound; no migration is inferred from dates.
Qualification
Conformance
No immutable conformance evidence is assigned in this projection.
Control boundary
Governance
- Verification
- Unknown
- Declared change class
- No separate classification record
- Release approval
- No separate approval record
- Risk owner
- No separate assignment recorded
Publication, deployment, production smoke, and attestation remain independent evidence dimensions unless exact sources establish them.
Registry boundary
Registry
No registry is bound where the canonical release family does not carry one.
Archive projection
Audience, domain, and change-kind facets
- Audiences
- developers · businesses · creators · institutions · people
- Domains
- identity · provenance · media · verification · public-witness · continuity · note
- Change kinds
- capability
Independent dimensions
Release boundary status
- Repository release
- Documented
- Git tag
- Absent
- Package publication
- Unknown
- Deployment
- Unknown
- Production smoke
- Unknown
- Signed attestation
- Unknown
Exact source bytes
Provenance
This Academy record is a projection beneath its sources. Record SHA-256 d0f46be88146e86ad27b795768186a6652ac2624a974d29310e967e3a8409bc6. Source-family inventory: complete.
SHA-256 20294ebccd323c5b523c45f2dcdae073d7c59ec5d46ca5027a5378876117e013SHA-256 84c885e3fa0172777e1855e485ccc12a148958e1e38996f0f3753de00797837eSHA-256 0c68703af9e02780c0e6ff307ffd0c5a9fdfa25dc69d07ca96732686ee70f6fc