Everything your team needs to make decisions stick
Record decisions, link them together, and trace why things were built the way they were.
Core Documents
Three documents that capture every decision
Beaket uses three types of documents — one for requirements, one for design, and one for architecture. They link to each other so your team can always trace why something was built the way it was.
Spec
ProductA Spec defines what your team is building and why. Write requirements in a single markdown document that evolves as your understanding deepens.
Status workflow
Draft → Review → Ready
Anyone on the team can confirm readiness — a signal of confidence that the Spec is ready to build from. The system shows who confirmed and when.
Brief
DesignA Brief records a design decision — first redefining the problem through a design lens, then declaring what was decided and why. Anyone can write a Brief.
Two perspectives
Redefinition · Declaration
When a connected Spec changes, the Brief shows a stale signal — a path to what changed, so the author can decide whether the design decision still holds.
ADR
DevelopmentAn Architecture Decision Record documents a technical choice. After acceptance, expression edits are allowed — every change is recorded in the trace. Anyone can write an ADR.
Status workflow
Proposed → Accepted → Superseded
When the decision itself changes, a new ADR supersedes the old one. Both stay visible and linked, preserving the full trail of how technical direction evolved.
Team Workflow
How your team works together
Beaket fits naturally into how teams already work. Roles suggest common paths — anyone can create any document.
Write Spec
Define what your team is building and why.
Request Review
Designers and developers are notified.
Write Brief
Record design decisions derived from the Spec. Anyone can write a Brief.
Write ADR
Record architecture decisions derived from the Spec. Anyone can write an ADR.
Every decision linked
When a Spec changes, related Briefs and ADRs receive stale signals — showing what changed. The right people get notified.
Collaboration
Stay aligned without leaving context
Comments & Decisions
Threaded comments stay attached to the document they belong to. When a discussion reaches a conclusion, create a Brief or ADR directly from the comment — the new document links back to the originating discussion.
@mentions
@ Notify a teammate in any comment. They receive an in-app notification linking directly to the conversation.
Cross-references
[[ Search and insert a reference to another document. Linked documents are automatically connected to each other, so you can navigate between related decisions in either direction.
Full-text search
Cmd+K Search across all Specs, Briefs, and ADRs in your project. Find any decision instantly.
Notifications
The right person gets the right signal at the right time — when a Spec needs review, when a Brief changes, when an ADR goes stale, or when you're @mentioned.
Traceability
Never lose the 'why'
Decisions age. Requirements shift. Beaket makes sure no context gets lost along the way.
Version history
Every edit to a Spec records who changed it, when, and why — each change requires a reason. Select any text to trace its full authorship history down to the sentence.
Transparent decisions
ADRs and Briefs can be edited after acceptance — every change is recorded in the trace. When a decision itself changes, a new document supersedes the old one. Six months later, you can trace exactly when and why a direction changed.
Stale signals
When context shifts, Beaket shows a stale signal — a path to what changed. Navigate to the source, see the diff, and decide whether your decision still holds.
Decision Map
ProSpot gaps before they become problems
A visual map of every decision in your project and how they connect. Each Spec and its derived Briefs and ADRs form a thread. Shared concerns appear as intersections.
Insight signals surface decision health at a glance:
- ●Gap — a Spec is missing derived documents
- ●Stale — a path to what changed since the decision was last reviewed
- ●Coupling — a node appears across multiple threads
Integrations
Bring context in, don't context-switch out
Link GitHub PRs, Jira issues, and more directly in your Specs and ADRs.
GitHub
ProEmbed GitHub PRs and issues directly in Specs and ADRs. Search and insert references without leaving the editor.
Jira
ProLink Jira issues to your decisions. Paste a Jira URL to embed issue details, keeping project management context visible alongside your decisions.
Start making decisions that stick.
Record, connect, and trace every decision — from requirement to design to implementation.
Get Started