Wikilinks Stay, and Your Config Says So

Why Care?

Yesterday's entry suggested OKF might want standard markdown links instead of wikilinks . It doesn't: OKF conformance is frontmatter and a type , nothing about links. The suggestion came from one demo tool that only follows markdown links. So wikilinks stay, and a repo can now say exactly which link syntax it uses.

What's New?

• A links: section in context-v/config.md (the starter) declares the link style new docs use ( wikilink by default, or markdown ), the wikilink forms allowed ( Name , label , [Name](https://github.com/lossless-group/context-vigilance-kit/blob/master/folder/Name) , Name#heading ), and how Name resolves: by filename anywhere in context-v/ .

• The skill follows it: agents link in the declared style, or match the surrounding docs when there's no config.

• The OKF decision's links question is settled: wikilinks stay. OKF's demo visualizer missing them is a limitation of that tool, and a 31-line patch fixes it. The patch isn't part of the kit.

Update, same day: path and alias. The declared default is now Obsidian's full form, [Payment Retry Policy](https://github.com/lossless-group/context-vigilance-kit/blob/master/specs/Payment-Retry-Policy.md) : the file's path, a pipe, and an alias that shows clean text while the filename stays space-free for tools. Links resolve by path first, then by filename. On the site, a wikilink without an alias now shows its filename with - and _ as spaces.