When your result differs from a video tutorial, use a reviewed Damas transcript to find the last matching result and the first observable difference. Compare those two checkpoints with the demonstration before changing anything. This manual review produces a focused question about the failed attempt; it does not diagnose the cause automatically or guarantee a repair.
Prepare the explanation
Damas supports public, on-demand YouTube, Instagram and X video links up to 90 minutes. On iPhone it requires iOS 18.6 or later, internet, Premium and AI processing consent. Only process material you are authorized to use. Private, restricted and live videos are unsupported; inaccessible public sources can also fail.
- Open the tutorial on its original platform and retain its link and title in your working note.
- Paste the supported link into Damas. Follow the current app instructions for transcription and review the AI consent.
- Wait for processing, then read the transcript alongside the video. Correct uncertain words, numbers and units before reusing the text.
- Watch demonstrations and read visible labels yourself. Speech transcription cannot supply an unspoken setting or a screen-only result.
- Edit and copy the checked text. A built-in summary can orient you, but use the full explanation to preserve order and exceptions.
Find the earliest observable difference
Stop adding later steps to an unexplained result. In a separate working note, write what you expected, what you actually observed and the last point where your result matched the demonstration. Use descriptions you can check, such as “the copied table has no visible rows”, rather than a diagnosis such as “the app deleted my data”. A mismatch is an observation, not proof of its cause.
Work forward from the last matching checkpoint. For each intervening operation, compare the source input, stated prerequisite, action and visible result with your own attempt. Keep “matches”, “differs” and “cannot compare” separate. Stop at the first difference you can establish; if the tutorial never shows that intermediate result, mark the checkpoint unavailable instead of assuming it matched.
Record possible causes in a separate column. A different starting file, an omitted instruction or an unexplained setting is something to investigate, not a confirmed explanation. Only carry a corrective action into your note when the source actually states its condition and remedy. If those are missing, prepare a question instead of inventing a repair. Do this comparison in notes; the method does not require repeating destructive operations.
Fictional example: a table disappears from view
This invented teaching example is not a real recording, a test or a Damas feature. Imagine a tutorial that copies a table, applies a category filter and then displays several rows. Your copy is visible before filtering, but no rows are visible afterward.
| Record | What to write |
|---|---|
| Last matching checkpoint | The copied table is visible before the filter. |
| First observed difference | After filtering, the tutorial shows rows; your view shows none. |
| Check next | Compare the category value and the starting rows with what the source actually shows. |
| Still unknown | Whether a different category, different input or another condition explains the result. |
The empty view alone does not establish that rows were deleted. If the source does not explain this case, do not invent a recovery command. Keep the original material intact and ask what prerequisite or example input is needed.
Prepare a question someone can answer
Copy a short handoff: source link and title; source operation and checked passage; your starting conditions; expected and observed results; first differing checkpoint; and one question. For the fictional case: “Which category value and starting rows are required for the example?” Label the observation as yours and the passage as source evidence. Do not turn an untested possibility into a claim about the tutorial.
The tutorial checklist helps prepare the steps before an attempt; use this review when an attempt has diverged. The quotation guide helps check exact wording. Damas makes the explanation editable and copyable so you can review the relevant passage without relying on memory.
No external LLM is needed. Optional formatting in another LLM requires permission to share the copied text and a check of every proposed cause; it is not a Damas integration. Keep uncertainty, source evidence and your observations separate. Never invent quotes, facts, owners or deadlines.
Processing time and accuracy vary. Damas does not download media, embed subtitles or process offline. Premium cannot make an inaccessible source available. Keep the source link with the final checklist so unresolved items can be revisited.
Damas Technologies LLC