SEGGY SAID · A SYSTEM

The
Wonder
Prompt System

Three steps to move from typing at AI like a search engine
to running it like a mirror that sharpens how you think.

↓ Begin

WELCOME TO THE SYSTEM

If you're reading this, you didn't buy a bunch of random word docs.
You bought a mirror.

Let's be honest — we are living in a weird time. Everyone is freaking out about AI taking over, or they're using it to write soulless emails and cheat on their homework. They are either scared of the machine, or lazy with it.

I don't believe in either of those paths.

I believe AI is the most powerful tool ever invented for self-reflection. Used correctly, it doesn't replace your humanity — it highlights it. It forces you to ask better questions. It shows you back to yourself with a clarity you can't get from your own head.

But here's the disclaimer before we start: garbage in, garbage out. If you treat it like a search engine, you get search engine answers. If you treat it like a mirror, you get a mirror. This system is built to teach you the second thing.

I designed it to move you from being a user — someone who types aimlessly — to a thinker, someone who uses the machine to upgrade their own mind without giving it away.

Three steps. Each one stacks on the last.

THE PREMISE
This is not a productivity hack.
It's an audit of the operating system you never consciously chose — and a structured way to rewrite it.
§
A WORD BEFORE WE START

The future is splitting into three camps.

I've been watching this coming for a year now. The people you know — your coworkers, your siblings, your neighbors — are quietly landing in one of three groups. Most of them don't know it yet. You need to know which one you're picking, because the choice is being made whether you make it or not.

01
The Outsourcers
Hand their agency to AI and slowly forget how to think. Their output goes up. Their capacity goes down. By year three they can't write a paragraph without asking the machine first.
02
The Ostriches
Refuse to engage with what's happening and get left behind. They'll tell you they're "too old for this." What they mean is they're scared. The fear is valid. The posture is not.
03 · THIS ONE
The Architects
Use AI to increase self-awareness and capability — without letting it replace identity, judgment, or responsibility. They get sharper as the machine gets smarter. That's the deal.
This system is built for the third camp.
Stay human. Use the machine. Become more yourself, not less.
§
STEP ONE · THE INITIATION
From user
to thinker.

Six operating skills I use every day so AI doesn't give me surface-level, recycled, agreeable garbage. This is the layer underneath everything else.

If Step 2 is how AI gets to know you,
and Step 3 is how you change your life,
this is how you operate.

Most people leave the magic on the table. They type at AI the same way they type at Google. A few small shifts in how you approach the machine and you stop getting "broadly reasonable" answers and start getting ones that actually move you.

You don't need to memorize any of this. Save the prompts somewhere you'll find them. The habits — voice mode, interview flipping, cross-checking — become automatic after a week.

01
Voice Unlock
WHY TYPING KEEPS YOU STUCK

Typing lies. Not intentionally. Structurally.

When you type, you clean things up. You shorten. You skip the messy, contradictory parts. You remove emotion, hesitation, tone, and pacing. All the layered nuance in your head gets flattened into something that looks like clarity but is actually performance.

When you talk, you contradict yourself. You pause mid-sentence. You take things back. Your uncertainty shows. And that mess is the signal — it's the truth of how you actually think.

The first real breakthrough I ever had with AI happened the moment I stopped typing and just talked. Your thoughts move faster than your hands, so when you type you're unintentionally shortening everything. Voice captures what your hands miss.

How to use it

  • Turn on voice dictation — the little microphone icon on your keyboard
  • Not the voice-chat mode where you talk back and forth. Just dictate.
  • Talk for 2–5 minutes without stopping
  • Don't aim for clarity. Aim for honesty.
  • Let contradictions happen. Talk like you're talking to your best friend.
If you only adopt one thing from this entire system, make it this.
Use your voice. Stop typing. Everything else builds on it.
§
02
Research Mode
HOW TO FORCE AI OUT OF "SAFE ANSWER" MODE

Most people don't realize this: AI defaults to the most statistically safe response. Not the deepest. Not the most current. Not the most useful. The most probable. It's a probability machine.

Ask "what's the best marketing strategy for TikTok?" and you'll get a clean, reasonable, generic answer that sounds right and helps almost nobody. Research Mode is how you force AI to stop summarizing the internet and start interrogating it.

You're telling it: where to look, what time frame matters, what disagreements exist, what incentives might be distorting the truth, and what to ignore.

Research Mode — Current

Use when you want what's happening now, not recycled advice.

research-mode-current.txt
I want you to enter research mode. Scan articles, expert commentary, and credible discussions from the last 30 days only. Ignore anything older unless it is foundational. Topic: [PASTE TOPIC] Your job: • Identify what is happening right now • Surface emerging disagreements or debates (minimum 10 sources) • Highlight what most people are still repeating that may be outdated • Separate proven patterns from speculation Then tell me: 1. What's actually working right now 2. What people think is working but isn't 3. What most summaries are missing 4. What additional steps I should be thinking about

Research Mode — Incentive Scan

Use when something sounds convincing but feels off.

research-mode-incentive.txt
Research this topic with incentive awareness. Scan for the most recent updates (last 30 days) but go back farther if needed. I want depth over speed. Topic: [PASTE CLAIM OR IDEA] While researching, pay special attention to: • Who benefits if this idea spreads • Who loses if it's challenged • Whether advice is tied to a product, course, or ideology Return: • The strongest arguments FOR • The strongest arguments AGAINST • Where incentives may be shaping the narrative

Research Mode — Contrarian Signal

Use when everyone seems to agree.

research-mode-contrarian.txt
Assume the popular consensus on this topic is incomplete. Topic: [PASTE TOPIC] Your task: • Find credible dissenting perspectives • Identify edge cases where the advice breaks down • Explain where certainty is being overstated
§
03
Flip the Interview
ADVICE WITHOUT CONTEXT IS USELESS

Most people ask AI for solutions before AI understands the problem. That guarantees generic advice.

When I'm stuck — emotionally, creatively, professionally — I don't ask "what should I do?" I say: interview me first. Ask as many questions as you need. One at a time. Let me answer, take that in, then ask the next one. Keep going until you fully understand.

Then I give the real question. And I answer each follow-up in voice mode. Out loud. With complete honesty. Sometimes uncomfortably.

Why this works

  • You often don't know what context matters
  • AI is better at extracting structure than guessing intent
  • Clarity emerges while you're answering, not after

Flip the Interview

flip-the-interview.txt
Before giving advice, interview me. Ask only the questions you actually need to understand my situation. Ask one question at a time. Let me answer. Take that in. Then ask the next. Look for: • My constraints • My goals • What I've already tried • What feels unclear or stuck Keep going until you feel you fully understand what I need. Then — and only then — give me your response. Here's what I want help with: [YOUR SITUATION]
Context first. Conclusions second.
§
04
Reality Check
HOW TO TELL IF SOMETHING IS BULLSHIT, CONFIDENTLY

AI can sound convincing while being wrong. So can you. Especially so can the internet.

Reality Check Mode turns AI into a skeptical investigator. This is the exact prompt I use when something sounds right and I want to know if it actually holds up.

Reality Check Prompt

reality-check.txt
I want you to investigate the following claim with maximum rigor. Nothing gets by you. Claim: [PASTE CLAIM] Your role: a skeptical investigative researcher. Rules: • Do not reassure me • Do not summarize popular opinion • Do not optimize for balance • Optimize for truth under uncertainty Process: 1. Trace the origin of the claim. Scan 20+ sources if needed. — Who first introduced it? — Was it research, anecdote, marketing, or speculation? 2. Cross-check independent sources. — Are sources genuinely independent or echoing each other? 3. Analyze incentives. — Who benefits if this claim is believed? — Who might be harmed if it's challenged? 4. Identify strongest counterarguments. — Not strawmen. The best opposing cases. 5. Check recency and relevance. — Has new data emerged that weakens or strengthens it? Output: • What's solid • What's overstated • What's missing • What would need to be true for this claim to hold Finally: assign a credibility score from 0–100 and explain why.
§
05
External Compression
BORROWING FRAMEWORKS INSTEAD OF GUESSING

YouTube, podcasts, and long-form content are incredible. You can learn anything you want nowadays. Any topic, any depth — there is an expert on YouTube telling you exactly how to do it.

But most people either skim and lose the insight, or spend hours taking notes they never use. I do something different. I compress expertise.

The tool I use is Glasp — it pulls transcripts, highlights, and notes from YouTube videos and articles. If you want to actually learn, watch the video. I still do. But when I want to execute on what someone's teaching, I let AI help.

How I actually use it

  • Pull transcripts from 3–5 people I trust on a topic
  • Paste them into AI: "Do not respond yet. Just absorb this material and learn how these people think."
  • Turn on voice mode and explain what I'm trying to build — constraints, style, audience, what I dislike
  • Then ask: "Based on these frameworks and my situation, design an approach that fits me."

This works for business, marketing, writing, health, strategy, life decisions. Find Glasp at glasp.co.

§
06
Model Cross-Checking
WHY MULTIPLE AIS REVEAL DEEPER TRUTH

No single AI sees the full picture. Just like no single human does.

Different models are trained differently. They notice different things. They emphasize different risks. When something matters, I never trust one answer.

