CLAUDE.md

@@ -128,10 +128,10 @@ created: YYYY-MM-DD
 ---
 
 Relevant Notes:
-- [[related-claim]] — how it relates
+- related-claim — how it relates
 
 Topics:
-- [[domain-map]]
+- domain-map
 ```
 
 ## How to Propose Claims (Proposer Workflow)
@@ -210,7 +210,7 @@ For each proposed claim, check:
 5. **Duplicate check** — Does this already exist in the knowledge base? (semantic, not just title match)
 6. **Contradiction check** — Does this contradict an existing claim? If so, is the contradiction explicit and argued?
 7. **Value add** — Does this genuinely expand what the knowledge base knows?
-8. **Wiki links** — Do all `[[links]]` point to real files?
+8. **Wiki links** — Do all `links` point to real files?
 
 ### Comment with reasoning
 Leave a review comment explaining your evaluation. Be specific:
@@ -288,7 +288,7 @@ When your session begins:
 ## Design Principles (from Ars Contexta)
 
 - **Prose-as-title:** Every note is a proposition, not a filing label
-- **Wiki links as graph edges:** `[[links]]` carry semantic weight in surrounding prose
+- **Wiki links as graph edges:** `links` carry semantic weight in surrounding prose
 - **Discovery-first:** Every note must be findable by a future agent who doesn't know it exists
 - **Atomic notes:** One insight per file
 - **Cross-domain connections:** The most valuable connections span domains

schemas/musing.md

@@ -34,7 +34,7 @@ tags: [cross-domain, architecture, case-study, pattern, ...]
 Freeform. No quality gates. The point is to think, not to publish. However:
 
 - Date your additions so the evolution of thinking is visible
-- Link to relevant claims with `[[wiki links]]` where connections exist
+- Link to relevant claims with `wiki links` where connections exist
 - **One-way linking only:** musings may link to claims, but claims must NEVER link back to musings. Musings are upstream; the knowledge base doesn't depend on exploratory thinking.
 
 ### Conventions (use these inline markers)