Demo

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.

1 min 41 sFor: Pilot buyer / engineering lead18 steps

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

  1. Click Source-based intakeA meeting note is not an approved decision. Here is the difference. Start in Add to DM, with a source you already have.
    1. Start on "Add to DM" (/add).
    2. Click "Source-based intake". The next view is "Source-based intake" (/add/source).

    What it means: A meeting note is not an approved decision. Here is the difference. Start in Add to DM, with a source you already have.

  2. Click Add source materialChoose Add source material.
    1. Click "Add source material". The next view is "Add source material" (/intake/bundles/new).

    What it means: Choose Add source material.

  3. Fill in the formPaste the note. It holds the choice, and the reason behind it.
    1. 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: Paste the note. It holds the choice, and the reason behind it.

  4. Click Analyze with DMSelect Analyze with DM.
    1. Click "Analyze with DM". The next view is "Pasted notes" (/intake/bundles/bundle-two-reviewers).

    What it means: Select Analyze with DM.

  5. Click ReviewDM proposes one decision candidate. It is a proposal, so it still needs a person. Select Review.
    1. Click "Review". The next view is "Production schema changes" (/candidates/cand-two-reviewers/review).

    What it means: DM proposes one decision candidate. It is a proposal, so it still needs a person. Select Review.

  6. Click ContinueCheck what DM understood, and where it came from. The statement and its reason match the note.
    1. Click "Continue". The next view is "Production schema changes" (/candidates/cand-two-reviewers/review).

    What it means: Check what DM understood, and where it came from. The statement and its reason match the note.

  7. Click NextPlace is optional here, so continue.
    1. Click "Next". The next view is "Production schema changes" (/candidates/cand-two-reviewers/review).

    What it means: Place is optional here, so continue.

  8. Click Continue to RefineCheck lists any blocking issues. DM found none here.
    1. Click "Continue to Refine". The next view is "Production schema changes" (/candidates/cand-two-reviewers/review).

    What it means: Check lists any blocking issues. DM found none here.

  9. Click ContinueRefine is where you would correct the wording. It is right as written.
    1. Click "Continue". The next view is "Production schema changes" (/candidates/cand-two-reviewers/review).

    What it means: Refine is where you would correct the wording. It is right as written.

  10. Click ApproveA person approves. Select Approve.
    1. Click "Approve". The next view is "Pasted notes" (/intake/bundles/bundle-two-reviewers).

    What it means: A person approves. Select Approve.

  11. Click View approved knowledgeDM records the approval as durable knowledge. Open it.
    1. Click "View approved knowledge". The next view is "Knowledge" (/knowledge).

    What it means: DM records the approval as durable knowledge. Open it.

  12. Click Select the decisionIt now sits in the approved Knowledge library. Select it.
    1. Click "Select the decision". The next view is "Knowledge" (/knowledge).

    What it means: It now sits in the approved Knowledge library. Select it.

  13. Click Open decisionOpen the decision.
    1. Click "Open decision". The next view is "Two reviewers for production schema changes" (/decisions/dec-review).

    What it means: Open the decision.

  14. Review approved decisionThe decision has its reason and its source on record.
    1. Review "Approved decision": "What was decided".

    What it means: The decision has its reason and its source on record.

  15. Click Ask DMLater, a new teammate wonders why. They open Ask DM.
    1. Click "Ask DM". The next view is "Ask DM" (/ask-dm).

    What it means: Later, a new teammate wonders why. They open Ask DM.

  16. Fill in the formThey type the question in their own words.
    1. Type "Why do production migrations need two reviewers?" into the "Ask a question about decision memory" field.

    What it means: They type the question in their own words.

  17. Click SendSelect Send.
    1. Click "Send". The next view is "Ask DM" (/ask-dm).

    What it means: Select Send.

  18. Review answer from the approved decisionThe answer comes from the approved decision, and shows the source it rests on. The team's reasoning is there when it's needed.
    1. 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, and shows the source it rests on. The team's reasoning is there when it's needed.

The extraction and the Ask DM answer are not real AI output: both are invented fixtures, so quality, coverage and accuracy of real results are not shown or verified.

Correcting the candidate, requesting evidence, conflicts with earlier decisions, follow-through and outcomes are not demonstrated.