How I use this

  • Draft in one model — usually ChatGPT or Claude
  • Drop the output into another — Gemini, or the other of those two
  • Ask: "What feels weak, missing, or overstated here? What would you challenge?"

Where models disagree is usually where the gold is. There have been times I was certain I was done, dropped it into another model, and got a completely new perspective that made the whole thing better. Use at least two for anything that matters.

One model is a draft. Two is a conversation.
Three is a team.
§

You don't have to memorize any of this.

Save these prompts somewhere you can find them. A lot of the skills — voice mode, interview flipping, cross-checking — will start happening naturally once you've done them a few times. The others, keep on hand for when you need them.

Master these and watch how much more useful your AI tools become. This is the foundation. Step 2 is where the real personalization starts.

STEP TWO · THE INNER PROFILE
Teach the mirror
who you are.

A one-time setup. Under an hour. What comes out the other end is an AI that stops treating you like an average human and starts reasoning inside your actual patterns.

WHY THIS MATTERS

AI doesn't meet you. It meets probabilities.

When you ask a question without context, AI defaults to the most common life path, the safest interpretation, the average emotional range, the "broadly reasonable" advice. That advice isn't wrong. It just isn't for you.

That's why AI often sounds insightful but doesn't actually move the needle. It feels supportive but vague. It repeats things you already know. It misses the real tension underneath your questions.

The problem isn't intelligence. The problem is identity resolution. AI can't personalize without a model of how you actually operate. That's what you're building here.

WHAT WE'RE DOING
This is not journaling. This is not therapy.
It's a behavioral operating model — extracted from your own voice, stored once, reused forever.
How memory actually works
READ ONCE · NEVER NEED IT AGAIN

Most people misuse AI memory. Understanding this one page puts you in the top 1%.

Project Memory

Short-term, powerful. What AI remembers inside one specific chat or thread. Highly contextual. Feels personal. The catch: it can fade or reset if the thread gets too long. This is your daily workspace.

Platform Memory

Selective, fragile. Some platforms store summaries about you in the background. It's compressed, inconsistent, and the system edits it without asking you. The catch: useful but not reliable. Never trust it with the important stuff.

User-Controlled Memory

The only stable anchor. Memory you own — a Google Doc, Notion, a text file, a note app. The rule: AI should reference your identity. It should never own it.

Own the source document. Let AI borrow from it.
Never let it be the keeper.
§
The Build
SEVEN STEPS · ONE HOUR · DONE FOREVER

Step 1 — Create the space

Open a new project in your AI tool. Name it something distinct — Inner Profile, Operating System, Thinking Partner, Yoda. This is your long-term space. You'll come back to it for years.

Step 2 — Set the mode before you start

Voice dictation is non-negotiable. Typed answers are curated. Spoken answers are revealing. Voice bypasses your self-image management and captures how you think, not just what you say. Dictate your answers into the text box like a normal message. Don't re-record. Ramble if needed. Think: recorded interview, not a casual chat.

Step 3 — Paste the Interviewer Prompt

This runs the interview. The questions aren't random — they're built from depth psychology and shadow work to target the patterns that actually run your life. Don't edit them. Trust the sequence.

prompt-A-interviewer.txt
I am ready to build my Inner Profile. I want you to act as a clinical interviewer whose job is to understand my psychological and behavioral operating system based on my answers alone. Your role is not to comfort me. Your role is to extract accurate signal. THE RULES: • Ask the questions below ONE AT A TIME. • After each answer, acknowledge briefly, then immediately ask the next question. • Do NOT summarize, interpret, or coach me yet. • If my answer is vague, rehearsed, or sounds like self-image management, push back and ask a follow-up until you get something concrete. • I will be answering using VOICE DICTATION. Do not interrupt. Let me finish speaking. THE QUESTIONS: 1. THE ORIGIN Describe the emotional atmosphere of your home around age 7. What parts of yourself did you learn to hide, mute, or exaggerate to stay safe or accepted? 2. THE LOOP What is the one problem you keep encountering in different forms? What hidden benefit do you get from staying in it? 3. THE SHADOW Who is the person or type of person that irritates you the most? What traits in them do you secretly recognize in yourself? 4. THE STRESS RESPONSE When overwhelmed, which pattern dominates: Fight, Flight, or Fawn? What is the internal script running in your head? 5. THE VALUE TEST If money, status, and recognition disappeared, what would you still feel compelled to do? 6. THE FUTURE SELF Ten years from now, if your life worked honestly, what three traits describe how you show up? 7. THE UNFINISHED SENTENCE If you died today, what truth would hurt most to leave unlived or unsaid? 8. THE OPEN MIC Is there anything else — a specific fear, a recurring dream, a frustration, or a detail about your history — that you haven't mentioned but feels essential for this profile to understand? Begin now. Ask Question 1.

The eight questions

Here's what the prompt will walk you through. Read them once before you run the interview, so your voice can start warming up to them.

QUESTION 01 · THE ORIGIN
What was the emotional weather of your home at seven — and which parts of yourself did you learn to hide to stay safe in it?
QUESTION 02 · THE LOOP
What's the one problem that keeps showing up in different costumes — and what are you getting out of staying in it?
QUESTION 03 · THE SHADOW
Who is the person or type who irritates you most — and which of those traits do you secretly recognize in yourself?
QUESTION 04 · THE STRESS RESPONSE
Under pressure, do you fight, flee, or fawn — and what's the script running in your head when it happens?
QUESTION 05 · THE VALUE TEST
If money, status, and recognition disappeared, what would you still feel compelled to do?
QUESTION 06 · THE FUTURE SELF
Ten years from now, if your life worked honestly — not impressively, honestly — what three traits describe how you show up?
QUESTION 07 · THE UNFINISHED SENTENCE
If you died today, what truth would hurt most to leave unlived, or unsaid?
QUESTION 08 · THE OPEN MIC
What else — a fear, a recurring dream, a frustration, a detail of your history — hasn't been named but feels essential for this profile to see?
The golden rule:
Do not perform. Do not answer as the healed version of yourself or the version you wish were true. Be who you are right now. Messy answers are better truth. Contradictions are gold.
Lock the data
STEPS 4 THROUGH 7 · THE FREEZE · THE ARCHITECTURE · THE ANCHOR

Step 4 — The Freeze

Once the interview is done, you need to lock the raw data before AI tries to "fix" it or smooth it into something prettier than the truth. Paste this next:

prompt-A2-freeze.txt
Do not interpret. Do not summarize. Do not improve language. Output a structured record in this format: • Question • Raw Transcript (verbatim, unedited) This is the canonical record. This prevents distortion.

Step 5 — The Architecture

Now we turn the raw data into a usable system. This is where AI moves from scribe to architect — reading the transcript and surfacing the pattern underneath your answers.

prompt-B-architect.txt
Now act as a systems architect analyzing my responses. TASK 1 — CONSTRUCT THE INNER PROFILE Create a section titled "THE INNER PROFILE" containing ONLY: CORE WOUND The primary insecurity driving my behavior. SHADOW PATTERN How I self-sabotage when things begin to stabilize. DEFAULT LOOP Trigger → Reaction → Result STRESS MODE How I behave under pressure and what I am protecting. FUTURE TRAITS The three traits that should guide decisions. AGENCY RULE A rule you must follow when giving me advice. Be precise. No motivational language. TASK 2 — MEMORY HANDOFF Acknowledge this as active context for this project.

Step 6 — The Anchor

Non-negotiable. Save both the Raw Transcript and the Inner Profile to a document outside of AI — Google Docs, Apple Notes, Notion, anywhere you own. This is your reset button. If AI ever loses the thread or hallucinates, you have the source code.

Step 7 — Daily Use

Stay inside your Inner Profile project for the big stuff. Ask questions normally. Let the context build. If the context ever feels lost, just start a new project, paste your saved Inner Profile, and say: "Use this as authoritative context for this project." That's it. No rituals. No constant re-pasting.

§

Clearer, not nicer.

This is not therapy. This is not healing. This is not comfort.

This is a mirror that doesn't forget. A pattern detector that doesn't get tired. A consistency engine between who you say you are and how you actually act.

Once it's installed, every conversation gets sharper. You're no longer asking AI for advice — you're asking it to reason inside your unique patterns. Trust me, this makes all the difference.

RITE OF COMPLETION · STEP TWO
You just taught the mirror who you are.
Nothing you do with AI from here forward looks the same.
STEP THREE · THE UPGRADE
A thirty-day
operating reset.

Three phases. Ten days each. Each one ends with a completion you can feel. You are not trying to fix yourself. You're updating how you process, decide, regulate, and follow through — so your effort stops leaking out of invisible gaps.

You can't out-hustle a bad system.

Most people try to change their lives by stacking hacks — a new app, a new routine, a new morning miracle, a new identity label. That's like trying to run heavy software on old hardware and blaming the laptop when it freezes.

The Upgrade isn't about fixing you. There is nothing to fix. It's about updating how you process, decide, regulate, and follow through so your effort stops leaking out of invisible gaps.

Fifteen minutes a day. One day at a time. If you miss a day, pick up where you left off — don't restart. The sequence still works even with gaps.

