Use Case · Architecture
Architecture Decision Records that write themselves.
Capture the reasoning behind a decision the moment you make it — out loud — and let Dicty shape it into a clean, linkable ADR grounded in the code it affects.
ADRs die in the gap between deciding and documenting. By the time anyone opens the template, the context and trade-offs have evaporated.
Speak the decision once. Dicty structures the context, options, and consequences into a numbered ADR and files it in your canonical hub.
The flow
From spoken thought to filed doc.
Attach the change
Select the PR or branch the decision concerns so the ADR links directly to real code.
Talk it through
Explain what you chose and why you rejected the alternatives — conversationally.
Review the draft
Dicty fills the ADR template: context, decision, status, consequences.
Reconcile & sync
The ADR is reconciled against related records, then exported to your wiki.
Zero template friction
No blank-page paralysis. The structure appears from your spoken intent.
Traceable to code
Every ADR carries links to the PRs and commits that motivated it.
Always numbered
Sequential ADR IDs are assigned and cross-referenced automatically.
# ADR-014: Adopt event sourcing for billing
- Status: Accepted
- Context: Refunds need an auditable ledger (PR #482)
- Decision: Store immutable events; project read models
- Consequences: +auditability, -write complexityStop writing docs. Start speaking them.
More use cases