Deep Links (omniscio:// URLs) (part 2)
How deep links are implemented: the resolver behind them, what happens when an agent writes a link that does not resolve, the route each link takes into the app's navigation, and the contracts and tests that hold the behaviour in place.
On this page
What it is
This is part 2 of the Deep Links (omniscio:// URLs) page. It carries how links are resolved and routed in the code, moved here because a single page is capped at 40,000 characters.
Where to find it
Nothing on this page is a surface — part 1 has the link formats and where they take you. What follows is the code behind them, so it is for a reader with the repository open.
How it behaves
Every link form resolves through one resolver and one navigator, so a new link kind is a declaration rather than a new branch. Below is how a link is parsed, what a link that cannot resolve does instead of failing silently, and the contracts that lock it.
Related
- Deep Links (omniscio:// URLs) — part 1 of this page, with the surfaces and the user-facing behaviour.
Last verified 2026-10-01