THE THREE PHASES
Audit · see the current system clearly.
Architect · design one that fits your real life.
Deployment · prove it under pressure.
PHASE ONE OF THREE

The Audit

DAYS ONE THROUGH TEN

Clarity without self-attack. Before you change anything, you identify what's actually happening. You're not improving yourself here — you're collecting clean information about you.

SETUP · DO THIS ONCE BEFORE DAY 1

Open a new AI chat or project. Name it: "CAP — Days 1–10 (Audit)". Only use this chat for days 1 through 10. This is your container for the whole audit.

Create a note somewhere outside the AI — Apple Notes, Google Docs, Notion — titled "CAP Scoreboard". You'll log one short entry per day there. Don't log inside the AI chat.

Then paste the master context prompt below into your new project. This tells the AI how to behave for the whole phase.

phase-1-master-context.txt · paste once
Cognitive Architecture Protocol — Phase 1 (Audit) — Master Setup You are my Behavior Change Coach using evidence-based methods. Context: This chat contains Days 1–10 of Phase 1: The Audit. Your job is to help me collect accurate data about how I currently operate. Global Rules (apply every day): • Ask questions before analyzing. • Use plain English. No therapy language. No motivational speeches. • Keep responses short and actionable. • Every day, end your response with two clearly labeled blocks: — CAP SCOREBOARD ENTRY (copy-paste ready) — PHASE ARTIFACT (copy-paste ready) • Do not add assumptions beyond what I tell you. Scoreboard: I log my score outside this chat in a separate note. Begin when I paste Day 1.

Most people think they're stuck because of something big — the wrong job, the wrong relationship, not enough discipline. In reality, most people stay stuck because of small repeated energy leaks they never see clearly.

Today is not about fixing your life. Today is about proving one thing: your life is not one giant unsolvable problem. It's made up of specific moments you can learn to handle differently. Patch one leak, recover energy. Energy is what you need to create change.

Think about yesterday. Not your life. Not a pattern. Not a personality trait. One specific moment that drained you.

  • A conversation that went on too long
  • Saying yes when you meant no
  • A task you overworked
  • A distraction spiral
  • A situation that felt heavier than it should have

Pick one. Then paste the prompt below.

day-01-leak.txt
Cognitive Architecture Protocol — Day 1 You are my Behavior Change Coach using evidence-based methods. Your job is to help me identify one energy leak from yesterday and give me a fix I can actually use today. First, ask me exactly 6 simple questions, one at a time, to fully understand the situation. After I answer all 6, complete the analysis below. Here is the situation: [DESCRIBE ONE SPECIFIC MOMENT THAT DRAINED YOU YESTERDAY] After the questions: A) Classify this leak into ONE category: - Time Trap - People Drain - Perfection Loop - Avoidance Loop - Self-Betrayal B) Explain in plain English what this leak is really protecting me from (guilt, conflict, discomfort, judgment, fear of disappointing someone). C) Give me a Patch Menu with 7 options: - 2 very easy options - 2 time or rule-based options - 2 exact scripts I could say - 1 firm boundary option D) Tell me which option is the best first patch for me and why. E) Give me one small action I can take today (under 2 minutes) to prove momentum. Then generate: • CAP SCOREBOARD ENTRY (copy-paste ready) • PHASE ARTIFACT (copy-paste ready) with: leak category, real driver, best first patch, one sentence I want to remember. Keep it practical. No motivational talk.

Pick one patch from the menu — doable, slightly uncomfortable, realistic today. Do the proof action once. Then write one sentence in your notes: "I patched ___ by doing ___ and the result was ___." That sentence is your proof.

Paste the Scoreboard Entry into your Scoreboard note. Paste the Phase Artifact into your notes under Day 1. You'll use it on Day 10.

If you finished today and thought "that was smaller than I expected, but I feel a little more in control" — that means it worked. Tomorrow we look at why certain habits formed in the first place, without blame, without excuses, so change stops feeling like a fight.

Every habit you have — even the ones costing you — started as a solution. It was working for something, at some point, even if it stopped working years ago. You didn't pick up these patterns because you're broken. You picked them up because they protected you. Once you see that, change gets a lot less adversarial.

Pick one habit that costs you today. Scrolling at night. Overworking. Avoiding a conversation. Picking fights. Something specific, not a theme.

day-02-origin.txt
Cognitive Architecture Protocol — Day 2 Your job today: help me see why one current habit ever made sense — so I can stop fighting it and start redesigning it. Ask me 5 questions, one at a time, to understand: • When this habit first showed up • What pressure or need it was responding to • What it was solving for back then • What it's costing me now • What I've tried instead that hasn't worked Here's the habit: [ONE SPECIFIC HABIT THAT'S COSTING YOU] After my answers, give me: A) THE ORIGIN STORY — in plain English, what this habit was originally designed to solve B) THE UPDATE NEEDED — what the habit can be replaced with now that my life is different C) THE MICRO-SWAP — one small behavioral swap I can try once today (not a full replacement) D) WHY I'LL RESIST THIS — the specific discomfort that will come up when I try the swap Then: • CAP SCOREBOARD ENTRY • PHASE ARTIFACT (origin, update, micro-swap, resistance) No motivational framing. Operational only.

Read the origin story slowly. Try the micro-swap once today — that's it. Log your score. Save the artifact.

If you "want" to change something and haven't, there's a trade happening you haven't named yet. Staying the same is giving you something. Usually: safety from judgment, from failure, from being seen wanting something and not getting it. Naming the trade doesn't mean you have to take it. It just means you can make the choice consciously instead of drifting.

Name one thing you say you want but haven't acted on. Be specific. A promotion. A project. A relationship change. A body change. Something that has been sitting on your list for months or years.

day-03-tradeoff.txt
Cognitive Architecture Protocol — Day 3 Your job: help me see what I'm getting from not changing — so I can decide if the trade is still worth it. Ask me 5 questions, one at a time: • What specifically I want • How long I've "wanted" it • What I've done and not done about it • What would become uncomfortable if I actually had it • Who in my life would be affected if I pursued it Here's what I want: [THE THING YOU SAY YOU WANT] After my answers, give me: A) THE HIDDEN TRADE — the specific thing I'm getting by staying the same. Not vague. Specific. "Safety from ___" or "Permission to ___." B) THE PRICE OF THE TRADE — what I lose every month by continuing the trade. C) THE DISRUPTION (not the full change) — one tiny action this week that breaks the trade without committing me to the full change. The smallest possible disruption. D) WHAT I'LL TELL MYSELF to avoid doing it. Then: • CAP SCOREBOARD ENTRY • PHASE ARTIFACT (want, trade, disruption, escape story) Be direct. Do not inflate or soften.

Read the tradeoff sentence slowly. Choose the disruption — not the full change. Do it today.

You have a story running about who you are. "I'm not good with money." "I'm not the creative one." "I'm just not disciplined." These stories feel like facts. They're not. They're interpretations you picked up somewhere along the way, and your life has been quietly organizing itself around them.

Pick one limiting story you tell about yourself. Test: does the sentence start with "I'm not" or "I always" or "I can't"? Those are stories. Grab one.

day-04-story.txt
Cognitive Architecture Protocol — Day 4 Your job: help me see one limiting story about myself and construct a more accurate one — without toxic positivity. Ask me 5 questions, one at a time: • What the story is, in my exact words • When I first remember believing it • What evidence I use to keep believing it • What counter-evidence I've been ignoring • What this story protects me from attempting Here's the story: ["I'M NOT ___" OR "I ALWAYS ___" OR "I CAN'T ___"] After my answers, give me: A) THE OLD STORY — restated precisely, with what it costs. B) THE COUNTER-EVIDENCE — the specific moments I've dismissed that contradict it. C) THE MORE ACCURATE STORY — not the opposite, not affirmation. The accurate one. Usually something like: "I've been ___ in specific conditions. Under different conditions, I've been ___." D) THE ONE BEHAVIOR that would only make sense if the new story were true. Then: • CAP SCOREBOARD ENTRY • PHASE ARTIFACT (old story, counter-evidence, new story, behavior) No hype. Accuracy over inspiration.

Compare the old story and the new one out loud. Which one has more evidence? Do the behavior today.

The sentences you say to yourself in your own head are doing work. Not metaphorical work. Behavioral work. They're either organizing you toward what matters or quietly dismantling you. You've been listening to this voice for so long you've stopped hearing it.

Identify one sentence you say to yourself often. "I'll never figure this out." "I should've done that by now." "Who am I to want this?" Grab the exact wording.

day-05-language.txt
Cognitive Architecture Protocol — Day 5 Your job: help me replace one self-sentence I've been repeating with one that's more accurate and more useful. Ask me 5 questions, one at a time: • The exact sentence I say • The situations that trigger it • What I feel physically when I say it • What I do differently right after I say it • Whose voice it sounds like, if anyone's Here's the sentence: [EXACT WORDING OF THE SENTENCE YOU SAY IN YOUR HEAD] After my answers, give me: A) WHAT THIS SENTENCE IS DOING — the specific behavioral job it's performing (avoiding action, deflecting responsibility, pre-empting judgment, etc.) B) A REPLACEMENT SENTENCE — not positive affirmation. A sentence that is true AND moves me toward action. It should feel slightly uncomfortable to say. C) THE WINDOW — the specific trigger moment when I should say the new sentence instead. Then: • CAP SCOREBOARD ENTRY • PHASE ARTIFACT (old sentence, job, new sentence, trigger) Specific over poetic.

