Build a small linked note library and answer with source names.
Build one thingCheck it worksChoose an extension
Module 06 / Build together
Before you start.
01
You already know
Module 02. Three fictional notes ready.
02
Open these tools
Plain-text editor; Obsidian optional; an existing AI chat tool.
03
Check the requirement
Plain Markdown needs no sync subscription or AI API.
Module 06 / Build together
Your first small win.
Turn this fictional note into Markdown with Title, Key facts, Open questions and Related notes: Book club meets Saturday at 10:00 in the community room. Entry is free. The organiser has not confirmed refreshments.
Module 06 / Build together
What happens between input and output?
1Capture an idea in a small note.
2Link related notes instead of hiding them in long documents.
3AI answers only from the notes you actually provide.
Module 06 / Build together
Step 01. Create a notes folder.
1Make second-brain/inbox, projects and reference.
2Open it in your editor or as an Obsidian vault.
3Use fictional or consented notes.
Module 06 / Build together
Step 02. Capture three small notes.
1Write meetup.md, preferences.md and ideas.md.
2Give each a title and source/date.
3Keep unknown facts explicitly unknown.
Module 06 / Build together
Step 03. Link useful connections.
1Add [[meetup]] in the project note if using Obsidian.
2Use ordinary file links in other editors.
3Check the link opens the intended note.
Module 06 / Build together
Step 04. Ask from supplied notes.
1Paste three labelled notes into a fresh AI chat.
2Copy the source-grounded prompt.
3Keep the note names attached to their text.
Module 06 / Build together
Step 05. Test what it does not know.
1Ask whether refreshments are confirmed.
2The answer should identify the missing confirmation.
3Check every citation against the supplied note.
Module 06 / Build together
Step 06. Keep it maintained.
1Move reviewed notes out of inbox.
2Add a decision and next action to a project.
3Export or back up the local folder.
Module 06 / Build together
Make the working version.
Answer only from the labelled notes below. Cite note filenames for each factual answer. If the notes do not establish a fact, say Not in my notes. Do not use outside knowledge. Question: [question]. Notes: [paste labelled notes].
Module 06 / Build together
Ask for a review. Then check it.
Check this answer against the supplied notes. List unsupported claims, incorrect filename citations and missing caveats. Suggest a facts-only revision. Notes: [paste]. Answer: [paste].
Module 06 / Build together
Prove your result works.
1Three notes have titles and sources.
2Links open correctly.
3Unsupported questions receive an explicit unknown.
Module 06 / Build together
When it does not work yet.
01
An invented citation
Open the named note and remove unsupported text.
02
It cannot see my vault
Paste or upload approved notes; a prompt alone grants no file access.
Module 06 / Build together
Choose your next challenge.
01
Core complete
Show one checked output to a partner.
02
Extension 1
Add tags and a project dashboard.
03
Extension 2
Explore retrieval search only after the small library works.
Module 06 / Build together
Keep the result. Keep the evidence.
Build a small linked note library and answer with source names.
Save your filesSave your promptName the next change
Module 06 / Build together
Sources you can check.
01
Obsidian
Manage vaults
02
NIST
Generative AI Profile
Make your notes useful again.
3 minutes
Outcome: Build a small linked note library and answer with source names. This is a 60-minute in-person laptop session after preflight. No setup-duration guarantee. Core first, extensions second.
References
Before you start.
3 minutes
Plain Markdown needs no sync subscription or AI API. The facilitator verifies accounts, installed tools and model/host connections before the session. Pair up if setup is incomplete. Do not create accounts or incur costs without understanding the provider terms.
References
Your first small win.
5 minutes
Quick win: Create one note with a question, an answer and a source. Aim for a visible result in the first 15 minutes after preflight. Explain that generated code/output is untested until the learner checks it. If tools are unavailable, inspect the prepared example with a partner.
References
What happens between input and output?
3 minutes
Ask a learner to explain each stage in their own words. This is a teaching model, not a promise that all tools behave identically.
References
Step 01. Create a notes folder.
3 minutes
Perform these numbered actions on the laptop. Pause after the step and inspect the result. Use fictional or approved material.
Use fictional practice inputs. Ask learners to show their work, not just the final answer.
References
Ask for a review. Then check it.
4 minutes
Use fictional practice inputs. Ask learners to show their work, not just the final answer.
References
Prove your result works.
6 minutes
These are manual acceptance tests for the learner to perform. No test is claimed to have run merely because it appears here. Ask pairs to demonstrate one pass and one corrected failure.
References
When it does not work yet.
4 minutes
Choose the observed symptom. Change one thing and rerun the smallest test. Avoid restarting the whole project or adding tools before diagnosing the current step.
References
Choose your next challenge.
5 minutes
Experienced learners use the extensions while beginners complete the same core outcome. An extension is optional, not a prerequisite for participating.
References
Keep the result. Keep the evidence.
3 minutes
Save the working version before leaving. Add a short note: what worked, what needed correction and what you would try next. The next module builds on the saved output.
References
Sources you can check.
2 minutes
Primary sources checked during course creation on 2026-10-08. Provider interfaces and availability can change. The examples, prompts and activities are original community teaching designs. Source links explain capabilities; they do not prove these fictional exercises were executed.
