Dragon Memory Learning cockpit

Obsidian first. GitHub underneath.

A front end for learning the operating system.

Read tasks in Obsidian. Learn the system here. Capture from brain.jbf.com, Mac Terminal, or Claude/Codex chat.

GitHub stays the backend, not the app you have to live in.

Obsidian NOW.md
GitHub events, log, issues
Claudecontext
Codexwork
Phonecapture

Current tasks

Open Obsidian. Look at NOW.md. Stop there.

If you want to know what to do now, do not open GitHub, Cursor, raw logs, old daily notes, or project folders first.

Obsidian app / NOW.md

Today

Maximum three checkboxes. These are the only tasks for the next 24 hours.

  • Open NOW.md
  • Do one visible task
  • Check it off in Obsidian
Obsidian app / NOW.md

This Week

Open loops that matter before Sunday. New todo: and mem todo items land here.

  • Follow-ups
  • Waiting items
  • Project next steps
Obsidian app / NOW.md

Someday

Loose captures. Do not treat this as the current task list.

  • Ideas
  • Maybe later
  • Raw thoughts
Plain rule: If it is not checked or listed in Today or This Week, it is not your current task view.

Screen map

Which screen am I on?

Each screen has one job. Confusion starts when the same sentence does not say which screen it belongs to.

Obsidian app

Use for: reading and checking current tasks.

Open: NOW.md

Do not: type todo: shorthand here.

memory.jbf.com

Use for: learning how the system works.

Open: this page.

Do not: expect it to store tasks.

brain.jbf.com

Use for: phone/browser dumps and uploads.

Open: brain.jbf.com

Do not: use it as the daily task list.

Mac Terminal

Use for: direct command capture.

Type: mem todo "..."

Result: checkbox in Obsidian This Week.

Claude Code / Codex chat

Use for: agent shorthand during work.

Type: todo: ...

Result: captured by the memory hook.

GitHub

Use for: durable history and issue backend.

Open: only when auditing or fixing the system.

Do not: live there day to day.

Daily loop

Three moves to memorize

1

Read

Open Obsidian and look at NOW.md. That is the cockpit, not GitHub.

2

Capture

Phone/browser: brain.jbf.com. Mac Terminal: mem todo "...". Claude/Codex chat: todo:.

3

Close loops

Open loops are issues. Finished thinking becomes lessons, Q/A, or project memory.

Capture paths

Same system, different front doors

This page teaches the system. It does not store tasks. Use the lane that matches where your hands are.

Where: Obsidian app

Action: open NOW.md, read Today and This Week, then check boxes there. Obsidian is the task view, not the backend.

Best for: daily orientation

Mental model

Every memory has a home

The system should answer one question quickly: what kind of thing is this?

Capture

Loose thought, raw idea, maybe useful later.

mem capture "..."

Todo

Open loop that must not disappear.

mem todo "..."

Lesson

A reusable thing learned from work.

mem lesson "..."

Q/A

A question and answer you should find again.

mem qa "Q" "A"

Session memory

What gets documented automatically?

Shorthand capture is automatic. Full session memory is agent-run closeout until we trust a stop-time hook.

Automatic now

capture:, todo:, lesson:, and remember: are captured by hooks. Git commits, Vercel deployments, and issues also preserve facts.

Closeout required

At the end of real work, the agent runs mem closeout. That writes a readable note in sessions/ plus a ledger event.

Not automated yet

A fully automatic stop-time hook is off until the format proves useful. The goal is reliable memory, not noisy transcripts.

Command builder

Turn a thought into the right capture

Practice

Where should this go?

Build order

Do not make the system clever before it is reliable

  1. Now Obsidian cockpit, GitHub backend, mem CLI, agent hooks.
  2. Next Friendly phone capture: iOS Shortcut, Obsidian mobile button, or tiny private form.
  3. Then Promotion tools that turn captures into project notes, lessons, Q/A, and wiki memory.
  4. Later Dashboards, Graphify, Supabase, and stronger multi-agent automation.