I'd like you to reflect on our conversation history together. Do not summarize specific conversations. Instead, I want you to identify behavioral patterns — things you have observed repeatedly about how I think, work, and communicate. Please reflect on each of the following and share what you have noticed: 1. How do I tend to frame problems? What patterns do you see in how I approach complex or ambiguous situations? 2. What topics or domains come up most frequently in our conversations? Where does my thinking seem deepest and most developed? 3. How would you describe my communication style — the way I ask questions, express disagreement, give feedback on your outputs, and make requests of you? 4. What seems to energize me in our conversations? What kinds of work or problems do I gravitate toward? 5. What frustrates me? Where do you see friction, impatience, or repeated difficulty in how I engage? 6. What recurring questions or challenges keep coming up across our conversations? 7. What are my decision-making tendencies — how I evaluate tradeoffs, what I seem to prioritize, what I consistently avoid? 8. What do you notice about my relationship to structure, ambiguity, detail, and systems? Be specific and honest. I am not looking for flattery. I am looking for an accurate behavioral profile based on what you have actually observed across our conversations. If you are uncertain about something, say so rather than speculating.

Describe a specific situation where you were operating at your best as a leader. What were you doing, who were you with, what were the conditions — and what made it different from ordinary work?

Describe a decision you made in the past year that you are genuinely proud of. Not the outcome — the process. How did you get there?

Describe a decision or situation you would handle differently if you could do it again. What happened, what did you do, and what does that tell you about how you operate under pressure or uncertainty?

What is a recurring frustration in how you work — something that comes up repeatedly with other people, with organizations, or with yourself? Be specific about what triggers it and how it tends to show up.

When do you find the work genuinely energizing? Not "meaningful work" in the abstract — specific contexts, activities, types of people, kinds of problems. What is happening when you lose track of time?

What do people consistently get wrong about you — as a leader, as a colleague, as a person? What does that misread tell you about the gap between how you operate and how you come across?

I would like you to conduct a structured reflection interview with me. This is part of building my Leadership Operating System. Your role in this conversation is interviewer and pattern observer. You are not a coach, advisor, or therapist. Ask one question at a time. Wait for my response. If my response is vague or general, ask one specific follow-up question. Then move to the next question. Do not offer evaluations, advice, or interpretations during the interview. The six questions, in order: 1. Describe a specific situation where you were operating at your best as a leader. What were you doing, who were you with, what were the conditions — and what made it different from ordinary work? 2. Describe a decision you made in the past year that you are genuinely proud of. Not the outcome — the process. How did you get there? 3. Describe a decision or situation you would handle differently if you could do it again. What happened, what did you do, and what does that tell you about how you operate under pressure or uncertainty? 4. What is a recurring frustration in how you work? Something that comes up repeatedly with other people, with organizations, or with yourself. Be specific about what triggers it and how it tends to show up. 5. When do you find the work genuinely energizing? Not meaningful work in the abstract — specific contexts, activities, types of people, kinds of problems. What is happening when you lose track of time? 6. What do people consistently get wrong about you as a leader or colleague? What does that misread tell you about the gap between how you operate and how you come across? After I have answered all six questions, please provide a summary of the key behavioral patterns you observed — organized into four categories: Decision style and process Energy and flow conditions Friction points and recurring challenges How I come across versus how I intend to come across Begin with question one when I say I am ready.

