Products
Breno records what was decided, by whom, when and why, and proposes connections between people, projects and other entities for you to approve.
What it does
Decisions with reasons
Each decision keeps who made it, when, what it rested on and what else was considered, linked to the meeting or document it came from.
Connections you approve
Breno proposes relationships and possible duplicate entities. Nothing changes in your knowledge graph until you approve it.
As it stood on a date
Read the graph as of a past date to see which relationships were known then.
The record of why
Decisions are listed with their status, active, superseded or replaced, so a new decision does not erase the one it replaced.
A copy of the product, drawn with sample data.
Why: Costs per seat rose, and the finance review supported $39.
Also considered: $35, usage-based pricing
Why: Retries and dead-lettering without new code.
Also considered: A database outbox
How it works
Capture
Decisions come out of your meetings, with the summary and action items.
Link
Each decision links to the item it came from.
Review
Proposed connections wait for your approval.
Look back
Move the date to see the graph as it was.
Keep reading
Ask
Answers with numbered citations, from your own material.
OpenKnowledge
Items with versions, owners and where each came from.
OpenTry it with your own material
Create a workspace, put a few real documents in, and ask it something you already know the answer to.