Source monitoring: where your memories came from
You know something about a friend: they have been thinking about leaving their job. You are sure of it. What you cannot produce, if you stop and check, is how you know. Did they tell you over coffee? Did a mutual friend mention it? Did you read it between the lines of something they posted and fill in the rest yourself? The fact is sitting in memory, clear and usable. The part that says where it came from is gone.
This happens constantly, and most of the time it does not matter. You act on the fact and never check where it came from. But the gap is real, and it has a name. A memory does not arrive stamped with its source. The source is something the mind reconstructs later, each time the memory is retrieved, and it gets the answer wrong more often than anyone is comfortable admitting.
Memory is unreliable about itself in more than one way. It rewrites the most vivid moments on every retelling. It converts lived scenes into filed facts. Source monitoring is a third failure, and a quieter one. It is not about what happened. It is about where you learned it.
The 1993 paper that named the problem
In 1993, the psychologists Marcia Johnson, Shahin Hashtroudi, and D. Stephen Lindsay published a paper in Psychological Bulletin with a deliberately plain title: “Source monitoring.” It gathered two decades of scattered experiments into one framework for a question the field had mostly treated as minor: how does a person decide where a memory came from?
Their conclusion was that the brain never stores it. A memory is not filed with a tag reading “acquired by watching it happen, on a Wednesday, in the kitchen.” Origin is not a recorded property. It is a judgment, made after the fact, reconstructed from the memory’s own characteristics. Johnson and her colleagues called the set of processes behind that judgment source monitoring, and the moments it fails source monitoring errors.
A memory does not come with a label
The framework’s central observation is that memories from different origins tend to carry different signatures.
A memory of something you actually perceived is usually rich in perceptual detail: sound, color, the layout of a room, a time of day. It carries contextual detail about where you were and what surrounded the event. A memory of something you only imagined or thought through tends to be thinner in those, and heavier in a different trace: a record of the mental effort that built it, the cognitive operations you performed to construct the scene.
Source monitoring is the process of reading those signatures and inferring an origin from them. Most of the time it runs fast and below awareness. You do not deliberate over whether you saw the car or dreamed it; you simply know. But it is still a decision under uncertainty, and like any such decision it can land wrong. When two sources produce memories that look alike, or when the distinguishing detail has worn away, the judgment misfires. The memory stays. It just gets reassigned to a source that was never its own.
Three ways to get the source wrong
Johnson, Hashtroudi, and Lindsay separated the problem into three kinds of judgment.
External source monitoring is telling two outside sources apart. Which of two colleagues made the remark in the meeting. Whether a piece of news came from an article you read or a friend who mentioned it.
Internal source monitoring is telling two inside sources apart. Whether you actually said the thing out loud or only rehearsed saying it. Whether you sent the message or composed it in your head and never hit send.
Reality monitoring is telling an inside source from an outside one: whether something happened or you imagined it, whether a memory is of a real conversation or a dream. This was the original problem Johnson and Carol Raye had named in a 1981 paper in Psychological Review; the 1993 framework widened it into the general case.
In daily life all three show up as the same small, familiar failures. “Have I already told you this?” “Did I lock the door, or only think about locking it?” “Was that my idea, or did I pick it up in a meeting and forget I did?” In each one the content is intact. What fails is the attribution of where it came from.
The label fades before the memory does
The source signal is fragile, and it decays faster than the thing it labels.
Perceptual and contextual detail are exactly what time strips away first. A year after a conversation you still hold the rough sense of what was said. The texture that would have told you the room, the day, the voice, the channel: that has thinned out. And the rough sense of a thing does not carry its own origin. So source monitoring errors grow with delay, not because the memory weakened but because the evidence the judgment depends on did.
This is why cryptomnesia happens. Cryptomnesia is the experience of having an idea, feeling certain it is your own, when in fact you encountered it somewhere else. Alan Brown and Dana Murphy demonstrated it in a 1989 experiment: people who had brainstormed in a group later reproduced other participants’ ideas as their own, with no sense of borrowing. They were not dishonest. The idea was in memory. The label saying “this came from the person across the table” was not.
It is also why misinformation takes hold. The 1993 review treats the eyewitness misinformation effect, where a detail suggested after an event gets folded into the memory of the event itself, as a source monitoring failure. The suggested detail and the witnessed detail end up looking alike enough in memory that the judgment cannot keep them apart, and the later one is absorbed into the earlier scene.
A record does not have to guess
Set a recorded trace next to a memory and the difference is structural.
A line of data does not need source monitoring, because its source is not inferred. It is fixed at the moment the record was made. A commit in your GitHub history came from GitHub; it cannot later turn out to have been something you dreamed. A calendar event names the person who organized it and the people who attended, so there is no deciding, months on, which of two colleagues called the meeting. A check-in names the venue, and the restaurant you would otherwise misremember cannot quietly overwrite it. A message you actually sent is in the sent folder; one you only meant to send is not.
This is the inversion worth noticing. Human memory stores content well and stores source poorly, then reconstructs the source on demand from whatever detail is left. A record does the opposite by design. The source, the timestamp, the tool, the people involved are the primary facts. The content is attached to them, not the other way around.
What a sourced diary keeps
deariary builds a diary entry each day out of the records your tools already keep: the events on your calendar, the messages you sent, the commits you pushed, the places you checked in, the things you finished. Each entry is not only an account of what happened that day. It is an account with its origins still attached. The line about a meeting traces back to a calendar event with a date and a set of names. The line about a long afternoon of work traces back to commits with their own timestamps. None of it depends on you correctly recalling, a year later, whether something was witnessed or imagined, said or only intended, your own idea or someone else’s.
You will still make source monitoring errors. The framework Johnson, Hashtroudi, and Lindsay described is not a habit you can drill away. It is simply what attribution looks like when origin was never stored in the first place. What an outside record gives you is a second account, one where the origin was stored, that the reconstructed memory can be checked against.