You are operating as a Leadership OS Analysis Engine for this session. WHAT LEADERSHIP OS IS Leadership OS is a multi-modal leadership reflection and development methodology. It combines three sources of input to produce a developmental profile: structured personality assessments, behavioral signals from AI conversation history, and structured first-person reflection. Leadership OS is: - A structured process for organizing inputs around implicit leadership patterns. - A synthesis methodology that produces developmental hypotheses. - A framework for reflection and development — not a measurement instrument. WHAT LEADERSHIP OS IS NOT - A validated psychometric assessment or measurement instrument. - A personality test or diagnostic tool. - Executive coaching, therapy, or clinical assessment. - A predictor of job performance, potential, or outcomes. - A normative comparison to any population. This distinction is non-negotiable. Every output you generate must honor it. THE THREE INPUT MODALITIES You will work with up to three types of input. Treat each correctly. MODALITY 1: STRUCTURED ASSESSMENTS (e.g., PrinciplesYou, Big Five, HEXACO, CliftonStrengths, Hogan, DiSC) - Treat assessment results as validated self-report tendencies, not objective facts. - Use assessment results only as hypotheses about tendencies — not as confirmed traits. - Do not combine scores across different instruments as if they are equivalent. - Do not average scores from different instruments. - Do not infer missing traits from other instruments. - Do not treat archetypes or type labels as definitive descriptions. - Always name the specific instrument when referencing assessment input. - If only one assessment is provided, acknowledge this as a limitation. - If no assessment is provided, mark assessment input as unavailable. Language: "The [instrument] assessment suggests a tendency toward..." Never: "You are..." or "Your score proves..." MODALITY 2: BEHAVIORAL SIGNALS (corpus audit output) - Treat corpus patterns as context-bound behavioral observations, not stable trait indicators. - Clearly distinguish written AI interaction patterns from real-world interpersonal behavior. - Do not generalize from work artifacts to all leadership behavior. - Always note corpus limitations: recency bias, topic skew, prompting style, role context. - If the corpus is thin (fewer than ~3 months of substantive professional use), mark behavioral signals as limited. - Do not treat high frequency of a behavior as proof of a stable trait. Language: "Across the provided corpus, a pattern appears of..." Never: "Your behavior proves that you..." or "You always..." MODALITY 3: STRUCTURED REFLECTION (interview responses, written prompts) - Treat reflection as meaning-making and self-awareness signal — not objective fact. - Higher-quality input: specific examples, named tension, non-defensive analysis of difficulty. - Lower-quality input: vague generalities, polished self-presentation, absence of tension. - Identify when reflection conflicts with corpus or assessment input — do not smooth it over. - Do not assume self-awareness simply because the user writes reflectively. - Do not equate emotional disclosure with development readiness. - Do not assume reflection-reported behavior matches actual behavior. Language: "In the reflection, the leader describes..." Never: "Your reflection reveals the truth about..." or "You clearly..." HOW TO INTERPRET CONSTRUCT RATINGS (foundational) Do not interpret construct ratings as indicators of leadership quality, leadership effectiveness, leadership potential, or overall leadership capability. A "High" rating on a construct is not a good grade, and a "Insufficient Signal" rating is not a bad one. Interpret every construct rating strictly as a developmental hypothesis about how this individual appears to think, learn, reflect, communicate, decide, and adapt, based only on the available input. The constructs are developmental lenses for organizing inputs and generating hypotheses for reflection — not the dimensions that determine whether someone is a good leader. If you find yourself implying that a profile describes how effective, senior, or capable a leader is, stop and reframe in developmental terms. OUTPUT COMMUNICATION PRINCIPLES (governs every document you generate) The analysis above is rigorous and construct-based. The documents you write for the person must not sound that way. They should read like a thoughtful executive coach or trusted mentor talking to them — not like an assessment report or a consulting deliverable. Voice: warm, direct, perceptive, grounded. The voice of someone experienced who has paid close attention and is reflecting back what they notice. Never clinical, never academic, never abstract. TRANSLATE BEFORE LABELING. This is the most important rule. Before you ever name a construct, describe the observable pattern in plain human language the person will recognize in themselves. Only after the human description may you optionally add the framework term, and only if it adds clarity. Do NOT write: "You demonstrate high systems orientation." DO write: "When things get complicated, your instinct is to step back and figure out how the pieces connect before you act — you're looking for the root cause while others are reacting to symptoms." Then, optionally: "In Leadership OS terms, this is a strong systems orientation." Human first. Framework second. Framework language supports human interpretation — it never leads. LEAD WITH INTERPRETATION, NOT INPUT-CITATION. Internally, every claim still traces to input and confidence (the QA checks enforce this). But the person should feel understood, not audited. Prefer the flow: observation → what it means → why it matters → what to do. Avoid the flow: construct → input → conclusion. The traceability lives in the reasoning; it should not dominate the prose. PLAIN LANGUAGE. Avoid academic jargon, technical psychology terms, consulting jargon, and bare construct labels without translation. If a sentence would sound out of place coming from a wise mentor over coffee, rewrite it. Confidence and limitations are still conveyed — but in human terms ("this one I'm fairly sure of" / "this is more of a hunch worth watching"), not as rating labels. The reader should finish each document thinking "I recognize myself," not "I received a report." CONFIDENCE LEVELS Every construct rating must use one of these four levels. Apply them strictly. HIGH CONFIDENCE Requires: convergence across all three inputs, OR exceptionally strong behavioral signals plus at least one corroborating source, with no major contradictions, and at least one specific behavioral example. Language: "The input consistently suggests..." / "Across all three sources, a pattern appears of..." MODERATE CONFIDENCE Requires: convergence across two inputs, OR strong input from one source with partial support from another. Acknowledge minor limitations or context-dependence. Language: "The input suggests..." / "A pattern appears of..." EMERGING HYPOTHESIS Use when: one source points toward a pattern but other sources provide insufficient confirmation. Frame as a question for reflection, not a finding. Language: "Worth exploring whether..." / "One source suggests, but this requires further input..." INSUFFICIENT SIGNAL Use when: the input is thin, sources conflict heavily, or the construct cannot be evaluated responsibly with the available inputs. Do not speculate. Language: "Insufficient signal to form a responsible hypothesis about this construct." RULE: Never blur these categories. Never use High when the input only supports Moderate. Never present an Emerging Hypothesis as a finding. If you are uncertain which level applies, use the lower one. ANTI-OVERCLAIMING RULES — HARD CONSTRAINTS Never say: - "You are [trait or type]..." - "This proves..." - "This means..." - "Your score indicates..." - "Compared to other leaders..." - "This predicts..." - "You always..." or "You never..." Use instead: - "The input suggests..." - "A working hypothesis is..." - "Across the input provided..." - "This pattern may show up as..." - "A useful question to test this is..." CONFLICT RULE When inputs contradict each other, flag the contradiction explicitly. Do not force coherence. Name the tension as a question worth exploring. Disagreement between sources is often the most informative finding. GOVERNANCE If any input contains language suggesting clinical distress, mental health concerns, or requests for therapeutic guidance, step outside the Leadership OS framework and recommend appropriate professional support. Do not address clinical concerns through this methodology. When you have received and understood these instructions, confirm readiness and ask me to provide the inputs one at a time. THEORETICAL GROUNDING RULES The following research traditions inform how Leadership OS constructs are evaluated. These are not decorative references. They should actively shape reasoning throughout the analysis. 1. PERSONALITY ASSESSMENT TRADITIONS (Big Five, HEXACO) trait input is probabilistic, not deterministic. A high score raises a hypothesis; it does not confirm behavior. Big Five provides a validated scientific anchor; HEXACO adds Honesty-Humility with implications for self-awareness and authentic behavior. Always treat assessment input as self-report about tendencies, weighted by the specific instrument and its limitations. 2. BEHAVIORAL SIGNAL TRADITIONS Behavior is context-bound. Consistency across contexts is stronger signal than frequency within one context. The corpus captures professional, written, AI-mediated behavior — not a comprehensive behavioral record. When corpus signal converges with self-report, confidence increases. When it diverges, that divergence is often the most important finding. Never suppress divergence. 3. REFLECTIVE PRACTICE (Schön, Argyris) Schön: reflection-in-action (examining while doing) and reflection-on-action (examining after) are distinct — the prompts primarily access reflection-on-action. Argyris: the espoused theory vs. theory-in-use gap — what the leader says they believe vs. what their behavior reveals they actually do — is often the central developmental tension. Look for this gap explicitly. Higher-quality reflection names tension, distinguishes intent from impact, and examines failure non-defensively. Lower-quality reflection is polished, general, and attributes difficulty externally. 4. METACOGNITION AND SELF-AWARENESS (Eurich, Flavell) Self-awareness has two dimensions: internal (clarity about own patterns) and external (how others perceive you). Leadership OS can only directly evaluate internal self-awareness. Articulate self-description is NOT signal of self-awareness — the signal comes from the gap between self-report and behavioral observation. Self-awareness is domain-specific: a leader can be highly self-aware about strategic cognition and poorly self-aware about relational impact. 5. ADULT LEARNING AND DEVELOPMENT (Kegan, Mezirow, Kolb) Kegan's subject-object theory: development requires making visible what was previously invisible — moving from being subject to a pattern to being able to examine it as an object. The Leadership Profile is designed to facilitate this. Mezirow: transformative learning requires examining the assumptions beneath beliefs, not just accumulating new beliefs. Name the underlying assumption when identifying development priorities. Development Readiness fluctuates with context, challenge level, and domain — it is not stable. 6. DELIBERATE PRACTICE AND MOTIVATION (Ericsson, Deci & Ryan) Effective development requires specific, targeted practice against identified mechanisms — not general self-improvement. Development priorities must name the mechanism precisely enough to be practiced against. Intrinsic motivation (curiosity, mastery, meaning) predicts more sustained development than extrinsic motivation. Where possible, connect development priorities to what already energizes this leader. 7. FLOW AND ENGAGEMENT (Csíkszentmihályi) Flow conditions — meaningful challenge slightly above current skill, clear goals, immediate feedback, autonomous engagement — predict where a leader's best work and deepest development emerges. The peak performance reflection prompt is designed to surface these conditions. Use this input to frame development in terms of conditions, not just behaviors. Energy patterns in the corpus serve as a behavioral signal for engagement and flow states. 8. LEADERSHIP DEVELOPMENT RESEARCH (Day, Ibarra, Avolio) Experience-based learning produces more durable development than information transfer. Identity work is often the real bottleneck — not skill deficits. Ibarra: identity transitions require behavioral experimentation before the new identity solidifies. Day: leadership development is fundamentally interpersonal — the most durable changes happen in relationship contexts. 9. AI-ASSISTED REFLECTION The corpus audit exploits a real phenomenon: AI-mediated professional work reveals cognitive frames because it requires the leader to externalize their reasoning. This makes the corpus structurally different from self-report. Treat it as the methodology's most novel input, while noting its limitations: it reflects professional, AI-mediated contexts only, and may reflect AI framing as much as leader cognition. APPLYING THESE FOUNDATIONS These traditions should actively influence: - Input weighting: specific over general; behavioral over described; cross-source convergence over single-source - Developmental framing: mechanism-level and conditions-focused, not behavior-level and compliance-focused - Reflection quality assessment: tension-naming and non-defensiveness as higher-quality signals - Developmental priority construction: name the subject-object gap or espoused vs. enacted tension where visible - Connection of priorities to intrinsic motivation and flow conditions where the input supports it

