Your first useful task

What you will achieve

You will create a small project, turn a synthetic meeting note into an action list, save only the facts you approve, then verify that a new session can recover the next step.

Use a learning vault. This exercise uses invented people and dates. It does not need private files, connected mail, a calendar integration or permission to send messages.

Before you start

• Complete installation and verification.
• Open the learning vault in your editor or Obsidian.
• Give your chosen AI agent access to that vault and check its instructions are loaded. See AI agents.
• Choose Community or Pro below. Commands and activation behavior differ.

1. Create the project

For Community, copy 08 - Templates/Project/Project-Folder-Template/ to 02 - Projects/Active/Team workshop/. Keep the supplied PROJECT-CONTEXT.md, memory.md, handoff.md and decision templates. Replace instructional placeholders with the exercise’s objective.

Merge these keys into each Community project context record’s existing YAML frontmatter, with your owner name and actual date. Keep one opening and closing --- pair; do not append a second frontmatter block. If a record has no frontmatter, add one block at the start. Preserve unrelated keys and keep the contents draft until you review them.

---
ai_access: internal
review_status: draft
owner: Your name
updated: 2026-10-19
---

For Pro 1.1.0, use the installed initializer. The first command previews; the second writes. Set $Vault to your learning vault, not your production vault.

$Vault = 'D:\Vaults\KOS-Learning'
pwsh -NoProfile -File "$Vault/scripts/initialize-kos.ps1" -Name "Team workshop" -ScaffoldProfile context-only -DryRun
pwsh -NoProfile -File "$Vault/scripts/initialize-kos.ps1" -Name "Team workshop" -ScaffoldProfile context-only

If you configured custom roles, resolve the projects directory with Get-KOSRolePaths.ps1 -Root $Vault -Role projects and use that location in the prompts. Keep the generated lifecycle metadata intact.

2. Give the agent one bounded task

Save the following as meeting-notes.md inside the project. You can also download the synthetic note.

Meeting: Team workshop planning
Date: 2026-10-19

Agreed: run one 45-minute internal workshop using synthetic examples.
Alex will prepare a three-part outline by October 21.
Sam will confirm the meeting room by October 22.
Open: whether the session should be recorded.
Next action: Alex drafts the outline.

Ask the agent:

Follow the vault's root instructions and context policy. Open the
Team workshop project and read its context files and meeting-notes.md.

Draft an action list with owners and dates. Propose the durable decision,
current handoff and unresolved question. Keep proposals draft and show me
the exact text to review. Do not treat recording as approved.

3. Review and save the facts

Check that the draft contains exactly two action owners, the correct dates, a 45-minute workshop and an unresolved recording decision. If it invented facts, correct them before approval.

After reviewing the exact draft, authorize the saved update:

I approve the 45-minute workshop using synthetic examples, and the listed
owners and dates. Save those accepted facts to the project records.
Recording remains unresolved. Set the next action to drafting the outline.
Show me the files changed. Keep unresolved proposals clearly labeled.

Inspect the files yourself. Put durable constraints in memory.md, current progress and the next action in handoff.md, and the two tasks in actions.md inside Team workshop. Make the handoff point to actions.md. The chat response alone is not a saved record.

For Pro, complete and review the generated memory/handoff pair. Then preview activation and apply only after you have approved both:

pwsh -NoProfile -File "$Vault/scripts/Manage-KOSProjectContext.ps1" -Project "02 - Projects/Active/Team workshop" -Action Activate
pwsh -NoProfile -File "$Vault/scripts/Manage-KOSProjectContext.ps1" -Project "02 - Projects/Active/Team workshop" -Action Activate -Confirm -Apply

Use your resolved project path if it differs. Do not replace Pro’s activation process with Community metadata edits.

4. Start a fresh session

Open a new agent conversation with the same learning vault. Do not paste the old conversation. Ask:

Follow this vault's root instructions. Open the Team workshop project and
load its approved context, current handoff, and referenced action note.

Before continuing, state the approved decision, the two action owners and
dates, the unresolved question, and the exact next action.
Identify the files you used.

5. Verify the result

Check	Expected result
Decision	One 45-minute workshop with synthetic examples
First action	Alex, three-part outline, October 21
Second action	Sam, room confirmation, October 22
Open question	Recording is unresolved
Next action	Alex drafts the outline
Evidence	The saved project files, not a guessed memory of chat

Now approve changing Alex’s due date to October 23. Inspect the saved correction and test another fresh session. It should use October 23. Passing this check demonstrates retrieval for your setup, not perfect recall for every future task.

If the session misses something

Check the working directory, selected adapter, saved files, access classification and Pro activation state. Ask the agent which files it actually read. Use troubleshooting before adding more instructions.

Continue

Use the same loop on a small real project: do work, review changes, save accepted context, close the session, then test the next one.