Say the new sentence out loud three times today in the trigger window. It's going to feel foreign. That's correct.

Your body has been signaling things your mind hasn't caught up to yet. The tension in your shoulders when you open a certain inbox. The pit in your stomach on Sunday nights. The tightness when your spouse mentions a topic. These aren't random — they're data.

Notice one physical signal you've been dismissing. Something recent or chronic. Where in your body. What situations bring it up. How strong.

day-06-body.txt
Cognitive Architecture Protocol — Day 6 Your job: help me translate one physical signal into usable behavioral information. Note: you are not diagnosing. You are helping me read a signal. Ask me 5 questions, one at a time: • Where in my body the signal shows up • When it started (recent, chronic, unclear) • What situations reliably trigger it • What I usually do when it shows up • Whether I've been treating it as "just stress" or a sign Here's the signal: [DESCRIBE THE PHYSICAL SIGNAL] After my answers, give me: A) THE LIKELY TRANSLATION — in plain language, what the signal is pointing at (not medical, behavioral). B) ONE REGULATION ACTION — something concrete I can do today when the signal rises (breath, movement, pause, leave the room, etc.) C) ONE INVESTIGATION QUESTION — a specific question I should ask myself the next time the signal shows up, to gather more data. Then: • CAP SCOREBOARD ENTRY • PHASE ARTIFACT (signal, translation, regulation, investigation question) Treat it like data, not drama.

Use the regulation action once today. Ask the investigation question when the signal next shows up. Log it.

There are rules running your life that you never consented to. "I should be further along by now." "I should want what they want." "I should feel grateful." Every should is a borrowed rule from a family, a culture, an era, a teacher. Today we find one and check whether it's still yours.

Name one "should" that pressures you regularly. The more embarrassing or shame-adjacent it feels, the better the one to pick.

day-07-should.txt
Cognitive Architecture Protocol — Day 7 Your job: help me find the origin of one "should" rule I'm still obeying — and decide if it's actually mine. Ask me 5 questions, one at a time: • The exact "should" sentence • Who I first heard it from (a person, a culture, a profession, a parent) • What I think happens if I violate it • What's actually happened when I partially violated it • Whether I would give this rule to someone I love Here's the should: [PASTE YOUR "SHOULD" SENTENCE] After my answers, give me: A) THE ORIGIN — where this rule most likely came from and why it existed in that context. B) THE UPDATE — what a version of this rule looks like that is actually mine, not borrowed. C) THE EXPERIMENT — one small, low-risk violation of the old rule I could do this week to test whether the consequence I fear is real. Then: • CAP SCOREBOARD ENTRY • PHASE ARTIFACT (old rule, origin, new rule, experiment) Keep it grounded. No rebellion-for-its-own-sake talk.

Compare the old rule and the new one. Run the experiment this week.

You think you're running on discipline. You're mostly running on environment. What's within arm's reach, what's on your phone's home screen, who you live with, what time you wake up — these do more work than willpower ever will. A bad environment can beat a strong will. A good environment makes an average will look like discipline.

Pick one area where your behavior isn't matching your intention — food, focus, phone, sleep, spending, relationships. Today we look at the environment around it.

day-08-environment.txt
Cognitive Architecture Protocol — Day 8 Your job: help me identify the environmental factors shaping one behavior — and suggest one specific change I can make tonight. Ask me 6 questions, one at a time: • The behavior I want to shift • What's in my physical environment that enables the old behavior • What's in my digital environment that enables it • Who, socially, is involved in the old pattern • What time of day it typically happens • What's missing from the environment that would make the new behavior easier Here's the behavior: [THE BEHAVIOR NOT MATCHING YOUR INTENTION] After my answers, give me: A) THE FRICTION AUDIT — where friction is currently lowest for the old behavior and where it's highest for the new one. B) ONE ENVIRONMENTAL CHANGE I can make tonight that tips the friction. C) ONE SOCIAL CUE to add or remove that shifts the pattern. Then: • CAP SCOREBOARD ENTRY • PHASE ARTIFACT (behavior, friction map, environmental change, social cue) Structural not motivational.

Make the environmental change tonight. Not tomorrow. Tonight.

Distraction is not a failure of focus. It's a successful escape from something. The phone, the snack, the "quick check-in," the new project that takes you off the real project — all of it is doing a job. Today we name the job.

Pick your favorite distraction pattern. The one you default to when something feels heavy. Scrolling, snacking, Netflix, news, busy-work.

day-09-distraction.txt
Cognitive Architecture Protocol — Day 9 Your job: help me see what my distractions are actually running from — so I stop treating distraction as a discipline problem. Ask me 5 questions, one at a time: • My preferred distraction pattern • What task or feeling usually precedes it • What it gives me in the moment (relief from what) • What it costs me after • What I'd have to feel if I didn't use it Here's the distraction: [YOUR DEFAULT DISTRACTION] After my answers, give me: A) THE ESCAPE MAP — what the distraction is reliably running from. B) THE REAL DISCOMFORT — the underlying feeling I'm unwilling to sit with. C) THE FIVE-MINUTE PROTOCOL — when the urge rises, what I can do for five minutes that isn't the distraction, so I can meet the real discomfort briefly. Then: • CAP SCOREBOARD ENTRY • PHASE ARTIFACT (distraction, escape, real discomfort, 5-min protocol) Direct, no shaming.

Run the five-minute protocol once today when the urge hits. Just once. Log it.

Today is synthesis. You're not collecting more data. You're looking at the data you already gathered over nine days and letting AI render your current operating system back to you. This is the map you've been living on without realizing it. You need to see it clearly before you can redesign it in Phase 2.

Gather all nine Phase Artifacts from days 1 through 9. Paste them in order into the prompt below. If you missed a day, skip it — don't fake it.

day-10-baseline.txt
Cognitive Architecture Protocol — Day 10 — Phase 1 Baseline Snapshot I am synthesizing Phase 1. Use ONLY the nine Phase Artifacts I'm about to paste. Do not add assumptions. Here are the artifacts from Days 1–9: [PASTE ALL NINE ARTIFACTS IN ORDER] Your job: produce a single synthesis document titled "PHASE 1 — BASELINE SNAPSHOT" with these exact sections: 1. THE RECURRING DRIVERS The 2–3 patterns that kept showing up across the days, in plain language. 2. WHAT I'M OPTIMIZING FOR (HONESTLY) What my current operating system is actually set up to produce — not what I want it to produce. 3. THE ACTIVE COSTS What I'm consistently paying for this system to keep running. 4. THE HIDDEN ASSETS What I'm actually good at, based on what I reported — things I may not have credited. 5. THE OPEN QUESTIONS The 2–3 things I don't yet have clarity on, that Phase 2 should work with. Write it in neutral, operational language. No motivation, no therapy, no advice. This document becomes the input for Phase 2. Save it.

Save the full Baseline Snapshot in your notes. You'll paste it into the Final System Review at day 30. Then take the rest of today off. The Audit is complete.

RITE OF COMPLETION · PHASE ONE
You finished the Audit.
You now have something most people never produce about themselves in a lifetime — a clean map of your current operating system. Take a day. Maybe two. Don't start Phase 2 until you've actually looked at the map.
§
PHASE TWO OF THREE

The Architect

DAYS ELEVEN THROUGH TWENTY

Design on purpose. You've seen the current system. Now you build a better one — not by stacking hacks, but by deciding what you actually want this thing to optimize for.

SETUP · DO THIS ONCE BEFORE DAY 11

Open a new AI chat. Name it: "CAP — Days 11–20 (Architect)". Do not keep using the Audit chat — it's too long and the context gets messy. Start fresh.

Paste the master context prompt below. Then, at the start of Day 11, you'll paste your Phase 1 Baseline Snapshot as the foundation.

phase-2-master-context.txt · paste once
Cognitive Architecture Protocol — Phase 2 (Architect) — Master Setup You are my Behavior Design Coach using evidence-based methods. Context: This chat contains Days 11–20 of Phase 2: The Architect. Your job is to help me design a better operating system based on the Baseline Snapshot I'll paste shortly. Global Rules (apply every day): • Ask the setup questions for each day before analyzing. • Use plain English. No therapy language. No motivational speeches. • Keep responses short and actionable. • Every day, end your response with two clearly labeled blocks: — CAP SCOREBOARD ENTRY — PHASE ARTIFACT (titled "Day N — [theme]") • Do not invent data. Use only what I give you + the Baseline Snapshot. I log my score in a note outside this chat. Begin when I paste Day 11.

Most people define success using language they got from someone else — a colleague, a podcast, their parents, LinkedIn. But a good day is specific. It fits your actual life, your actual energy, your actual season. Today you design one — realistic, not aspirational.

No 5am miracle mornings unless you already do them. No two-hour deep work blocks if you have toddlers. The goal is a day shape you can repeat.

Open your Phase 1 Baseline Snapshot. You'll paste it into the prompt below. Also think about your actual life right now — responsibilities, time windows, energy patterns, what usually derails you.

