Why Hjarni outside Cascade's workspace
Cascade reads files in your workspace when you open them. That works for code. It does not work for design docs in someone's Notion, decisions in a Linear comment, or the runbook a teammate keeps in their Apple Notes. Hjarni is one place all of that can land, with MCP search built in.
Windsurf's planning step is the highest-leverage moment to inject context. If the plan is wrong, the execution is wrong. Folder-level AI instructions in Hjarni let you steer Cascade's plans per project: 'in the Payments folder, never propose schema changes without an ADR'.
Cascade is one editor. Engineers use more than one. Hjarni stays put while editors change underneath it, so the knowledge base you build today is still useful when Windsurf updates, when you try a new editor, or when a new teammate joins.