Use Verachi
Decisions
Capture, edit, link, and review decisions that sit on top of Slack, Jira, and GitHub.
UpdatedMay 11, 2026
On this page
Decisions are the durable record of what changed, why it changed, and which evidence supports it.
Verachi does not replace Slack, Teams, Jira, or GitHub. It records the decision and points back to the source.
What a decision includes
| Field | Purpose |
|---|---|
| Title | Short name for the decision |
| Resolution | What was decided |
| Rationale & context | Why this direction was chosen |
| Source | Manual, Slack, Teams, Jira, GitHub, document, meeting, or transcript |
| Source link | Link back to the original evidence |
| Status | Draft, Published, or Superseded |
| Projects | The projects this decision belongs to |
| Risk | Current risk posture for the decision |
| People involved | Creator, reviewers, approvers, and latest review state |
| Discussion | Team comments and review history |
| Graph | Related decisions, projects, and evidence |
Create a decision
Manually
- Open Projects.
- Open the project that the decision belongs to.
- Click New decision from the project work area.
- Add a title.
- Open More details if you want to add the summary, source, type, date, or link.
- Save.
After saving, use the detail page to review people involved, add discussion, connect relationships, and flag risks.
From an integration
Use Integrations to connect a source and create a rule.
Supported sources:
- Slack reaction rules
- Microsoft Teams message rules
- Jira issue rules
- GitHub label or pull request rules
Captured decisions should still be reviewed before you rely on them.
Decision statuses
| Status | Meaning |
|---|---|
| Draft | Work in progress |
| Published | Current decision |
| Superseded | Replaced by another decision |
In the database, Published maps to the internal status active.
Detail sections
| Section | Use it for |
|---|---|
| People involved | Creator, approvers, reviewers, and evidence source |
| Details | Rationale, metadata, linked context, and risk posture |
| Graph | Nearby decisions, projects, and evidence |
| Discussion | Review discussion and approval comments |
Common actions
- Edit a decision to change the title, resolution, source, type, date, or relationships.
- Ask Verachi from a decision to start a grounded chat with that decision attached.
- Flag risk when the decision may block or weaken work.
- Publish a draft when it is ready.
- Supersede a decision when a newer one replaces it.