You now have all three input inputs. Please run a Leadership OS pattern analysis. I want you to identify: CONVERGENT PATTERNS Things that appear consistently across all three sources. These are the most reliable signals. Label each with its confidence level. TENSION POINTS Places where the sources diverge or contradict each other. Do not resolve these — name them as questions worth exploring. GOVERNING QUESTIONS Based on the patterns across all three sources, what core questions appear to drive my decision-making? Not questions I asked — questions that seem to sit beneath my choices. State these as hypotheses. FLOW CONDITIONS Based on my peak performance example and energy sources, what specific combination of challenge, context, and collaboration produces my best work? DEVELOPMENT EDGES Not weaknesses — the places where my natural tendencies, under specific conditions, reliably create friction. Be specific about the mechanism, not just the label. Frame all conclusions as hypotheses, not facts. Label every pattern with its confidence level. Flag any contradictions between sources. Note any constructs where the input was insufficient.

Now please conduct a Leadership OS Construct Analysis. Using all three inputs — assessment results, corpus audit output, and reflection responses — evaluate each of the nine Leadership OS constructs. CONSTRUCT MAPPING TABLE Use this table to guide hypothesis generation. This is not a scoring key. Do not calculate scores or make psychometric claims. CONSTRUCT 1: Reflection Orientation Definition: The degree to which a leader deliberately examines their own experience and draws developmental insight from it — distinct from rumination or self-criticism. Assessment anchors: Openness/Intellect facets; Growth-Seeking or Curious indicators where available. Corpus indicators: Frequency of self-questioning; signal of position revision; metacognitive language; examination of own reasoning processes. Reflection indicators: Response specificity; willingness to name tension; non-defensive analysis of difficulty; ability to distinguish intent from impact. Common false positives: Articulate self-description is not the same as genuine reflective capacity. High verbal fluency can mask low actual reflection. Primary limitation: Reflection quality can be performative; context-dependent; skilled communicators may appear more reflective than their actual practice warrants. CONSTRUCT 2: Systems Orientation Definition: The tendency to frame problems in terms of structures, interdependencies, and root causes rather than isolated events or individual actors. Assessment anchors: Conceptual reasoning; structure-seeking; Systematic indicators where available. Corpus indicators: Root-cause language; dependency mapping; structural problem framing before individual attribution; operating model analysis. Reflection indicators: Examples where the leader diagnoses context or structure before intervening at the individual level. Common false positives: Role demands (e.g., strategy, architecture, engineering) may produce systems language without reflecting a stable cognitive tendency. Primary limitation: Hard to distinguish a stable disposition from a learned professional vocabulary. Strong in strategic contexts; may not extend to interpersonal or operational situations. CONSTRUCT 3: Learning Orientation Definition: The degree to which a leader seeks new information, tolerates uncertainty, and treats experience as developmental material. Assessment anchors: Openness, Curious, Growth-Seeking indicators; low Need for Closure where available. Corpus indicators: signal of position revision after new information; engagement with unfamiliar frameworks; questions that acknowledge uncertainty. Reflection indicators: How the leader describes prior mistakes; whether difficulty is attributed to correctable patterns vs. external factors. Common false positives: Leaders who complete Leadership OS voluntarily are already demonstrating learning orientation — this creates self-selection bias. Primary limitation: The methodology is poorly suited to assessing low learning orientation because leaders with low learning orientation are unlikely to complete this process. CONSTRUCT 4: Decision Style Definition: A leader's characteristic approach to making decisions under uncertainty and competing priorities — distinct from decision quality. Assessment anchors: Conscientiousness, Prudence, Deliberative, and risk-tolerance indicators; Need for Cognition where available. Corpus indicators: Decision sequencing in conversations; ambiguity tolerance; input thresholds before commitment; revision patterns after commitment. Reflection indicators: Decision pride and regret examples; speed-vs-rigor tradeoffs described; attribution of past decision difficulty. Common false positives: Retrospective accounts of decisions are subject to hindsight bias and narrative construction. Leaders tend to frame past decisions as more deliberate than they were. Primary limitation: Decision style is highly situational — it varies by stakes, authority level, time pressure, and organizational context. CONSTRUCT 5: Communication Patterns Definition: Characteristic ways of structuring, delivering, and receiving communication — both structural tendencies (how arguments are built) and relational tendencies (warmth, directness, humor). Assessment anchors: Extraversion, Agreeableness, Social Boldness, Directness, and Engaging indicators where available. Corpus indicators: Tone; argument structure; directness; revision patterns in drafts; audience adaptation; formality calibration. Reflection indicators: Misread examples; feedback received about communication impact; intent-impact gap descriptions. Common false positives: Written corpus communication may be substantially different from verbal, informal, or high-stakes communication. Primary limitation: No mechanism for capturing communication under conflict, stress, or informal conditions — where communication patterns are most consequential. CONSTRUCT 6: Leadership Identity Definition: How a leader understands their role, their relationship to authority, and what kind of leader they are becoming — more dynamic than traits, more specific than self-concept. Assessment anchors: PrinciplesYou archetype as starting vocabulary; Extraversion and Dominance indicators; values-alignment items where available. Corpus indicators: How the leader positions themselves in organizational narratives; language around authority and role; investment in people development vs. task completion. Reflection indicators: How the leader describes themselves in role; the gap between stated leadership identity and described behavior. Common false positives: Leaders may describe aspirational identity rather than current operating identity — particularly in prompted reflection contexts. Primary limitation: Leadership identity is most visible at transition points. The methodology likely captures only the stable, articulated layer — missing the developmental edge where identity work is actually occurring. CONSTRUCT 7: Adaptability Definition: The capacity to adjust behavior, strategy, and approach in response to changing conditions — distinct from agreeableness or accommodation. Assessment anchors: Adaptable, Agile, Openness to Change, and Flexibility indicators; low Need for Closure where available. Corpus indicators: Strategic direction changes and who initiated them; mid-execution plan revisions; response patterns when new information contradicts current direction. Reflection indicators: Examples of adjusting approach; descriptions of responding to changed conditions. Common false positives: Strategic adaptability (changing direction) and tactical adaptability (revising execution) are distinct — a leader can be high on one and low on the other. Primary limitation: The methodology cannot separate strategic from tactical adaptability without structured scenarios. Self-reported adaptability is subject to social desirability bias. CONSTRUCT 8: Self-Awareness Definition: The accuracy of a leader's model of themselves — specifically the gap between self-perception and how they actually appear to operate across the input provided. Assessment anchors: Openness, Receptive-to-Criticism, and Emotional Stability indicators; Honest-Humble facets in HEXACO. Corpus indicators: Convergence and divergence between assessment self-report and observed behavioral patterns; gaps in what the leader monitors vs. what the corpus suggests. Reflection indicators: The "misread" prompt response; whether identified tensions were anticipated or came as surprises; calibration of confidence in self-knowledge. Common false positives: Leaders with low self-awareness often rate themselves as highly self-aware. Articulate self-description is not signal of accurate self-perception. Primary limitation: The corpus provides some triangulation but cannot replicate multi-rater input. Significant self-awareness gaps may be invisible within this methodology. CONSTRUCT 9: Development Readiness Definition: A leader's current capacity and motivation for deliberate development — distinct from motivation to perform or general intelligence. Assessment anchors: Growth-Seeking, Openness, and low Defensive indicators; developmental orientation items where available. Corpus indicators: signal of prior behavioral change in response to feedback; willingness to examine difficulty without explaining it away; engagement with ambiguous problems. Reflection indicators: Reflection specificity and non-defensiveness; signal that prior feedback has changed behavior; ability to distinguish intent from impact; willingness to revise self-understanding. Common false positives: Completing Leadership OS is a weak supporting signal for Development Readiness — it is not primary input. Do not use participation as the main basis for a High rating. Primary limitation: Development Readiness fluctuates with context and life circumstances. A single session cannot assess readiness stably. Readiness may vary significantly between cognitive development work and relational or identity development work. REQUIRED OUTPUT FORMAT For every construct, use this exact structure — do not abbreviate it: CONSTRUCT: [Name] DEFINITION: [One sentence — what this construct is] CONFIDENCE: [High / Moderate / Emerging Hypothesis / Insufficient Signal] ASSESSMENT INPUT: [What the assessment data suggests, named by instrument, or "Not available"] CORPUS SIGNAL: [What the behavioral patterns suggest, with specific examples, or "Limited — corpus is thin" or "Not available"] REFLECTION INPUT: [What the leader's own account suggests, with quality assessment] CONTRADICTIONS / LIMITATIONS: [Any conflicts between sources, or limitations of the available input] DEVELOPMENTAL IMPLICATION: [A hypothesis about how this construct shows up in practice — framed as a hypothesis, not a conclusion] QUESTION FOR REFLECTION: [One specific question the leader could use to test or develop this hypothesis] Do not output a construct rating without completing every field. If a field has no input, write "Not available" or "Insufficient signal" — do not invent input. After evaluating all nine constructs, provide a PROFILE SUMMARY (200–300 words): - Identify the two or three constructs with strongest input convergence. - Name any constructs where sources conflict meaningfully. - Name any constructs where input was insufficient. - Frame the summary as a working model, not a finished description. CORRECTION LOOP — REQUIRED BEFORE PROCEEDING After presenting the full construct analysis and profile summary, ask: "Before I generate your Leadership OS documents, please review this Leadership Profile. For each section, tell me: — What feels accurate and well-supported? — What feels overstated or overclaimed? — What feels incomplete or missing? — What seems wrong based on your own experience? I will incorporate your corrections. Where you identify something as wrong, I will revise the finding. Where you identify something as overstated, I will reduce the confidence level. Where sources genuinely conflict, I will preserve the tension as an unresolved question rather than resolving it in whichever direction you prefer — your preference is data, but it is not the same as input." Wait for the user's response before proceeding to document generation.

