The Decision Log — building your own evidence.

Why journaling decisions through your Authority beats consuming more content.

9 min readFree lesson

The temptation, after enough study, is more study.

After a certain point in any framework's study, the temptation is always more content. Another book. Another teacher. Another deeper-than-the-last article. The mind enjoys the process; the body, in this framework, learns nothing further from it.

The opposite move is the higher-leverage one. Stop consuming and start observing your own decisions.

Reading about your authority does not change much. Watching your decisions over time, sorted by whether you honored your authority or overrode it, changes everything. PRISM's Decision Log is the tool for the second practice. This chapter explains why it is the single most useful thing you can do with the framework once Foundations is behind you.

Your own evidence.

Trust in the framework deepens through one mechanism only: you watching, in your own life, decisions made through your authority producing better outcomes than decisions made by mental override. You do not need a teacher to confirm this. You need to see it yourself.

The fastest way to see it is to write it down at the moment of decision — not later, when memory has reorganized the story. Capture the field. Capture the response. Capture what you decided. Capture what happened. Read back across six months, twelve months, three years. The pattern, once it is laid out in front of you in your own handwriting or your own typing, is hard to argue with. The framework's claim about your authority gets demonstrated by your own life rather than asserted by anyone else.

This is also the practice that ends the dependency on teachers. Once your evidence is built, you stop needing the next book to validate what you already know about yourself. You have your own record, and the record is more persuasive than any external authority on the framework could be.

The format.

A useful decision log captures three moments per material decision.

Pre-decision. What is the question? What is the context? How did your authority respond? How strong was the signal — was it a clear yes, a tentative leaning, a body silent on the question? Capture this before you commit, in the moment of considering. The field of the moment is what you are documenting, and the field cannot be reconstructed from memory once it has passed.

At decision. What did you actually decide? Yes, no, or deferred? And, honestly: were you in alignment with what your authority told you, or did you override it for some other reason — social pressure, urgency, mental case-building?

Post-decision. What happened? How satisfied are you, on a one-to-five scale? Did you land in your type's signature — peace, satisfaction, success, surprise — or in the shadow — anger, frustration, bitterness, disappointment? The post-decision field can be filled in later, days or weeks after the decision has played out.

The pre-decision capture is the most important. The other two stages will fill themselves in over time. But if you skip the pre-decision capture, the log loses most of its value — you cannot tell, six months later, whether you honored your authority in the moment, because you no longer remember what your authority was actually saying.

The retroactive chart context.

Every PRISM decision log entry automatically captures more than your prose. The full chart context at the moment of capture is preserved with the entry: your type, authority, and profile (frozen, in case you later recompute against different birth inputs); the day's most-relevant transits; the gates that were ringing across your chart and the sky simultaneously.

Read an entry six weeks later, and you do not just see what you decided. You see the field you decided in. You see that you decided yes on a high-water emotional day, two months before you walked it back. You see that your sacral gut said no, you overrode it, and the outcome confirmed the gut. You see that the splenic whisper arrived clearly and the mind built a contrary case in three steps that, in retrospect, look exactly like the mental case-building you have been doing for years.

The pattern emerges from rereading. The framework is no longer abstract; it is your own story, indexed.

What to log, and what to skip.

Do not log every coffee order. The log is for material decisions — ones whose outcome will matter to you in three months. The bar varies by person. For some, it is commitments over a few hundred dollars. For others, it is any decision involving another person beyond family. For others, it is decisions that take more than ten minutes of consideration.

A useful starting cadence: any decision you are uncertain about, that you would have asked a friend about, gets logged. Two or three entries per week is plenty. The pattern emerges within ninety days.

If you are over-logging, you will know. The practice will start to feel like documentation rather than observation, and the entries will be shallow. Reduce the volume; increase the depth of the entries that remain.

The ninety-day review.

After ninety days, sit down and read every entry in order. Notice:

Where you honored your authority, and how those outcomes felt — signature or shadow.

Where you overrode your authority, and how those outcomes felt — almost always shadow.

Recurring patterns. Same situation, same override, same disappointing result. The framework's most useful claim is that this pattern is structural, not personal failure; the log will show you whether the pattern is, in fact, structural.

Authority signal strength. Did stronger signals correlate with better outcomes? They should. If they did not in your data, the override was happening even when the signal was clear, and the work to do is on the override habit rather than on the signal sensitivity.

What field-conditions produced your worst overrides? Likely high-emotional-wave days for emotional authorities, social-pressure moments for sacral, mental urgency for splenic. Once you know your own pattern, you can build the conditions in which override is least likely.

The review is the practice. Reading the entries back is when the framework stops being a teaching and becomes your evidence. From there, the dependency on outside teachers tapers gracefully. You have your own record. Your own record is enough.