Knowledge Base & Sync

Dicty bridges spoken architectural decisions and written documentation across local and cloud knowledge bases.

Supported Knowledge Targets#

Configure your destinations in Settings (⌘ ,) → Knowledge Base:

1. Local Files & Obsidian Vaults#

• How it works: Dicty writes directly to Markdown files within an Obsidian vault, local directory, or cloned GitHub repository.
• Setup: Browse and select your root vault folder (e.g. ~/Documents/ObsidianVault).
• Target File: Specify a specific target note or let the AI autonomously find the relevant document.

2. Atlassian Confluence (Cloud)#

• Host URL: https://your-domain.atlassian.net
• Space Key: Target workspace (e.g. ENG or ARCH).
• User Email & API Token: Configure securely in the API Integrations tab.
• Target Page: Select an existing page title or create new hierarchical documentation.

3. Linear Docs#

• Target Workspace: Select specific Linear Teams or Projects.
• Global Document Search: When enabled, the AI searches your entire Linear organization to find where decisions belong.

The Architecture Staging Queue#

Instead of immediately overwriting documentation with every spoken sentence, Dicty uses a Staging Queue:

 🎙 Spoken Thought #1 ("Switch auth to JWT") ────┐
 🎙 Spoken Thought #2 ("Store tokens in Keychain")─┼──> [ Architecture Queue ] ──> [ ⚡️ Synthesize ] ──> [ Visual Diff ]
 📝 Written Code Snippet (Swift Keychain helper) ──┘

1. Switch to Librarian Mode and speak your thoughts throughout your work session.
2. Each thought is tagged with a timestamp, source, and active Git branch.
3. Open the Architecture Queue tab (⌘ , tab 17) to search, edit, or add manual notes.
4. Click ⚡️ Synthesize Architecture Doc. Dicty gathers all thoughts, analyzes context, and synthesizes a cohesive, formatted Markdown document.

Pending Updates & Visual Diff Review#

Before any file or remote document is modified, Dicty stages the change in Pending Updates:

• Side-by-Side Diffing: Compares the original version against proposed changes.
• Syntax Highlighting: Green indicates new additions; red indicates deletions.
• Approve & Publish: Atomically writes to Obsidian or publishes via Confluence/Linear API.
• Reject: Discards the proposed update.