Decisions are made in meetings and forgotten by the next quarter. Paste the notes, or point the agent to the Notion page where they live, and an Orkeste agent writes a decision record in Confluence: the context, the options considered, the decision, the owner and the date. The decision owner approves the page before it is created.
The problem
Six months later, nobody remembers why the team chose one option over another, and the debate starts again. Decision records are good practice that rarely survives a busy week.
How the workflow runs
Runs: When you start it after a meeting.
Read the notes: The agent reads the notes you paste or the Notion page you name.
Extract the decisions: It identifies each decision, the options considered and the owner.
Check earlier records: It searches Confluence for earlier records on the same topic and links them.
Draft the record: It writes the record in your template.
Approve: The page waits in Validations for the decision owner.
Create the page: The approved record is created in your Confluence space.
The page is created only after the decision owner approves it.
Who does what
Decision writer: Turns meeting notes into decision records.
Decision owner (human): Approves the record before it is published.
What this workflow does not do
Does not read Slack threads or join meetings; it works from notes.
Creates and updates pages; it does not delete pages or change permissions.