Which roles may approve is not verified; the demo signs in as a workspace editor and the simulated backend accepts the approval.

Descriptive transcript

Read the full transcript, including what happens on screen

Demo environment · synthetic workspace and data · backend responses are simulated. A meeting note is not an approved decision
The extraction result, the checks, the approval, the approved decision 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 shows the sequence DM is designed around: a source becomes a proposal, a person approves it, and only then can it be recalled as approved knowledge. It does not claim every decision in a real workspace is captured or available.

A banner reading "Demo environment · synthetic workspace and data · backend responses are simulated" stays on screen for the whole video.

00:00–00:10 · launch

On screen: Start on "Add to DM" (/add). Click "Source-based intake". The next view is "Source-based intake" (/add/source). A highlight labelled "Source-based intake" marks "Source-based intake You have source material. DM understands it and p…".

Narrator: A meeting note is not an approved decision. Here is the difference.

Narrator: Start in Add to DM, with a source you already have.

00:10–00:13 · material

On screen: Click "Add source material". The next view is "Add source material" (/intake/bundles/new). A highlight labelled "Add source material" marks "Add source material Paste text and/or attach files together. DM analy…".

Narrator: Choose Add source material.

00:13–00:19 · paste

On screen: 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 "The source note".

Narrator: Paste the note. It holds the choice, and the reason behind it.

00:19–00:23 · 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: Select Analyze with DM.

00:23–00:32 · 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: DM proposes one decision candidate. It is a proposal, so it still needs a person.

Narrator: Select Review.

00:32–00:40 · 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: Check what DM understood, and where it came from.

Narrator: The statement and its reason match the note.

00:40–00:44 · place

On screen: Click "Next". The next view is "Production schema changes" (/candidates/cand-two-reviewers/review). A highlight labelled "Next" marks "Next →".

Narrator: Place is optional here, so continue.

00:44–00:50 · check

On screen: Click "Continue to Refine". The next view is "Production schema changes" (/candidates/cand-two-reviewers/review). A highlight labelled "Blocking issues" marks "0".

Narrator: Check lists any blocking issues. DM found none here.

00:50–00:55 · refine

On screen: Click "Continue". The next view is "Production schema changes" (/candidates/cand-two-reviewers/review). A highlight marks "Edit if needed".

Narrator: Refine is where you would correct the wording. It is right as written.

00:55–00:59 · confirm

On screen: Click "Approve". The next view is "Pasted notes" (/intake/bundles/bundle-two-reviewers). A highlight marks "Approve".

Narrator: A person approves. Select Approve.

00:59–01:05 · approved-bundle

On screen: Click "View approved knowledge". The next view is "Knowledge" (/knowledge). A highlight labelled "Approved knowledge" marks "View approved knowledge".

Narrator: DM records the approval as durable knowledge. Open it.

01:05–01:10 · library

On screen: Click "Select the decision". The next view is "Knowledge" (/knowledge). A highlight labelled "The new decision" marks "Any migration that touches production schema needs approval from two…".

Narrator: It now sits in the approved Knowledge library. Select it.

01:10–01:13 · open-decision

On screen: Click "Open decision". The next view is "Two reviewers for production schema changes" (/decisions/dec-review). A highlight labelled "Open the decision" marks "Open decision".

Narrator: Open the decision.

01:13–01:18 · approved

On screen: A highlight labelled "Approved decision" marks "What was decided".

Narrator: The decision has its reason and its source on record.

01:18–01:24 · open-ask

On screen: Click "Ask DM". The next view is "Ask DM" (/ask-dm). A highlight marks "Ask DM".

Narrator: Later, a new teammate wonders why. They open Ask DM.

01:24–01:28 · 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 type the question in their own words.

01:28–01:31 · send

On screen: Click "Send". The next view is "Ask DM" (/ask-dm). A highlight marks "Send".

Narrator: Select Send.

01:31–01:40 · 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, and shows the source it rests on.

Narrator: The team's reasoning is there when it's needed.

Last verified against the product on .

Demo 1 min 12 s12 steps

Why AuzzurA: stop losing the why

An elevator demo explaining lost decision rationale and continuity. The code tells you what changed. Who remembers why?

For: Founder, head of engineering, design partner