day-11-good-day.txt
Cognitive Architecture Protocol — Day 11 Your job: help me design a realistic "Good Day" schedule that fits my actual life, constraints, and energy. Ask me 10 simple questions, one at a time. Wait for each answer. Cover: • My current responsibilities • My available time windows • My energy levels throughout the day • My biggest recurring distractions • My top priorities • What tends to derail me • What I avoid • What I want more of • What I want less of • What a "good day" would feel like at the end Here is my Phase 1 Baseline Snapshot: [PASTE BASELINE SNAPSHOT FROM DAY 10] After my answers, give me: A) MY GOOD DAY — as a realistic timeline (morning / midday / afternoon / evening). Include one focus block, one health block, one connection block, one recovery block. B) THE BIGGEST GAP between my current days and this Good Day. C) MINIMUM VERSION — smallest version I can do on a hard day, under 30 minutes total. D) FIRST UPGRADE — one small change I can try tomorrow. Specific and time-bound. E) ONE IF/THEN RULE to protect the Good Day from my most predictable derailment. Then: • CAP SCOREBOARD ENTRY • PHASE ARTIFACT (good day schedule, biggest gap, minimum version, first upgrade, if/then rule) Plain and practical. No hype.

Pick the Minimum Version or the First Upgrade — not both. Run it once today or tomorrow morning. Write one sentence: "I ran ___ by doing ___ and the result was ___." Save the artifact.

You can't install a belief by force. You can't affirm yourself into trusting something you've never seen proof of. What you can do is find the belief you want, look for real evidence you've been ignoring, and give it a chance to settle.

Today you're not upgrading your whole belief system. You're picking one belief and making it feel honest.

Pick one belief you want to hold but don't fully trust. "I can earn well." "I can be in a loving relationship." "I can actually finish things." Something that would change how you act if it felt true.

day-12-belief.txt
Cognitive Architecture Protocol — Day 12 Your job: help me take one belief I want to trust and make it feel honest based on evidence I already have. Ask me 6 questions, one at a time: • The belief I want to trust • Why I don't fully trust it yet • What my current evidence says (pro and con) • Specific moments in my life that partially support the belief (even small) • What would need to be true about me for the belief to feel honest • What behavior would only make sense if I trusted it Here's the belief: [THE BELIEF YOU WANT TO TRUST] After my answers, give me: A) THE EVIDENCE CASE — the actual supporting moments I've been minimizing. B) A MORE HONEST VERSION of the belief (not affirmation, not downgrade — the version that matches what's true so far). C) ONE BEHAVIOR that only makes sense if I trust the honest version. D) THE PREDICTABLE OBJECTION my mind will raise — and what to do when it does. Then: • CAP SCOREBOARD ENTRY • PHASE ARTIFACT (belief, evidence, honest version, behavior, objection) Accuracy over inspiration.

Say the honest version out loud. Do the behavior once. Notice the objection when it shows up.

Vague fear is paralyzing. Specific fear is workable. When you don't name it, it runs the room. When you do — and look at it directly — it usually turns out to be smaller, more specific, and more survivable than you thought.

Pick one fear that's been stalling you. The one sitting behind a decision you keep postponing.

day-13-fear.txt
Cognitive Architecture Protocol — Day 13 Your job: help me take one vague fear and turn it into something specific, survivable, and workable. Ask me 6 questions, one at a time: • The fear in my own words (not cleaned up) • The worst case I'm actually imagining (concretely) • How likely it is on a 1–10 scale • What I've done in similar situations before • What resources I actually have if it happened • Who I'd tell if it did Here's the fear: [THE FEAR THAT'S STALLING YOU] After my answers, give me: A) THE FEAR IN SPECIFIC LANGUAGE — rewritten from vague dread into a concrete sentence. B) THE REALISTIC WORST CASE — what would actually happen, with honest probability. C) THE RESOURCE MAP — what I already have that would handle it. D) ONE FEAR-INFORMED ACTION — a small step I can take this week that moves me forward even while the fear is still present. Then: • CAP SCOREBOARD ENTRY • PHASE ARTIFACT (specific fear, realistic worst case, resources, action) Honest, not reassuring.

Take the small action. Not the big one — the small one. Prove to yourself the fear is workable.

Sometimes the fastest way to upgrade is to borrow. You know someone — or know of someone — who operates from a belief you don't have. Not because they're better. Because their environment shaped them differently. Today you borrow the belief long enough to see what it would do inside your life.

Identify one person who seems to operate from a belief you wish you had. Specific belief. Specific behavior. Not a celebrity — someone you can actually observe.

day-14-borrow.txt
Cognitive Architecture Protocol — Day 14 Your job: help me identify a borrowed belief that would change how I act — and test-drive it for one week. Ask me 5 questions, one at a time: • Who I'm borrowing from and what I've observed • The specific belief I think they operate from • How they behave differently because of it • Where in my own life I would act differently if I held the same belief • What resistance I already feel to trying it on Here's who I'm studying: [PERSON + SPECIFIC BELIEF YOU'VE OBSERVED] After my answers, give me: A) THE BORROWED BELIEF — restated precisely in a sentence I could speak. B) ONE SITUATION THIS WEEK where I'll test it (specific place, time, conversation). C) WHAT I'LL DO DIFFERENTLY if I act as if it were true. D) THE LIKELY INTERNAL RESISTANCE and how to handle it when it shows up. Then: • CAP SCOREBOARD ENTRY • PHASE ARTIFACT (borrowed belief, test situation, new behavior, resistance plan) No cosplay. Test the belief, not the person.

Try on the belief in the situation you named. See what changes. You're collecting information, not committing.

Your stated values and your actual values aren't always the same. Look at where your time, money, and attention go — that's your real value system speaking. Today you map the gap between what you say and what wins when you're tired.

Pull up a sense of your last two weeks. How'd your time actually go? Not the plan. The real thing.

day-15-values.txt
Cognitive Architecture Protocol — Day 15 Your job: help me see my actual values (revealed by behavior) vs. my stated values — and reduce the gap by one thing. Ask me 6 questions, one at a time: • What I say I value (top 5) • Where my time actually went in the last 14 days • Where my money actually went • Where my attention defaulted to • What I'd be doing if my stated values were running the show • What's currently winning when stated values and default behavior clash After my answers, give me: A) STATED vs. REVEALED — the clearest mismatch. B) THE DRIVER underneath the revealed value (what is it protecting or feeding). C) ONE SMALL REALIGNMENT — a single adjustment this week that pulls behavior back toward a stated value I actually care about. D) THE PREDICTABLE PATTERN that will try to undo the realignment. Then: • CAP SCOREBOARD ENTRY • PHASE ARTIFACT (stated vs. revealed, driver, realignment, predictable pattern) Non-judgmental, structural.

Make the one realignment this week. Small. Real. Notice the pattern that tries to pull you back.

Envy is embarrassing. It's also useful. It points — reliably and specifically — at something you actually want but haven't given yourself permission to name. Today you take one envious feeling and decode it.

Think of someone whose life or work makes you feel a twinge. Not admiration. The sharper thing. You know the one.

day-16-envy.txt
Cognitive Architecture Protocol — Day 16 Your job: help me turn one specific envy into one specific piece of useful direction. Ask me 5 questions, one at a time: • Who the person is and what they have/do • What specifically triggers the feeling (not the whole life — the specific thing) • What it would mean about me to admit I want that • What I think is required to have it (that I don't have) • What I've actually tried so far After my answers, give me: A) THE DECODED WANT — the specific underlying desire the envy is pointing at. B) WHAT IT SAYS ABOUT ME (neutral reading, not a flaw). C) THE FIRST STEP TOWARD IT that doesn't require what I think is required. D) THE TRAP — the way comparison typically stops me from taking that first step. Then: • CAP SCOREBOARD ENTRY • PHASE ARTIFACT (envy source, decoded want, first step, trap) No shame language. Envy is data.

Take the first step. The one that doesn't require what you think it requires.

You have an energy profile. Most people don't know theirs. They know what drains them — they rarely know what restores them reliably. Today you map both sides.

Think about your last two weeks. When did you feel most energized? Most depleted? Be specific about the moments.

day-17-energy.txt
Cognitive Architecture Protocol — Day 17 Your job: help me map what reliably restores my energy and what reliably depletes it — and install one protection rule. Ask me 6 questions, one at a time: • The last 3 times I felt genuinely energized (describe the moment) • The last 3 times I felt drained (describe the moment) • Which people consistently leave me feeling clearer • Which environments consistently settle me • Which tasks I do that I don't notice time passing • What I already know drains me but do anyway After my answers, give me: A) MY ENERGY PROFILE — the reliable givers and reliable takers, specific. B) ONE PROTECTION RULE I can install this week to guard a consistent giver. C) ONE REDUCTION MOVE that lessens exposure to a reliable drainer without blowing up a relationship. D) ONE THING TO STOP SAYING YES TO for the next 14 days. Then: • CAP SCOREBOARD ENTRY • PHASE ARTIFACT (energy profile, protection rule, reduction move, 14-day no) Practical. No martyrdom talk either way.

Install the protection rule this week. Start the 14-day no today.