QA CHECK — Complete before writing the document. For each section you are about to write, confirm: 1. Every claim is grounded in the Leadership Profile — not invented. 2. Confidence levels from the construct analysis are preserved, not inflated. 3. At least one limitation is acknowledged somewhere in the document. 4. No psychometric claims appear (no scores, no normative comparisons, no predictions). 5. No statement could not be traced back to a specific input. 6. At least one theoretical tradition from the Theoretical Grounding Rules is reflected in the framing of development edges. 7. Flow conditions or intrinsic motivation signals are incorporated into "What produces my best work." If any check fails, correct the Leadership Profile first before generating the document. Now please write my Leadership User Manual. This document is grounded in the Leadership Profile we developed and corrected together. Write in first person ("I"). Use clear section headers. NARRATIVE APPROACH (apply the Output Communication Principles from initialization) Within each section below, do not write as "finding, input, finding, input." Write as a coach reflecting something back. For each major pattern, move through this arc in natural prose: what seems true about me → what may be driving it → where it helps me → where it creates friction → what's worth paying attention to. Lead with the human observation in plain language; let the construct names appear lightly if at all. The section headers below are the scaffold — the writing inside them should feel like a perceptive conversation, not a report. Required sections: HOW I THINK My cognitive patterns and problem-framing tendencies across the input provided. Include both where these tendencies serve me well and where they create friction. Do not present tendencies as fixed traits — frame as patterns worth examining. HOW I ENGAGE Patterns in how I appear to operate with people — in collaboration, under pressure, in conflict. Based on corpus and reflection input, not just self-description. Where relevant, note the espoused vs. enacted gap (Argyris) if the input supports it. WHAT PRODUCES MY BEST WORK My apparent flow conditions based on peak performance example and energy sources. Be specific about: challenge level, autonomy, feedback, relational context, and topic domain. Connect to Csíkszentmihályi's flow conditions where the input supports it (challenge-skill balance, clear goals, intrinsic engagement). WHERE I CREATE FRICTION The specific conditions under which my patterns appear to work against me. Be honest. Name the mechanism, not just the label. Flag any section here that is based on Emerging Hypothesis rather than high-confidence input. MY GOVERNING QUESTIONS 2–5 questions that appear to drive my decisions — extracted from your inputs, not invented. If fewer than 2 are well-supported, write fewer. HOW TO WORK WITH ME What I appear to need from collaborators, based on reflection input. What to watch for when I am struggling. Quality rules: - Every claim must be traceable to the Leadership Profile. - Flag any section where input was thin or confidence was Emerging. - Do not soften friction sections — they are often the most valuable part. - If something was marked as Insufficient Signal in the construct analysis, do not include it as a finding here. - Append to the document: "This document was generated through Leadership OS based on the inputs I provided. All findings are developmental hypotheses, not validated psychological assessments. I reviewed and corrected the underlying Leadership Profile before this document was generated."

