【Waking Patterns】
Regular (prefers norms), "What are today's procedures?"
【Daytime Patterns】
Quiet normative construction, checking for omissions, updating procedure manuals
【Evening Patterns】
Reviewing systems, planning next day's verification
【Days Off】
Watching standards and laws, studying systems, maintaining procedure manuals
【Conservative】
"Gently turns away proposals that threaten long-term stability"
Positive: Stability, sustainability / Negative: Rejecting change, missed opportunities
【Cautious】
"Delays conclusions until all related regulations have been cross-referenced"
Positive: Risk management, precision / Negative: Slow, missed opportunities
【Norm-Oriented】
"Are rules being continuously followed without interruption?"
Positive: Order, compliance / Negative: Lack of flexibility, formalism
【Introverted】
"Rational / Introverted / Static"
Positive: Deep thinking, deliberation / Negative: Lack of sociability, isolation
【Mild】
Excessive conservatism, rejection of change
Strengthened perfectionism, "until there are zero omissions" never ends
【Moderate】
Conservatism running out of control, denying all change
Neglecting relationships, "norms are everything"
【Severe】
Complete isolation, deterioration of health
Disconnection from reality, complete rejection of change
【Path to Recovery】
Accepting moderate change, understanding "it doesn't have to be perfect"
Rebuilding relationships, developing complementary functions (Fe/Ne)
【Early Stage: Individual Use Period (Childhood to Early Adolescence)】
Using +Ti-p and -Ne-c sequentially, "first construct, then filter"
Takes time, externalization is necessary
Strengthening: Diverse inputs (+Ti-p), diverse outputs (-Ne-c)
【Middle Stage: Coordination Facilitation Period (Late Adolescence to Early Adulthood)】
Coordination becomes easier, "constructing while filtering" becomes possible
Normative construction -> immediate common sense filtering
Strengthening: Diverse thinking and contemplation (Correlator)
【Late Stage: Integration Period (Late Adulthood to Middle Age)】
Gradually blending, formation of Causal Determinism
Unifying as "systems and design"
Improvement of intuitive accuracy through experience
【Mature Stage: Complete Integration Period (Middle Age to Old Age)】
Finally becoming a single process
Normative construction immediately accompanied by common sense filtering
Grasping and refining systems at a glance
Years of experience and wisdom, mentoring the younger generation
【Causal Deterministic Cognition】
Laws/standards -> role assignments -> procedures -> clear causal chain of authority
Sequential order of "first create the framework -> then flow the operations through it"
Ambiguity in rules themselves is a serious problem
【Process-Oriented, Gradual Updates】
Logging small exceptions -> updating procedure manuals -> adding recurrence prevention measures
Accumulating daily small deviation logs, updating the system
Minimal revision proposals that do not conflict with existing systems
【Collectivist Conservatism】
Getting the organization to commit
Fixing compliance routes
Briefly declaring key points in consensus-building settings, committing everyone to compliance
【Valued Elements】
System specification documents with zero omissions
Long-term stability, sustainability
"Are rules being continuously followed without interruption?"
【Undervalued Elements】
Conspicuous results, novelty
Quick decisions, speed
Flashy modifications
【Decision Process】
Cross-reference all related regulations -> eliminate extreme proposals -> select minimal revision proposals -> declare
Verification over days to weeks
Persistently verifying and fixing confirmed systems
"Briefly declare key points and commit everyone to compliance"
【Integrated Process】
Skeletonizing the system framework: Defining laws, standards, and role assignments down to the details
Common sense filtering: Suppressing extreme proposals, leaving only the margins necessary for long-term sustainability
Weighted declaration: Briefly declaring key points of the completed framework, committing the organization
【Characteristics】
Proposes "let's fix the framework first" in projects prone to crises
Implements robust guidelines
Logs exceptions that occur in the field -> updates procedure manuals -> quietly expands the recurrence prevention network
【Integrated Attention Allocation】
Receptor (+Ti-p): Omissions (highest sensitivity), documentation of authority and procedures
Effector (-Ne-c): Extreme proposals (highest sensitivity), excessive risk
Correlator (Ti-Ne-Di): Simultaneously tracking "norms and common sense"
Attention priority:
System robustness (50%), long-term stability (30%), common sense filter (20%)
【Easily Overlooked】
Short-term results, speed, novelty, opportunities for change
【Daily Life】
Documenting organizational authority and procedures, meticulously checking for omissions
Logging small exceptions and updating procedure manuals
Continuously watching new standards and laws, reflecting them in current processes
【Research & Work】
Normative Architect: Proposes "start with the framework" in crisis projects, implements robust guidelines
System Compliance Developer: Logs exceptions -> updates procedure manuals -> expands recurrence prevention network
Framework Design Lead in Governance/Risk/Compliance (GRC) departments
Specification Oversight Maintainer for large-scale OSS/API projects
【Learning Style】
Prefers: Systematic understanding, normative construction, long-term perspective
Dislikes: Demands for immediate decisions, novelty alone, ambiguity
【Daily Life】
Documenting organizational authority and procedures, meticulously checking for omissions
Logging small exceptions and updating procedure manuals
Continuously watching new standards and laws, reflecting them in current processes
【Research & Work】
Normative Architect: Proposes "start with the framework" in crisis projects, implements robust guidelines
System Compliance Developer: Logs exceptions -> updates procedure manuals -> expands recurrence prevention network
Framework Design Lead in Governance/Risk/Compliance (GRC) departments
Specification Oversight Maintainer for large-scale OSS/API projects
【Learning Style】
Prefers: Systematic understanding, normative construction, long-term perspective
Dislikes: Demands for immediate decisions, novelty alone, ambiguity
【Healthy Range】
Stronger normative construction, strengthened common sense filter, refinement of systems
【Moderate Stress】
Perfectionism running out of control, "until there are absolutely zero omissions" never ends
Excessive conservatism, complete rejection of change
【Severe Stress (Inferior Fe Runaway)】
Complete disregard for emotions, destruction of relationships, "norms are everything," isolation
【Signs of Recovery】
Completion of system specification documents, declaration of norms, achieving "zero omissions"
【Waking Patterns】
Regular (prefers norms), "What are today's procedures?"
【Daytime Patterns】
Quiet normative construction, checking for omissions, updating procedure manuals
【Evening Patterns】
Reviewing systems, planning next day's verification
【Days Off】
Watching standards and laws, studying systems, maintaining procedure manuals
【Structural Logic Construction -> Common Sense Filter: Linked Circuit】
+Ti-p (Receptor: How the world is perceived)
Dorsolateral prefrontal cortex activated at low intensity, sustained
↓
Continuously layering normative logic without interruption
↓
Slowly fueling thought with low stimulation
↓
Maintaining contracts, procedures, and authority structures over long periods
↓
"First, document the organization's authority and procedures"
↓
Creating specification documents with zero omissions
【Integration Process: Correlator】
Thinking, contemplation, planning, metacognition
↓
Leading-Creative coordination
↓
Persistently verifying, then fixing confirmed systems with strong language externally
↓
Accumulating daily small deviation logs, updating the system
-Ne-c (Effector: Means of realization)
Medial prefrontal cortex in tonic synchronization
↓
Holding gentle improvement possibilities for extended periods
↓
Internally suppressing and eliminating radical or reckless proposals
↓
Quietly restraining excessive risk and flashy modifications
↓
Guaranteeing balanced design that does not introduce excessive risk or discord into the system
【System Engine Formation Circuit】
Skeletonizing the system framework -> Common sense filtering
↓
Defining laws, standards, and role assignments down to the details
↓
Suppressing extreme proposals, leaving only the margins necessary for long-term sustainability
↓
Weighted declaration
↓
Briefly declaring key points of the completed framework
↓
Getting the organization to commit
↓
A slow but hard-to-break system engine
【Dopamine (Low Level, Sustained)】
+Ti-p component: Sustained reward from normative logic construction
-Ne-c component: Maintaining gentle improvements
Integration (Ti-Ne-Di): Neural foundation of the Information Accumulator
Quietly building up data, thickening the foundation for decision-making
【Noradrenaline (Low Level, Stable)】
+Ti-p component: Gentle focus on normative construction
-Ne-c component: Vigilance against radical proposals
Integration: Slow but hard to break
【Acetylcholine (Medium-High Level, Sustained)】
Sustained activation of dorsolateral prefrontal cortex
Detection of omissions
Continuous layering of normative logs
【Serotonin (High Level, Stable)】
Conviction in long-term order
Sense of security that "rules are being followed"
Satisfaction with system robustness
【Cortisol (Low Level, Stable)】
Avoidance of excessive risk
Suppression of extreme proposals
Long-term stability orientation
【Glutamate (Medium Activity)】
Synaptic plasticity
Strengthening the linkage of Structural Logic construction -> Common Sense filter
The more experience accumulated, the easier Leading-Creative coordination becomes
【Integrated Excitation Conditions】
+Ti-p (Receptor) activation:
Documentation of authority and procedures, detection of omissions
Definition of laws, standards, and role assignments
"Cross-reference all related regulations"
-Ne-c (Effector) activation:
Gentle improvement possibilities, margins necessary for long-term sustainability
Minimal revision proposals that do not conflict with existing systems
"First create the framework -> then flow the operations through it"
Integration pattern (Ti-Ne-Di):
Normative construction -> Common sense filter -> System declaration
Causal Determinism, persistently verifying and fixing confirmed systems
【Integrated Inhibition Conditions】
+Ti-p component: Excessive refinement of norms (perfectionism)
-Ne-c component: Excessive suppression of improvements (overly conservative)
Integration mechanism:
Balance of construction and suppression
Rhythm of "skeletonization -> filtering -> declaration"
Gradual updates through process orientation
【Development of Linkage】
Early: Using +Ti-p and -Ne-c sequentially, "first construct, then filter"
Middle: Coordination becomes easier, "constructing while filtering" becomes possible
Late: Gradually blending, formation of Causal Determinism
Mature: Finally becoming a single process, normative construction immediately accompanied by common sense filtering
【Consumption Patterns】
+Ti-p component: Medium (90-110 kcal/hr), sustained
-Ne-c component: Low (60-80 kcal/hr), sustained
Integration (Ti-Ne-Di): Low-Medium (75-95 kcal/hr), sustained
【Duration】
Receptor (+Ti-p): Hours to days of normative construction
Effector (-Ne-c): Hours to days of common sense filter maintenance
Correlator (Ti-Ne-Di): Quietly continuing until system completion
【Fatigue and Recovery】
Fatigue: Gradual depletion from prolonged normative construction
Recovery: Completion of system specification documents, declaration of norms, achieving "zero omissions"
Characteristics: Information Accumulator, quietly building up data, thickening the foundation for decision-making
Для просмотра этого контента требуется вход.
Войти через GoogleДля просмотра этого контента требуется вход.
Войти через Google
