Machine-readable public surface
Product architecture and workflow
Public explanation of how Smart Links work: one stable public URL, device-aware routing, editable destinations, QR entry behavior, and deterministic fallback rules. The canonical capability contract remains authoritative.
Canonical contract relationship
- Authoritative source
- Public capability governance contract.
- Backed by
-
documentation/canonical/product-capabilities-contract.md - This page does
- Explain workflow and architecture semantics that stay aligned with the contract.
Public routing lifecycle
- 1. A visitor opens the public Smart Link or scans a QR code that points to it.
- 2. Smart Linker reads the stored destinations attached to that public link.
- 3. The router evaluates the request context and selects a destination based on the configured routing model.
- 4. The public link stays stable even when destinations are edited later.
- 5. If no destination applies, Smart Linker renders the public fallback page instead of inventing a target.
Device-aware behavior
| Context | Public behavior |
|---|---|
| iPhone | Routes to the configured App Store destination when present. |
| Android | Routes to the configured Google Play destination when present. |
| Desktop | Uses the configured web fallback when present, otherwise the public fallback page. |
| QR scan | Uses the same stable public URL; QR is a delivery format, not a separate routing system. |
Stable-link and install-link semantics
- One public URL can be reused across campaigns, bios, partner placements, launch pages, and QR assets.
- The destination behind that URL is editable later without reissuing the public link everywhere it appears.
- Install-link behavior is a public entry pattern for app distribution, not a deep-linking or attribution guarantee.
- Same link, same stored destinations, same request context: the routing outcome stays deterministic.
Fallback model
- Configured device-specific destinations take precedence when they are available.
- If a destination is missing, the public fallback page is rendered instead of inventing a redirect target.
- The fallback behavior is deterministic and stays tied to the published public link.
Governance boundaries
- Public: routing concepts, fallback concepts, stable-link behavior, QR semantics, platform-level guarantees, deterministic routing principles.
- Private: infrastructure topology, secrets, anti-abuse internals, deployment mechanics, monitoring details, scoring logic, sensitive security details.
- This page does not expand the capability contract; it explains the workflow semantics behind it.