Our Story
Knowledge that compounds, instead of decaying.
We are a small, remote team of engineers who got tired of watching our architectural decisions get buried in Slack threads and orphaned Google Docs.
Dicty was born from a simple realization: engineers don't hate documentation, they hate the friction of context switching and the futility of maintaining linear logs.
When you solve a hard problem, the "Why" is clear in your mind. But by the time you've opened a PR, reviewed the diff, and responded to CI failures, the architectural nuance is often reduced to a simple commit message: "Refactored auth queue."
We built the Voice-to-Knowledge Engine (VKE) to act as an Architectural Librarian. It listens to your spoken intent, reconciles it against your existing codebase, and builds a Hub-and-Spoke model of your system's truth.
How We Think
Architecture First
We believe documentation is the database of the project. It should be normalized, indexed, and maintained with the same rigor as production code.
Stop the Decay
Documentation that grows linearly with every commit becomes ambiguous, redundant, and ultimately useless. We build tools to reconcile intent.
Data Sovereignty
You control the rules of your documentation. By syncing directly to Obsidian, Notion, or your own GitHub wikis, you own your knowledge base.