From evidence to a trusted decision
Show one end-to-end decision lifecycle with evidence and human approval. A meeting note is not an approved decision. Here is the difference.
For: Pilot buyer / engineering lead
Demo
Why AuzzurA: stop losing the why
An elevator demo explaining lost decision rationale and continuity. The code tells you what changed. Who remembers why?
Read the steps OR watch the video. Both teach the same outcome, and neither is needed for the other.Jump to the video
Quick steps
Fill in the formTake one note that holds a real decision, and add it to DM.
- Start on "Add source material" (/intake/bundles/new).
- Type "Sync notes: we agreed that any migration touching production schema needs two reviewers. A single-reviewer migration dropped an index in the spring. Priya owns the rule." into the "Paste text" field.
What it means: Take one note that holds a real decision, and add it to DM.
Click Analyze with DMDM reads it and proposes a decision.
- Click "Analyze with DM". The next view is "Pasted notes" (/intake/bundles/bundle-two-reviewers).
What it means: DM reads it and proposes a decision.
Click ReviewA proposal is not yet team knowledge. A person has to review it.
- Click "Review". The next view is "Production schema changes" (/candidates/cand-two-reviewers/review).
What it means: A proposal is not yet team knowledge. A person has to review it.
Click ContinueThe reviewer checks the statement and its reason against the source.
- Click "Continue". The next view is "Production schema changes" (/candidates/cand-two-reviewers/review).
What it means: The reviewer checks the statement and its reason against the source.
Click NextThen the review steps on.
- Click "Next". The next view is "Production schema changes" (/candidates/cand-two-reviewers/review).
What it means: Then the review steps on.
Click Continue to RefineDM shows what it found before approval.
- Click "Continue to Refine". The next view is "Production schema changes" (/candidates/cand-two-reviewers/review).
What it means: DM shows what it found before approval.
Click ContinueWording can be corrected here.
- Click "Continue". The next view is "Production schema changes" (/candidates/cand-two-reviewers/review).
What it means: Wording can be corrected here.
Click ApproveThen a person approves it.
- Click "Approve". The next view is "Pasted notes" (/intake/bundles/bundle-two-reviewers).
What it means: Then a person approves it.
Click Ask DMMonths later, a new teammate asks why.
- Click "Ask DM". The next view is "Ask DM" (/ask-dm).
What it means: Months later, a new teammate asks why.
Fill in the formThey ask in their own words.
- Type "Why do production migrations need two reviewers?" into the "Ask a question about decision memory" field.
What it means: They ask in their own words.
Click SendSelect Send.
- Click "Send". The next view is "Ask DM" (/ask-dm).
What it means: Select Send.
Review answer from the approved decisionThe answer comes from the approved decision, with the source it rests on. The reason is still there, long after the meeting.
- Review "Answer from the approved decision": "Any migration that touches production schema needs approval from two reviewers, because a…".
What it means: The answer comes from the approved decision, with the source it rests on. The reason is still there, long after the meeting.
Next, see the product workflow.
No time, cost or quality benefit is claimed or measured.
Real extraction quality and Ask DM answer quality are not shown: both are invented fixtures.
Other ways DM carries approved decisions to people and tools (for example Prepare context) are not shown.
Next lesson
Descriptive transcript
Read the full transcript, including what happens on screen
Demo environment · synthetic workspace and data · backend responses are simulated. From a note, to an approved decision, to an answer
Extraction, the checks, the approval and the Ask DM answer are SIMULATED: this guide uses a synthetic workspace and fixture data, not a deployed backend or a real AI run. It makes no measurement or return-on-investment claim, and it does not claim every decision in a real workspace is captured or available; only decisions that were added and approved can be recalled.
A banner reading "Demo environment · synthetic workspace and data · backend responses are simulated" stays on screen for the whole video.
00:00–00:10 · pain
On screen: The AuzzurA DM logo, the title "Why AuzzurA: Stop Losing the Why" and the subtitle "From a note, to an approved decision, to an answer".
Narrator: The code tells you what changed. But who remembers why?
Narrator: Decisions are made in meetings and notes. When people move on, the reason can go with them.
00:10–00:16 · paste
On screen: Start on "Add source material" (/intake/bundles/new). Type "Sync notes: we agreed that any migration touching production schema needs two reviewers. A single-reviewer migration dropped an index in the spring. Priya owns the rule." into the "Paste text" field. A highlight marks "One decision-bearing note".
Narrator: Take one note that holds a real decision, and add it to DM.
00:16–00:21 · analyze
On screen: Click "Analyze with DM". The next view is "Pasted notes" (/intake/bundles/bundle-two-reviewers). A highlight marks "Analyze with DM".
Narrator: DM reads it and proposes a decision.
00:21–00:27 · candidate
On screen: Click "Review". The next view is "Production schema changes" (/candidates/cand-two-reviewers/review). A highlight labelled "Nothing is approved yet" marks "Source material produces candidates for review. Approved candidates b…".
Narrator: A proposal is not yet team knowledge. A person has to review it.
00:27–00:32 · understand
On screen: Click "Continue". The next view is "Production schema changes" (/candidates/cand-two-reviewers/review). A highlight labelled "Statement and reason" marks "Any migration that touches production schema needs approval from two…".
Narrator: The reviewer checks the statement and its reason against the source.
00:32–00:36 · place
On screen: Click "Next". The next view is "Production schema changes" (/candidates/cand-two-reviewers/review).
Narrator: Then the review steps on.
00:36–00:40 · check
On screen: Click "Continue to Refine". The next view is "Production schema changes" (/candidates/cand-two-reviewers/review).
Narrator: DM shows what it found before approval.
00:40–00:43 · refine
On screen: Click "Continue". The next view is "Production schema changes" (/candidates/cand-two-reviewers/review).
Narrator: Wording can be corrected here.
00:43–00:47 · confirm
On screen: Click "Approve". The next view is "Pasted notes" (/intake/bundles/bundle-two-reviewers). A highlight marks "Approve".
Narrator: Then a person approves it.
00:47–00:51 · open-ask
On screen: Click "Ask DM". The next view is "Ask DM" (/ask-dm). A highlight marks "Ask DM".
Narrator: Months later, a new teammate asks why.
00:51–00:55 · ask
On screen: Type "Why do production migrations need two reviewers?" into the "Ask a question about decision memory" field. A highlight marks "Your question".
Narrator: They ask in their own words.
00:55–00:58 · send
On screen: Click "Send". The next view is "Ask DM" (/ask-dm). A highlight marks "Send".
Narrator: Select Send.
00:58–01:07 · answer
On screen: A highlight labelled "Answer from the approved decision" marks "Any migration that touches production schema needs approval from two…".
Narrator: The answer comes from the approved decision, with the source it rests on.
Narrator: The reason is still there, long after the meeting.
01:07–01:11 · close
On screen: The AuzzurA DM logo, the heading "Next: see the product workflow" and the line "Add a source, review it, approve it, then find it again"
Narrator: Next, see the product workflow.
Last verified against the product on .
Related tutorials