DDL Protocol · PRO-DDL-MDN-001

MDN

Meta Dave Note · Working memory · Not permanent record

A real-time annotation embedded in conversation. The thing that holds a thought in external memory until it becomes internal memory. Not a note-taking system. A cognitive exhaust capture layer.

01
What an MDN is

MDN stands for Meta Dave Note. The name is deliberately personal. It is not a framework. It is not a methodology you adopt. It is a specific operator's working memory made legible during active construction.

The purpose is simple: capture the thought now, without derailing the work. The corpus gets the signal. You get to keep moving. When the thought becomes internalized — when the scaffolding is no longer needed — the MDN stops appearing. The corpus keeps the record. The operator keeps the understanding.

"Working memory, not permanent record. Some scaffold. Some stay. The operator decides."
02
How the format works

The format is minimal by design. A prefix, a colon, the thought. M-count indicates nesting depth — each additional M means a thought within a thought.

*MDN:Primary observation. The thought itself.
*MMDN:Meta observation. A note about the note.
*MMMDN:Meta-meta layer. A thought about the note about the note.
*MMMMDN:Each additional M = one more level of nesting. It goes as deep as needed.

Claude's UI may render the asterisks as bold or italic. That's fine. The *MDN: tag is distinctive enough to serve as an identifier regardless of how it renders.

Dex Jr. sweeps for *MDN: automatically at corpus ingestion. The operator does not need to manage them.

03
The lifecycle

MDNs are not permanent. They exist until they are no longer needed. Internalization is the exit condition.

1
Thought appears during active work
Something needs to be captured but the work shouldn't stop. The MDN holds the thought externally.
2
The corpus receives it
Dex Jr. sweeps the session and ingests the MDN with full context. It is now retrievable and queryable.
3
The operator works with it
Some MDNs scaffold future work. Some name a pattern. Some surface a blocker. Some just capture. All of them are valid.
4
Internalization
The thought becomes internal knowledge. The MDN stops appearing. The scaffolding comes down. The structure it built stays standing.
04
How it emerged

The system was not designed. It emerged. The behavior existed before the format had a name. The operator was already leaving annotations in conversation — thoughts that were too important to lose, not important enough to stop for.

Naming it made it retrievable. It did not create it. The pattern was already there. The protocol is the recognition, not the invention.

"I didn't invent this. I just noticed it. Naming it so I can use it."

The format stabilized through use, not through design. The operator used it until it worked, then noticed what they were actually doing. The protocol wrote itself.

05
Categories

The extractor auto-assigns categories based on content. They can be adjusted manually. Categories are for routing — they tell the corpus what kind of signal this is.

BLD
Building Block
Durable shift in capability or understanding
GOV
Governance
Boundary, disclaimer, or constraint
OBS
Process Observation
Noticing how work is happening
FEAR
Fear Named
Internal blocker surfaced
META
Meta / Recursive
Note about a note
CAP
Capture
Default — raw thought preserved
FUTURE
Future
Time-locked note for later retrieval

MDN Extractor

PRO-DDL-MDN-001

Paste any document — council review, session log, conversation transcript. The extractor pulls every *MDN: and its variants, auto-categorizes, and lets you sort and export before routing to the corpus.

CATEGORY LEGEND

BLDDurable shift in capability or understanding
GOVBoundary, disclaimer, or constraint
OBSNoticing how work is happening
FEARInternal blocker surfaced
METANote about a note
CAPDefault — raw thought preserved
FUTURETime-locked note for later retrieval
Dropdown Logistics — Chaos → Structured → AutomatedDexJr eats at 3am