Core Philosophy
The principles that guide how we build Lithora.
1. The Tool Should Do the Busy Work
We believe software should be active, not passive. If you complete a task, the tool should know to update the project status, notify the stakeholders, and generate the weekly report. Humans should focus on high-leverage decision making.
2. Structure Without Straitjackets
Lithora enforces enough structure to keep teams aligned (Projects › Tasks › Subtasks), but remains flexible enough to adapt to your workflow. We don't force you into Scrum, Agile, or Waterfall.
3. Speed is a Feature
Latency is the enemy of flow. Every common action has a keyboard path through the ⌘K palette, edits apply optimistically instead of waiting on a round trip, and changes propagate to your teammates in real time rather than on refresh.
4. Single Source of Truth
There should never be two versions of the truth. If a date changes in the roadmap, it changes in the task list. If a spec is updated, the linked tasks reflect that change.
5. Destructive Actions Should Be Reversible
People hesitate in tools that punish mistakes, and hesitation is how workspaces fill with stale work nobody dares delete. Deleting a work item or a project is a 30-day soft delete with a self-service restore, and permanent removal is a separate, deliberate step. The same instinct applies to the AI agent: it proposes, you approve, and what it did is on the record.
Our Promise
"We build tools for builders. If it doesn't help you ship faster, we remove it."