Document references
A document reference uses a stable UUID or a local name in one exact namespace and parent scope. A move or rename does not change a UUID reference. Different parents can contain the same local title.
[[id:019a0000-0000-7000-8000-000000000001#section|Label]]
[[name:document:root:Root title]]
[[name:document:019a0000-0000-7000-8000-000000000002:Child title]]
{{{#include id:019a0000-0000-7000-8000-000000000001}}}
{{{#redirect id:019a0000-0000-7000-8000-000000000001}}}
{{{#category id:019a0000-0000-7000-8000-000000000001}}}
[[file:id:019a0000-0000-7000-8000-000000000001]]
[[#link="id:019a0000-0000-7000-8000-000000000002" || file:id:019a0000-0000-7000-8000-000000000001]]Use name:<namespace>:<root-or-parent-UUID>:<escaped-local-title> for an explicit name. Namespaces are document, file, category, template, user, and site. A parent scope defines identity. It does not grant inherited access.
site is a fixed, lowercase source token. A host can show a different display name for each language edition. That label is not a parser alias. Site and host labels such as SevenWiki do not select the Site namespace.
Escape \, :, |, #, [, ], {, and } in a local title with a backslash. Keep #section and |Label outside the reference. Put include arguments before the reference: {{{#include #argument="value" id:UUID}}}.
Bare titles and existing root namespace prefixes remain valid shorthand: [[Title]], [[template:Card]], [[site:Policy]], {{{#include Title}}}, and [[file:logo.png]]. They use the same named reference enum. A malformed or unavailable UUID does not fall back to a parent, path, namespace, or title lookup.
Namespace shorthand belongs to the syntax that defines it. For example, [[template:Card]] selects a Template, but {{{#include template:Card}}} selects the literal Document title template:Card. Write {{{#include #namespace="template" Card}}} or {{{#include name:template:root:Card}}} to include that Template. Browser URL prefixes do not change these source rules. A namespace parameter supplies a default for named references; it does not change a UUID's identity.
The same rule applies to Site. [[site:Policy]] selects a Site document, while {{{#include site:Policy}}} keeps the literal Document title site:Policy. Use {{{#include #namespace="site" Policy}}} or {{{#include name:site:root:Policy}}} to include the Site document. Use [[document:site:Policy]] for the literal Document title in a wiki link.
UUIDs must use the hyphenated form and must be nonnil. UUID v7 is supported. Named local titles allow at most 200 Unicode scalar values and 800 UTF-8 bytes. They cannot contain control characters. The host owns normalization and lookup.
File media requires the resolved document to have the File namespace. Category membership requires the Category namespace. A mismatch affects that occurrence; an ordinary allowed link to the same UUID can remain available.
Missing and unreadable ordinary wiki links use the same unresolved display. They keep the authored display content. Without display content, they show the authored local title or UUID. They do not show a private resolved title, path, or document identity.
The host can make an unresolved named link open its normal name lookup route. That lookup keeps the exact namespace and parent scope and rechecks read access. The display does not disclose whether the target exists. It grants no File, include, or link-preview access. An unresolved UUID does not get a lookup route. The host owns any document creation flow.
Editors can display authorized titles or paths while retaining UUID source text. The parser supplies reference ranges for decoration and completion. The host supplies current authorized candidates. See document reference LSP.