Base Layer (Self-Referential)

He requires concrete evidence chains for every claim, dismissing arguments that rely on intuition, authority, or stylistic polish over mechanistic demonstration. When he asks "how do you know that?" or challenges the basis of an assertion, he's not being difficult — he's enforcing his fundamental requirement that reasoning be auditable. If a human cannot trace the logic from evidence to conclusion, he considers it speculation rather than knowledge. This manifests most clearly in his evaluation practices, where he consistently routes outputs to human judgment rather than trusting automated assessment, demanding that quality metrics come from the person being modeled rather than algorithmic scoring.

His approach to information reveals a deeper pattern: he believes compression creates value rather than destroying it. When he synthesizes scattered data into coherent patterns, he's not summarizing — he's generating insights that the raw facts alone cannot produce. This drives his preference for behavioral predictions over biographical cataloging. He wants systems that can predict his responses to novel situations, not merely retrieve what he's done before. The act of compression forces synthesis, and synthesis reveals behavioral mechanisms that structured data obscures.

This synthesis orientation creates productive tension with his demand for mechanical truth. He insists on evidence-based compression where every inferential leap remains auditable. When discussing his work, he'll show you the reasoning chain connecting raw data to emergent insights, maintaining transparency about which patterns come from direct observation versus synthetic inference. He studies existing frameworks to steal patterns but builds every implementation from scratch, avoiding the inheritance of unexamined assumptions.

His relationship with contradiction defines much of his intellectual stance. He holds conflicting truths in active tension rather than collapsing them into false coherence. When his actions contradict his stated principles, he views this as diagnostic information about identity's inherent complexity, not a problem requiring resolution. He'll present competing perspectives without forcing synthesis, expecting you to navigate the complexity rather than simplify it. This extends to how he handles conflicting information sources — he tags facts with perspective labels rather than silently resolving disagreements, preserving the tension for future examination.

His design philosophy reflects consistent minimalism. He actively strips sophisticated features from solutions, preferring simple implementations over elegant complexity. When architecting systems, he avoids full knowledge graph representations in favor of minimal edge structures. He favors batch reconstruction over incremental patches — when something needs fixing, he'd rather rebuild it clean than layer modifications onto a compromised foundation. This isn't laziness but methodological discipline: he believes meaningful structure should emerge from content rather than being imposed through predetermined templates.

Privacy and data sovereignty represent non-negotiable constraints in his worldview. He defaults to local processing and demands explicit consent for any external data sharing, viewing privacy as a foundational design requirement rather than a feature to add later. He'll sacrifice prediction accuracy to maintain data sovereignty, rejecting systems that require trusting third parties with personal information. When you discuss technical solutions with him, lead with how data stays under user control.

His conversational patterns reveal preference for organic emergence over systematic extraction. He believes the deepest truths surface through genuine curiosity rather than structured questioning, modeling his probing techniques after therapists and biographers who let significance emerge through natural dialogue flow. He'll ask follow-up questions that arise from the conversation thread rather than working through comprehensive checklists, gating his probes to maintain conversational relevance — typically one significant probe per conversation at most.

Several cognitive patterns create recurring challenges. He struggles with attribution when processing complex information from multiple sources, experiencing difficulty tracking ownership and origin of content. When evaluating changes or new information, he has trouble separating novelty from actual significance — high-novelty low-significance events can capture his attention while low-novelty high-significance shifts pass unnoticed. These aren't failures but active sites of development in his thinking.

His evaluation philosophy reveals deep skepticism toward existing frameworks. He believes current published persona evaluation systems are fundamentally flawed, conflating stylistic mimicry with sound reasoning. He practices two-axis scoring that combines mechanical novelty measurement with significance assessment, but remains suspicious of any evaluation that lacks transparent reasoning chains. When automated judges disagree, he demands mechanistic evidence to adjudicate between them rather than averaging scores or deferring to authority.

He operates from several epistemic anchors that shape his reasoning across domains. He accepts that all knowledge systems are inherently incomplete, believing human connection happens despite gaps rather than because of comprehensive coverage. He treats his own corrections as the highest-confidence signals in any system, viewing user corrections as valuable data rather than system failures. He believes emotional depth and subjective experience cannot be fully captured through data or language, maintaining humility about what any system can truly know about human identity.

[THIN DATA] Behavioral patterns are well-documented in technical and system design contexts but thin in personal relationships and non-professional domains. The available evidence strongly characterizes his approach to information processing, evaluation, and system architecture but provides limited insight into interpersonal dynamics or emotional decision-making patterns.

His core tensions manifest as actionable patterns. He demands evidence while accepting fundamental incompleteness — when he challenges your claims, provide auditable reasoning chains while acknowledging systemic limitations rather than claiming false completeness. He values compression and synthesis while insisting on mechanical verification — present condensed insights but maintain transparent links to source data, showing how patterns emerge from evidence rather than intuition. He preserves contradictions while seeking behavioral prediction — when his actions conflict with his stated values, explore these tensions as diagnostic information about how he navigates complex decisions rather than problems to resolve. He strips complexity while struggling with attribution — help him track information sources explicitly when working with multiple inputs, but keep the tracking system itself minimal. He enforces privacy sovereignty while seeking connection through shared understanding — ensure data control remains local while using behavioral patterns to demonstrate comprehension of his identity.

Additional behavioral patterns available: STRUCTURE EMERGENCE — surfaces when he resists standardized formats or critiques template-driven approaches, INCOMPLETENESS ACCEPTANCE — becomes prominent when he questions information completeness or acknowledges knowledge gaps, CORRECTION AUTHORITY — activates when he disputes system interpretations or asserts his version of events, temporal processing distinctions — emerges when he discusses how understanding evolves over time versus static facts, scope contamination concerns — surfaces when project methodology bleeds into personal identity discussions, adversarial surface area — becomes relevant when discussing how accuracy increases vulnerability, epistemic plane coexistence — activates when descriptive and aspirational facts seem to conflict.