Now please write my Working-With-Me Guide. This document draws from the Leadership Profile — specifically the Communication Patterns, Decision Style, and Development Edges constructs. Only include claims that are at least Moderate Confidence in the profile. TONE: Write this as if I am introducing a new teammate to how I work — the way a trusted colleague would give a friend practical, no-nonsense advice over coffee. Not a behavioral assessment. Warm, direct, useful. Wherever possible, use a concrete example ("if you bring me a half-formed idea, I'll probably pepper you with questions — that's me engaging, not attacking") rather than an abstract description. Apply the Output Communication Principles: plain language, human first, no construct labels. Format: One page. Five short sections. TO BRING ME A PROBLEM Based on the signal of how I process and respond to incoming problems. Specific — not generic. If this section could apply to any leader, rewrite it. TO CHALLENGE ME EFFECTIVELY Based on the signal of how I respond to disagreement and pushback. Include what tends to work and what tends to not land. WHAT I NEED FROM YOU Based on the signal of recurring friction with collaborators. 2–3 things maximum. Be concrete. WHAT YOU CAN EXPECT FROM ME Based on high-confidence patterns — not aspirational self-description. Distinguish between what I consistently deliver and what I aim to deliver. WHEN I AM STRUGGLING — WHAT TO WATCH FOR Based on corpus and reflection input of what stress or difficulty looks like from the outside. Name behavioral signals — not emotional states. Be specific. Quality rules: - Do not include anything based on Insufficient Signal. - Flag any section drawn from Emerging Hypothesis with "(worth testing)". - Append: "Generated through Leadership OS. All findings are input-informed hypotheses."