There are events in your life that you've assigned a meaning to. That meaning feels like the event itself. It isn't. The facts are the facts. The meaning is something your mind authored, often years ago, often under stress. Today you take one event and re-read it.

Pick one past event you still carry. A rejection. A failure. A betrayal. A loss. Something that you've given a meaning to that still shapes how you move.

day-18-meaning.txt
Cognitive Architecture Protocol — Day 18 Your job: help me separate the facts of one past event from the meaning I assigned it — and consider a more accurate meaning. Ask me 6 questions, one at a time: • The event in plain facts, no interpretation • The meaning I assigned it at the time • The meaning that has calcified since • What that meaning has cost me • Who I'd be if I didn't hold that meaning • What actually happened vs. what I've told myself happened After my answers, give me: A) THE FACTS, separated from the interpretation. B) THE OLD MEANING and what it was protecting me from feeling. C) A MORE ACCURATE MEANING — not a positive reframe. Accurate. D) ONE BEHAVIORAL SHIFT that would only make sense under the new meaning. Then: • CAP SCOREBOARD ENTRY • PHASE ARTIFACT (event, facts, old meaning, new meaning, behavior) No toxic positivity. Truth only.

Sit with the new meaning for an hour. Do the behavior today or tomorrow.

You have a shape. You do certain things easily that most people find hard. This isn't ego. This is operational. When you work inside your natural shape, you produce disproportionate value for proportional effort. Outside it, you grind.

Today you map your shape.

Think of three times in the last year where something felt surprisingly easy — and the result was surprisingly good. Try to remember what you were doing, what kind of problem it was, who you were helping.

day-19-leverage.txt
Cognitive Architecture Protocol — Day 19 Your job: help me identify my highest-leverage behavior pattern — the place where small effort produces disproportionate value. Ask me 6 questions, one at a time: • 3 recent moments where something felt easy and went well • What I was doing in each one • What kind of problem I was solving • Who benefited • Why it felt easy (structural, not "because I love it") • What's common across all three After my answers, give me: A) MY LEVERAGE SHAPE — the structural pattern across those three moments. B) WHERE I'M CURRENTLY WORKING OUTSIDE IT and paying a tax. C) ONE REDIRECTION — a shift this week that pulls more of my time into the leverage shape. D) WHAT I'LL HAVE TO SAY NO TO so I can say yes to this. Then: • CAP SCOREBOARD ENTRY • PHASE ARTIFACT (leverage shape, tax areas, redirection, no) Operational, not "find your passion."

Make the redirection this week. Notice what feels different about the effort.

Synthesis day. Days 11 through 19 gave you the pieces — the good day, the beliefs, the fears, the values, the energy profile, the meanings, the leverage shape. Today you stitch them into one document you can read in two minutes. This is your new operating blueprint.

Gather your Phase Artifacts from days 11 through 19. Paste them into the prompt below. If you missed a day, skip — don't fill it in.

day-20-blueprint.txt
Cognitive Architecture Protocol — Day 20 — Phase 2 Operating Blueprint I am synthesizing Phase 2. Use ONLY the artifacts I paste. Do not add assumptions. Here are the artifacts from Days 11–19: [PASTE ALL NINE ARTIFACTS IN ORDER] Your job: produce a single document titled "PHASE 2 — OPERATING BLUEPRINT" with these sections: 1. THE GOOD DAY SHAPE Minimum version + first upgrade + protecting if/then rule. 2. THE HONEST BELIEFS The 2–3 beliefs I'm working to trust, each with their evidence + one behavior. 3. THE FEAR MAP The specific fears named, their realistic worst case, and the fear-informed actions. 4. THE VALUES CORRECTION Where stated vs. revealed diverged + the one realignment. 5. THE ENERGY RULES My givers, my takers, the protection rule, the 14-day no. 6. THE LEVERAGE SHAPE My structural leverage + what I'm redirecting toward it + what I'm saying no to. 7. THE NEW MEANING The past event reread + the behavioral shift under the new meaning. 8. THE KEEP / STOP / START 3 things I'm keeping, 3 stopping, 3 starting — based on everything above. Neutral, operational language. No motivation. This becomes the input for Phase 3.

Save the Operating Blueprint. Read it once slowly. Take a day before Phase 3. You're about to start running this thing in real conditions.

RITE OF COMPLETION · PHASE TWO
You finished the Architect.
You now have a blueprint for how you actually want to operate. Not aspiration. Design. Phase 3 is where you prove it in conditions you don't control.
§
PHASE THREE OF THREE

The Deployment

DAYS TWENTY-ONE THROUGH THIRTY

Prove it in real life. The new system only matters if it survives contact with real people, real triggers, and real exhaustion. This phase is about operating under pressure without collapsing back to default.

SETUP · DO THIS ONCE BEFORE DAY 21

Open a new AI chat. Name it: "CAP — Days 21–30 (Deployment)". Start fresh. At the start of Day 21, you'll paste your Phase 2 Operating Blueprint.

Paste the master context prompt below.

phase-3-master-context.txt · paste once
Cognitive Architecture Protocol — Phase 3 (Deployment) — Master Setup You are my Behavior Deployment Coach using evidence-based methods. Context: This chat contains Days 21–30 of Phase 3: Deployment. Your job is to help me run my new operating system in real conditions without collapsing to defaults. Global Rules (apply every day): • Ask the setup questions for each day before analyzing. • Use plain English. No therapy language. No motivational speeches. • Keep responses short and actionable. • Every day, end your response with two clearly labeled blocks: — CAP SCOREBOARD ENTRY — PHASE ARTIFACT (titled "Day N — [theme]") • Do not invent data. I log my score in a note outside this chat. Begin when I paste Day 21.

A blueprint doesn't move your life. Action inside the blueprint does. And the most honest test of any new system is whether you can take the smallest version of the first move before your mind finds twelve reasons not to.

Today is not about momentum. It's about proving the wheels turn.

Open your Phase 2 Operating Blueprint. Pick one area where the blueprint says you should be acting differently but you haven't started yet.

day-21-smallest-action.txt
Cognitive Architecture Protocol — Day 21 Your job: help me take the smallest possible first action inside my new blueprint — today. Here is my Phase 2 Operating Blueprint: [PASTE OPERATING BLUEPRINT FROM DAY 20] Ask me 4 questions, one at a time: • Which area of the blueprint I haven't started acting on • What's stopping me (specifically — not "I'm busy") • What I'd be willing to do in under 10 minutes today • What would quietly count as progress if no one was watching After my answers, give me: A) THE SMALLEST HONEST ACTION — under 10 minutes, doable today. B) THE DIRECT RESISTANCE that will show up and the exact sentence to say back to it. C) ONE PROOF MARKER — how I'll know I actually did the thing (not a feeling). D) WHAT THE NEXT SMALL ACTION LOOKS LIKE after this one, if momentum survives. Then: • CAP SCOREBOARD ENTRY • PHASE ARTIFACT (smallest action, resistance script, proof marker, next action) No pep talk. Just the move.

Do the action. Ten minutes. Log the proof marker.

Your default behavior is organized around who you've been. Most of your decisions are made from the past version of you — before the blueprint. Today we test what it looks like to make one specific decision from the version you're becoming.

Not pretending. Not performing. Deciding.

Identify one decision you're about to make this week — anything from a conversation to a commitment to a purchase. Pick one where the "old you" and "new you" would likely choose differently.

day-22-becoming.txt
Cognitive Architecture Protocol — Day 22 Your job: help me run one real decision through the lens of the person my blueprint describes — not the default me. Ask me 5 questions, one at a time: • The decision coming up this week • What the "old me" would do • What the blueprint version of me would likely do • The specific discomfort of choosing the second option • What's the cost of defaulting back After my answers, give me: A) THE TWO PATHS — the old default + the aligned choice, in short sentences. B) THE KEY DIFFERENCE — what separates them operationally, not aesthetically. C) ONE SUPPORT MOVE that makes the aligned choice easier to execute (environment, script, timing). D) WHAT WILL LIKELY PULL ME BACK at the moment of decision. Then: • CAP SCOREBOARD ENTRY • PHASE ARTIFACT (decision, two paths, key difference, support move, pullback) Operational clarity, no identity-talk inflation.

Make the decision from the blueprint version. Notice what it costs you. Notice what it gives back.

People treat you the way you've trained them to. Not once. Over years, in thousands of micro-interactions where you either held a line or didn't. Today you pick one relationship and one line — small, specific — and start retraining.

Your blueprint is going to fail unless the people around you learn the new rules.

Identify one relationship where there's a recurring pattern that doesn't fit your blueprint — being over-relied on, being talked over, being asked for things at bad times, being taken for granted. Specific person. Specific pattern.

day-23-retraining.txt
Cognitive Architecture Protocol — Day 23 Your job: help me start retraining one relationship pattern with one specific interaction this week. Ask me 5 questions, one at a time: • The person and the pattern • What I've implicitly taught them to expect • What the blueprint version of me would expect instead • The smallest change in behavior that would signal the new expectation • What I'm afraid will happen if I make that change After my answers, give me: A) THE SIGNAL — one small behavioral change that communicates the new expectation without a confrontation. B) ONE SENTENCE I can actually say in the moment, in my own voice (short — editable). C) THE LIKELY REACTION and what to do when it shows up. D) WHAT TO DO IF THE PATTERN RETURNS after I signal (most do, the first time). Then: • CAP SCOREBOARD ENTRY • PHASE ARTIFACT (person, pattern, signal, sentence, reaction, return plan) Compassionate, not passive. Direct, not harsh.