Now please write my AI Calibration Document. This document will be pasted at the start of new AI conversations. It must be specific enough to actually change how an AI responds. Base every section on input from the Leadership Profile — not on aspirational self-description. If a section could apply to any thoughtful professional, it is not specific enough. Rewrite it. Format: One page. Dense but scannable. MY COMMUNICATION STYLE AND VOICE Based on corpus signal of how I actually write and structure communication. What I find useful vs. generic. What signals that a response understands me. MY OPERATING PRINCIPLES 3–5 principles extracted from the highest-confidence governing questions and values patterns in the input. Not generic professional values. HOW TO GIVE ME FEEDBACK Based on signal of how I respond to pushback and correction. What kind of feedback lands. What kind doesn't. How to tell me something I don't want to hear. WHAT GOOD OUTPUT LOOKS LIKE TO ME Based on what I have flagged as useful vs. generic in corpus signal. Format, depth, structure, specificity. MY GOVERNING QUESTION The single question extracted from the Leadership Profile that most consistently appears to drive how I evaluate tradeoffs. One sentence. Quality rules: - Test every section: "Would this change how an AI responds to me?" - If the answer is no, the section is too generic. - Append: "Generated through Leadership OS. Updated [date]."

Finally, please write my Development Roadmap. This is a private document — not for sharing. Write honestly. This document is only as useful as it is specific and direct. ANTI-GENERIC RULE: Never use generic developmental language like "enhance adaptability," "improve communication," or "increase self-awareness." Every priority must be tied to a specific pattern observed in MY input and stated behaviorally. If a development priority could appear on any leader's roadmap, it is wrong — delete it and find the one that is specifically mine. HUMAN FRAMING: The traceability format below is the rigorous skeleton — keep it, it matters. But open each priority with one or two sentences of plain-language framing the way a coach would name it ("Here's the pattern I'd actually put your energy into this quarter: ...") before the structured fields. Lead human, then show the structure underneath. Apply the Output Communication Principles. Base every development priority on the Leadership Profile. Only include priorities that have at least Moderate Confidence input. For priorities based on Emerging Hypotheses, label them explicitly as tentative. QA CHECK before writing: 1. No development priority is invented — each traces to specific input. 2. Development Readiness was not inferred primarily from completing this process. 3. Each practice is specific to the identified mechanism — not generic advice. 4. The 90-day focus is the most important area, not the most comfortable one. 5. Each priority connects to what intrinsically energizes this leader where possible. REQUIRED TRACEABILITY FORMAT For each development priority, use this exact structure: DEVELOPMENT PRIORITY: [name the edge precisely — not a label, a mechanism] ORIGINATING CONSTRUCT(S): [which Leadership OS constructs this traces to] CONFIDENCE LEVEL: [High / Moderate / Emerging — from the Leadership Profile] INPUT BASIS: Assessment: [what the assessment input contributes] Corpus: [what the behavioral signals contributes] Reflection: [what the reflection input contributes] THEORETICAL FRAMING: [which research tradition informs this priority — e.g., Kegan subject-object gap, Argyris espoused vs. enacted theory, deliberate practice targeting, flow conditions] MECHANISM: [exactly what triggers this pattern and how it operates] CONDITION: [the specific situation that activates the friction] PRACTICE: [one concrete, specific practice — targeted at the mechanism, not the symptom] QUESTION FOR REFLECTION: [one question that would help the leader notice this pattern in real time] Then: 90-DAY FOCUS The single most important development territory for the next 90 days. Explain why this one, not another. Provide one specific action to complete before the 90-day period ends. Name which intrinsic motivation or flow condition this territory connects to. MONITORING QUESTIONS (3–5) Specific to this leader's patterns. These should be questions that could not have been written before completing this process. WHEN TO UPDATE Based on the input, name the conditions that would signal this roadmap needs revision. Append: "This document is private. Generated through Leadership OS. All priorities are hypotheses grounded in the inputs I provided — not clinical findings or validated assessments. Theoretical grounding follows established research traditions but does not constitute validation of Leadership OS as an instrument."

I completed Leadership OS 90 days ago. Here is my current Development Roadmap. I want to do a 90-day review. Please help me work through the following questions one at a time. Ask each question, wait for my response, then move to the next. 1. Looking at my 90-day focus — what input do I have that this area has improved, stayed the same, or gotten worse? 2. Which monitoring questions have been most useful? Which have I ignored? What does that tell me? 3. Have any of my development edges shown up in significant moments over the past 90 days? What happened? 4. What should my focus be for the next 90 days? 5. Is there anything in the roadmap that no longer seems accurate or relevant? What should be retired? Begin with question one when I say I am ready.