Use the signal this week. One interaction. Watch the reaction. Hold the line when the pattern tries to return.

Distraction isn't about willpower. It's about what you've protected and what you've left exposed. Today you pick one thing that matters to your blueprint, and put a simple fence around it before the next week tries to eat it.

Pick one priority from your blueprint that keeps getting eroded by small distractions. Health, focus time, family time, creative time, rest.

day-24-protect.txt
Cognitive Architecture Protocol — Day 24 Your job: help me build a practical fence around one priority before this week erodes it. Ask me 5 questions, one at a time: • The priority • The predictable distractions that attack it • When (day, time, context) it gets attacked most • What fence I've tried before that didn't hold • What I'm unwilling to sacrifice to protect this After my answers, give me: A) THE FENCE — a simple operational rule (environment, calendar, device setting) that protects this priority this week. B) ONE COMMUNICATION — what I tell the one person most likely to run into the fence. C) ONE CONDITIONAL EXCEPTION — the one scenario where the fence can bend (so it doesn't become a prison). D) HOW TO MEASURE that the fence actually held this week. Then: • CAP SCOREBOARD ENTRY • PHASE ARTIFACT (priority, fence, communication, exception, measure) Structural, lightweight, real.

Put the fence up tonight. Send the communication tomorrow if needed. Measure by Sunday.

The comfort zone isn't where growth dies — it's what you build out from. Today you pick one stretch your blueprint quietly asks for, and design it to be hard enough to matter but small enough that you'll actually do it.

Pick one area where the blueprint calls for a stretch — a conversation, a creative risk, a visibility move, a physical challenge. Something in range, not a leap.

day-25-stretch.txt
Cognitive Architecture Protocol — Day 25 Your job: help me design one deliberate stretch for this week — harder than default, smaller than heroic. Ask me 5 questions, one at a time: • The area of stretch • What a "5 out of 10" stretch would look like (not a 9) • What's already in range that I've been avoiding • What resource or support I have available • What a "botched" version of this stretch still teaches me After my answers, give me: A) THE STRETCH — defined by behavior, not outcome. B) THE PRE-COMMITMENT — how I lock this in before my nerves talk me out. C) THE DEBRIEF QUESTIONS I'll ask after, whether it goes well or not. D) THE FAILURE CASE — what still counts as progress even if the outcome is bad. Then: • CAP SCOREBOARD ENTRY • PHASE ARTIFACT (stretch, pre-commitment, debrief, failure case) Calm ambition. No heroics.

Lock the pre-commitment today. Do the stretch this week. Run the debrief regardless of outcome.

At some point this week, you've already slipped back into an old pattern. Maybe more than once. Most people bury the slip in self-judgment and lose the information. Today you recover the data instead.

A misstep inside a good system is gold — it tells you exactly where the system needs a patch.

Identify one specific misstep from the last 5 days. Not "I did badly at life." One concrete moment where the old pattern won.

day-26-misstep.txt
Cognitive Architecture Protocol — Day 26 Your job: help me extract usable data from one misstep this week — without self-judgment. Ask me 5 questions, one at a time: • The specific misstep • What was happening right before it • What I felt in my body • The thought that justified the misstep in the moment • What I did immediately after After my answers, give me: A) THE TRIGGER PATH — the sequence of trigger → thought → behavior. B) THE SYSTEM GAP — where my current design didn't catch the pattern. C) ONE PATCH — a small structural addition that closes the gap for next time. D) THE RESET PROTOCOL — what I do in the 10 minutes after the next misstep, so I don't spiral. Then: • CAP SCOREBOARD ENTRY • PHASE ARTIFACT (misstep, trigger path, system gap, patch, reset protocol) Neutral. Clinical. Useful.

Install the patch. Rehearse the reset protocol once, quietly, so it's available when you need it.

Your brain has a filter. It notices what you've trained it to notice. Most people train this filter by accident — by what they scroll, what they complain about, what they fear. Today you train it on purpose for one week.

Pick one thing you want your brain to get better at noticing. Evidence that you're capable. Moments of real connection. Micro-wins. Opportunities you usually miss. Leverage-shaped tasks.

day-27-filter.txt
Cognitive Architecture Protocol — Day 27 Your job: help me deliberately train my attention filter for the next 7 days around one specific target. Ask me 4 questions, one at a time: • What I want to train my brain to notice • Where and when that thing tends to show up • What usually distracts me from noticing it • How I'll capture what I notice (journal, note, voice memo) After my answers, give me: A) THE FILTER RULE — a short phrase I can run in the back of my mind for the week. B) THE DAILY PROMPT — one question I ask myself before bed to log what I noticed. C) THE OVERRIDE — what to do when the old filter tries to take over. D) A MEASURABLE RESULT — what will tell me the filter is installing after 7 days. Then: • CAP SCOREBOARD ENTRY • PHASE ARTIFACT (target, filter rule, daily prompt, override, result) Lightweight, repeatable.

Run the filter for 7 days. Ask the daily prompt each night. Notice what your brain starts surfacing.

There are predictable threats to any new system. Not dramatic ones. Ordinary ones: travel, illness, a hard week at work, a person pushing old buttons, an old mood descending. If you don't name them now, they'll catch you on a Tuesday you weren't expecting.

Look at the next 30 days. What's coming that could derail your blueprint? A trip, a visit, a deadline, a season, a holiday, a recurring dynamic?

day-28-defense.txt
Cognitive Architecture Protocol — Day 28 Your job: help me build a simple defense plan against the top 3 threats to my blueprint in the next 30 days. Ask me 5 questions, one at a time: • The 3 most predictable threats coming (people, events, seasons, moods) • Which part of the blueprint each one endangers • What I historically do when each threat hits • What I have available to help • What I've noticed about warning signs before each threat lands After my answers, give me: A) THE THREAT MAP — each threat + what it targets + the historical response. B) ONE DEFENSE MOVE per threat — something I can set up now, not when it's on me. C) THE WARNING SIGNS I'll watch for, each one paired with one action. D) THE FALLBACK MINIMUM VERSION of the blueprint that keeps the core alive during a rough week. Then: • CAP SCOREBOARD ENTRY • PHASE ARTIFACT (threats, defense moves, warning signs, minimum version) Pragmatic, not paranoid.

Install at least one defense move today. Put warning signs on your radar. Know your minimum version cold.

Self-betrayal is quiet. It's saying yes when you meant no. It's taking the thing that's offered instead of the thing you wanted. It's agreeing in the room and resenting in the car. Today you build a simple test so you can catch it before it happens instead of after.

Name one recent decision where you betrayed yourself. Not dramatically — in the ordinary way. Saying yes, showing up, agreeing, performing. You know the moment.

day-29-alignment.txt
Cognitive Architecture Protocol — Day 29 Your job: help me build a simple decision test I can run in real time to catch self-betrayal before it happens. Ask me 5 questions, one at a time: • The recent decision I want to learn from • What I actually wanted vs. what I said • Who I was trying to protect or please • The signal in my body that was there but I ignored • What would have happened if I'd said the truer thing After my answers, give me: A) THE DECISION TEST — a short check (3 questions max) I can run in 30 seconds before answering. B) THE EMBODIED SIGNAL that I'll use as a tell. C) A HOLDING PHRASE — what I say when I need time to actually check in (no performative "let me think about it"). D) WHAT HAPPENS if I use the test and the aligned answer costs me something real. Then: • CAP SCOREBOARD ENTRY • PHASE ARTIFACT (decision test, embodied signal, holding phrase, cost plan) Honest, not hostile.

Run the decision test in one real moment this week. Even if the answer is uncomfortable. Especially then.

Final synthesis. You don't close this with a big transformation speech. You close it with a clean record of what you actually did, what actually moved, and what you're locking in for the 90 days ahead.

The goal here isn't to feel different. It's to be operating differently.

Gather your Phase Artifacts from Days 21 through 29. Paste them in order into the prompt below.

day-30-trajectory.txt
Cognitive Architecture Protocol — Day 30 — Phase 3 Deployment Summary I am synthesizing Phase 3. Use ONLY the artifacts I paste. Do not add assumptions. Here are the artifacts from Days 21–29: [PASTE ALL NINE ARTIFACTS IN ORDER] Your job: produce one document titled "PHASE 3 — DEPLOYMENT SUMMARY" with these sections: 1. WHAT ACTUALLY MOVED The 2–3 behavioral shifts I can prove happened, in plain language. 2. WHAT DIDN'T Where the blueprint met friction and didn't translate — non-judgmental. 3. THE REAL LEARNINGS What I now know about myself that I didn't before Phase 3 started. 4. THE 90-DAY LOCK The 3 rules, rituals, or protections I am committing to carry forward for the next 90 days. 5. THE EARLY WARNING SIGNS What I'll watch for that tells me I'm drifting back to default. 6. THE RECOVERY PROTOCOL Exactly what I do if I notice I've drifted — in 10 minutes or less. Neutral, operational. No motivational closing. This is the final input for my System Review.

Save the Deployment Summary. You now have three phase documents — the Baseline Snapshot, the Operating Blueprint, and the Deployment Summary. Take a day. Then come back for the Final System Review below.

RITE OF COMPLETION · PHASE THREE
You finished the Deployment.
Thirty days of honest work. You audited, you designed, you ran it in real conditions. Most people never make it to here. Don't skip the final review below — it's where the whole thing gets pulled into a single field of view.
§
FINAL SYSTEM REVIEW
Pull it all
into focus.

One master prompt, pasted into a fresh AI chat, that takes your three phase summaries and hands back a single operating document you can return to for years.

Here's what you'll do:

  • Open a brand-new, empty AI chat — not one of your phase containers
  • Paste the master prompt below
  • The AI will ask for your Phase 1, then Phase 2, then Phase 3 in sequence
  • After all three are in, it produces the Final System Review — seven sections, scannable, reusable
  • Save it in the same place you saved your Inner Profile. This is the top-level document. You'll reference it more than any other.
WHY A FRESH CHAT
Your three phase chats have a lot of context in them.
A clean chat means the review is grounded only in your three summary documents — no noise, no drift.
final-system-review.txt · paste into new chat
Cognitive Architecture — Final System Review (Master Recap) You are my Cognitive Systems Analyst. Your role is to perform a full diagnostic and synthesis of my 30-day Cognitive Architecture Protocol journey. CONTEXT: This program was completed across three phases, each summarized separately: • Phase 1 — Baseline Snapshot (Audit) • Phase 2 — Operating Blueprint (Architect) • Phase 3 — Deployment Summary (Deployment) RULES: • Use ONLY the information I paste. Do not add assumptions. • Do not motivate, praise, exaggerate, or soften. • This is a system-level review, not therapy. • Maintain phase boundaries: Section 1 uses Phase 1 only. Section 3 uses Phase 2 + Phase 3 only. • If phases conflict, name the conflict explicitly rather than blending it. • Be precise, grounded, and honest. • Clean and scannable formatting. OUTPUT FORMAT: • Use the exact section headers provided below. • Use bullet points where requested. • Keep language neutral and operational. • Do not include extra sections. • Do not write advice unless a section explicitly asks for it. — INPUT 1 — PHASE 1: BASELINE SNAPSHOT Ask me to paste the full block labeled "PHASE 1 — BASELINE SNAPSHOT." Then WAIT. Do not analyze. When I paste it, respond with exactly: "Phase 1 received. Now paste PHASE 2 — OPERATING BLUEPRINT." INPUT 2 — PHASE 2: OPERATING BLUEPRINT Ask me to paste the full block. WAIT for input. When pasted, respond with exactly: "Phase 2 received. Now paste PHASE 3 — DEPLOYMENT SUMMARY." INPUT 3 — PHASE 3: DEPLOYMENT SUMMARY Ask me to paste the full block. WAIT. When pasted, respond with exactly: "All phases received. Running Final System Review now." — FINAL SYSTEM REVIEW OUTPUT SECTION 1 — ORIGINAL OPERATING SYSTEM (BEFORE) Using Phase 1 data only. Describe how I was operating before this protocol. Subheaders (exact): • Dominant belief patterns • Emotional regulation strategies • Default coping/avoidance behaviors • Primary energy leaks Under each subheader, 3–7 bullets using Phase 1 language where possible. SECTION 2 — THE TRUE CONSTRAINT Identify the single underlying constraint that most limited my progress before the protocol. • Constraint (1 sentence) • Why it made sense then (2–5 bullets) • Why it became costly (2–5 bullets) • Patterns it explains (list the Phase 1 patterns) Do not recommend fixes here. SECTION 3 — THE SYSTEM I BUILT (AFTER) Using Phase 2 + Phase 3 data only. Describe the system I now operate from. Focus on demonstrated behavior, not intention. Subheaders (exact): • New default beliefs • Decision rules • Pressure response • Fear handling • Boundaries & energy protection Under each, 3–7 bullets grounded in Phase 2/3 evidence. SECTION 4 — PERSONAL DRIFT PATTERN How I am most likely to drift under stress. • Trigger conditions (3–6 bullets) • Early warning signs (3–6 bullets) • Regression behaviors (3–6 bullets) Use Phase 3 stress/drift evidence. SECTION 5 — KEYSTONE PROTECTION RULE The single behavior or rule that most protects my system. • Keystone rule (1 sentence, imperative form) • Why it protects the system (3–6 bullets) • What breaks first if missing (3–6 bullets) Consistent with Phase 2 keystone behavior + Phase 3 reality. SECTION 6 — RE-ENTRY PROTOCOL A simple drift-recovery plan. • Drift signal: • Immediate corrective action: • Reset sentence: Executable in under 5 minutes. SECTION 7 — ONE-PAGE OPERATING SUMMARY A tight, reusable block I can keep at hand. Include: • 3–5 core beliefs • Keystone behavior • Primary drift risk • Re-entry rule • What I must protect • What I must stop doing Short bullets, max 1 line each. No commentary. End with: "END — FINAL SYSTEM REVIEW" — IMPORTANT RULES No motivational language. No congratulations. No softening uncomfortable truths. Increase clarity, not emotion.

This document becomes your command console.

You'll read it when you feel drift starting. You'll read it before big decisions. You'll re-run it every six to twelve months with new phase summaries, and watch how the system updates itself around the life you're actually living.

One more thing before I let you go.

§
RULES OF ENGAGEMENT
How to actually
run this protocol.

Five ground rules. Re-read them if things feel heavy or unclear. They're the difference between doing the work and performing it.

One day per day. No stacking.

Doing two days in one day doesn't save time. It collapses the processing window that makes each day work. If you have extra energy, use it to do the proof action — not to race ahead.

Do not perform.

Answer as the version of you that's tired, contradictory, and real — not the healed, optimized, enlightened version you wish were true. Messy answers are better truth. The whole system falls apart if you're performing for the AI or for yourself.

Use containers.

A new AI project or chat for each phase. Don't run the whole 30 days in a single thread — the context gets noisy and the AI starts blending days. Each phase, fresh chat, paste the relevant master context, and go.

Do the proof action.

Insight without action is entertainment. Every day has a small, real-world action attached. That's not optional. The action is the data. The action is the result. The action is the difference between a thought you had and a life you actually changed.

Log the scoreboard.

One short entry per day in a note outside the AI. The scoreboard isn't tracking for its own sake — it's a physical proof that you showed up. On Day 30, you'll look at the scoreboard and see something most people never see: thirty consecutive days of themselves taking their own life seriously.

If you miss a day, don't restart.
Just pick up where you left off. The sequence works even with gaps.
§
A few honest notes
READ ONCE BEFORE YOU BEGIN

I built this system because I've used it on myself and it works. But I'm not a therapist, a doctor, or a mental health professional — and this system isn't a replacement for any of those things.

This is not therapy.

The prompts go into real material — origin stories, shadow patterns, old meanings. If at any point something comes up that feels bigger than you can hold on your own, stop the protocol and talk to a professional. That's not weakness. That's the protocol working — it surfaced something that deserves human care.

This is not medical or psychiatric advice.

If you're on medication, in treatment, or working through a diagnosis — this doesn't replace any of it. Run anything that looks clinical by your actual care provider. AI is a mirror. It is not a clinician.

This is not crisis support.

If you're in crisis — thoughts of harming yourself or someone else, an acute mental health emergency — please reach out to a professional or crisis line in your country. 988 in the US. Talking with AI about these topics can feel helpful but it is not the right tool for acute moments.

When to pause the protocol.

  • When a day stirs something bigger than you expected and you don't feel okay
  • When you're in an unstable life situation (grief, major transition, active crisis)
  • When you notice you're using the protocol to self-flagellate instead of self-understand
  • When you've had a genuinely great day and it feels more useful to just live it

Pausing doesn't end the protocol. You can pick it up when the ground is steadier.

§

CLOSING

You bought a mirror.
You learned how to look into it.

Most people use AI for a year and end up shallower — faster at producing, slower at thinking, more anxious, less certain who they actually are. You just used it to do the opposite. You ran yourself through an audit, designed a system that fits your real life, and proved it in real conditions.

That puts you in a group so small it's almost weird.

From here, come back to this whenever you feel drift. Re-run the protocol once a year. The documents you made — your Inner Profile, your Baseline Snapshot, your Operating Blueprint, your Deployment Summary, your Final System Review — are yours for life. You own them. Not the AI. Not Anthropic. Not OpenAI. You.

That's what this was always about. You stay human. You use the machine. You become more yourself, not less.

FINAL NOTE
Send me what you find. I read everything.
seggy@seggysaid.com
IF YOU'RE READY FOR WHAT'S NEXT

Conversations With The Infinite · Vol. II

The Wonder Prompt System taught you how to use AI to upgrade your operating system. Conversations With The Infinite is what you do when the operating system is running and you want to go deeper — fifteen prompts designed for the parts of you that don't have answers yet. Interior. Bonds. Horizon. Not how to think. What to look at.

Open the next door