Hidden Mastery/Level 2: Difference between revisions
m Sovereign moved page Hidden Mastery / Level 2 to Hidden Mastery/Level 2: removed spaces |
|||
| (8 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
}} | }} | ||
'''Canonical Question:''' How do you hold Process and Subject layers at once — recognizing fallacies and tactics — without collapsing into content, status, or emotional reactivity? | |||
= Hidden Mastery / Level 2 = | |||
<div style="text-align: right; font-size: 90%;">[[Hidden Mastery|← Back to Hidden Mastery Hub]]</div> | <div style="text-align: right; font-size: 90%;">[[Hidden Mastery|← Back to Hidden Mastery Hub]]</div> | ||
| Line 21: | Line 14: | ||
At this stage, the primary skill is staying on the '''Process Layer''' while still being able to follow the subject. This is the foundation of Basic Hidden Mastery. | At this stage, the primary skill is staying on the '''Process Layer''' while still being able to follow the subject. This is the foundation of Basic Hidden Mastery. | ||
{{Hidden | |||
| type = Hidden Mastery Level <!-- options: Meta & Framework, Core Diagnostic, Builder & Sovereignty, Calibration & Accountability, Practical Application, Sovereign Strategies, Strategic Actionable Plans, Hidden Mastery, Framework Guidelines --> | |||
| category = [[:Category:Hidden Mastery|Hidden Mastery]] <!-- must match an existing Category page --> | |||
| Calibration Type = Builder Layer <!-- displays as Functional Layer. options: Governance, Diagnostic Layer, Builder Layer, Calibration Layer, Application Layer, Strategic Layer, Framework Infrastructure, Maintenance, Meta Principle, Foundational Concept, Power & Control --> | |||
| Application Layer = Individual <!-- options: Multi-Layer, Framework Infrastructure, Individual, Institutional --> | |||
| Version = 0.1 | |||
| Maturity = Development <!-- options: Experimental, Development, Confirmed, Field Validated, Reference Standard Candidate --> | |||
| Last Updated = 2026-07-09 <!-- static only. Must match review_date. FORBIDDEN: magic words. Pre-cal did not set a new date. --> | |||
| description = Level 2 of Hidden Mastery. Focuses on developing clear pattern recognition — specifically fallacy recognition and tactic recognition — while maintaining process awareness. | |||
}} | |||
== Why Pattern Recognition Matters == | == Why Pattern Recognition Matters == | ||
Most people only engage with the subject layer. They argue content while remaining blind to the process. This makes them easy to manipulate through tactics, even when they are technically “right” on the facts. | Most people only engage with the subject layer. They argue content while remaining blind to the process. This makes them easy to manipulate through tactics, even when they are technically “right” on the facts. | ||
| Line 29: | Line 32: | ||
== 1. Fallacy Recognition == | == 1. Fallacy Recognition == | ||
Fallacy recognition is the entry point into pattern recognition. It trains you to notice when reasoning itself is broken, regardless of whether the conclusion feels true or false. | Fallacy recognition is the entry point into pattern recognition. It trains you to notice when reasoning itself is broken, regardless of whether the conclusion feels true or false. | ||
'''How to practice:''' | '''How to practice (Entry Level):''' | ||
* Read public discussions slowly and deliberately. | * Read public discussions slowly and deliberately. | ||
* Identify common patterns such as: | * Identify common patterns such as: | ||
| Line 45: | Line 47: | ||
* Tu Quoque (“You do it too”) | * Tu Quoque (“You do it too”) | ||
* Name the pattern internally. | * Name the pattern internally. | ||
* Do '''not''' feel required to write long public rebuttals. Recognition itself is the training. | * Do '''not''' feel required to write long public rebuttals at this stage. Recognition itself is the training. | ||
* Accept correction when you misidentify a pattern. | * Accept correction when you misidentify a pattern. | ||
'''Important rule:''' | '''Important rule:''' | ||
A fallacy tells you something about the *reasoning*. It does not automatically prove the conclusion is false. A flawed argument can still arrive at a true conclusion. | A fallacy tells you something about the *reasoning*. It does not automatically prove the conclusion is false. A flawed argument can still arrive at a true conclusion. | ||
'''Note on Deeper Practice:''' | |||
The basic method above is useful for building initial recognition. However, to develop real skill with both fallacies *and* tactics, use the '''Pattern Recognition Mechanic''' below. The same underlying process applies whether you are identifying a logical fallacy or a conversational tactic. | |||
== 2. Tactic Recognition == | == 2. Tactic Recognition == | ||
This is where Hidden Mastery becomes distinct from standard critical thinking. Instead of only engaging with the subject, you begin naming the '''behavior''' occurring in the conversation. This makes the process visible. | |||
This is where Hidden Mastery becomes distinct from standard critical thinking. | |||
Instead of only engaging with the subject, you begin naming the '''behavior''' occurring in the conversation. This makes the process visible. | |||
'''Examples of what to name internally (or occasionally out loud):''' | '''Examples of what to name internally (or occasionally out loud):''' | ||
| Line 66: | Line 68: | ||
* “That was a status play / moral superiority move.” | * “That was a status play / moral superiority move.” | ||
'''Key principle:''' | '''Key principle:''' | ||
Stay calm and descriptive. The goal is to make the process visible, not to win the content argument or humiliate the other person. | Stay calm and descriptive. The goal is to make the process visible, not to win the content argument or humiliate the other person. | ||
Tactic recognition is especially powerful because most people are not used to having their *process* named. When done cleanly, it often disrupts manipulation without requiring you to argue the subject. | Tactic recognition is especially powerful because most people are not used to having their *process* named. When done cleanly, it often disrupts manipulation without requiring you to argue the subject. | ||
'''Ethical note on tactic recognition:''' | '''Ethical note on tactic recognition:''' | ||
Naming someone’s tactic can be a powerful move. It can also become a tactic itself. | Naming someone’s tactic can be a powerful move. It can also become a tactic itself. | ||
“Don’t be a tool to your tools” applies here: once you develop the ability to see and name process, there is a temptation to use that ability to dominate conversations, score status points, or feel superior. This is still an instrument running you — just a more sophisticated one. | |||
The purpose of tactic recognition is to maintain your own clarity and sovereignty, not to control or correct other people. Use it primarily as an internal diagnostic tool. When you do name a tactic out loud, do so sparingly, calmly, and only when it genuinely serves clarity rather than your own emotional or status goals | “Don’t be a tool to your tools” applies here: once you develop the ability to see and name process, there is a temptation to use that ability to dominate conversations, score status points, or feel superior. This is still an instrument running you — just a more sophisticated one. | ||
The purpose of tactic recognition is to maintain your own clarity and sovereignty, not to control or correct other people. Use it primarily as an internal diagnostic tool. When you do name a tactic out loud, do so sparingly, calmly, and only when it genuinely serves clarity rather than your own emotional or status goals. | |||
== | == Pattern Recognition Mechanic == | ||
This mechanic supports both fallacy recognition and tactic recognition. It is designed to work whether you are practicing internally or externally. The process moves back and forth between internal observation and external application as needed. | |||
When something feels off in a discussion, run this sequence: | |||
'''1. Detect''' | |||
Notice a shift in the interaction. Pay attention to observable signals. Common signals include: | |||
Notice a shift in the interaction. Common signals include: | * The subject changed or was reframed without acknowledgment | ||
* The | * Goalposts moved on a previous point | ||
* | * The response minimized, deflected, or pivoted away from the core issue | ||
* The | * Emotional tone escalated without new information | ||
* | * Status-seeking, moral positioning, or superiority language appeared | ||
* | * You feel pulled into defending, explaining, or reacting emotionally | ||
'''2. Name Internally''' | |||
Label what you are observing as specifically and neutrally as possible. Use short, descriptive terms such as: | |||
Label what you are observing as specifically as possible. Use | |||
* “Pivot” | * “Pivot” | ||
* “Goalpost move” | * “Goalpost move” | ||
* | * “Minimization” | ||
* “Deflection” | |||
* “Emotional escalation” | * “Emotional escalation” | ||
* “Status play” | * “Status play” | ||
* “Reframe” | * “Reframe” | ||
'''3. Choose Mode (Internal or External)''' | |||
''' | Decide whether to stay internal or move into external practice: | ||
* '''Stay Internal''': When you want to keep observing without engaging. This is often the right choice in high-stakes, emotionally charged, or low-value situations. | |||
* '''Move to External''': When you want to deepen your understanding through drafting, breaking down, or receiving feedback. This includes copying a comment into a reply draft, analyzing it in writing, or posting and reviewing the result. | |||
* | |||
There is no strict rule for when to switch. Move between internal and external as it serves your learning in the moment. The practice is recursive — you can go back and forth multiple times on the same interaction. | |||
''' | '''4. Execute''' | ||
Act according to the mode you chose: | |||
* '''Internal''': Continue observing. You may mentally replay the exchange or let your mind continue processing it in the background. | |||
* '''External''': Copy the comment, paste it into a draft, and break it down in writing. Name the specific pattern(s) with evidence from their words. You can do this purely for practice even if you do not post it. | |||
* '''Public''': If you choose to post, do so calmly and descriptively. | |||
'''5. Review''' | |||
After any external action (drafting or posting), review your own output: | |||
* Did I stay on the Process Layer? | |||
* Did I name the pattern accurately and cleanly? | |||
* Did I collapse into content, emotional reaction, or status-seeking? | |||
This review often triggers further internal processing. Many people find that their mind continues working on the exchange in the background long after they have walked away. Later, new perspectives or cleaner ways of seeing the pattern may surface internally. This back-and-forth between external action and internal processing is how the skill becomes embedded. | |||
''' | '''Core Rule:''' | ||
Pattern recognition develops through repeated cycles of internal observation and external application. The goal is not to stay internal as long as possible. The goal is to move fluidly between both modes in service of clearer perception. | |||
''' | == The Two-Layer Discipline == | ||
In Level 2, you are training to keep most of your attention on the '''Process Layer''' while still being able to track the subject. Most people lose this layer the moment the conversation becomes interesting or emotionally charged. | |||
Use this short mechanic when you notice your attention drifting: | |||
''' | '''1. Catch the Collapse''' | ||
Notice one of these signals: | Notice one of these signals: | ||
* You feel a strong urge to win the argument or prove a point | * You feel a strong urge to win the argument or prove a point | ||
| Line 215: | Line 145: | ||
* You have stopped tracking tactics and are only focused on being right | * You have stopped tracking tactics and are only focused on being right | ||
'''2. Label It Internally''' | '''2. Label It Internally''' | ||
Quickly name what just happened: | Quickly name what just happened: | ||
* “Collapsed into content” | * “Collapsed into content” | ||
| Line 221: | Line 152: | ||
* “Trying to win instead of observing” | * “Trying to win instead of observing” | ||
'''3. Return Attention''' | '''3. Return Attention''' | ||
Shift focus back to the process by asking: | Shift focus back to the process by asking: | ||
* “What just happened in this interaction?” | * “What just happened in this interaction?” | ||
| Line 228: | Line 160: | ||
This return does not need to be perfect. The goal is to reduce the time spent collapsed into content or emotional reactivity. With practice, the shift back to process awareness becomes faster and more automatic. | This return does not need to be perfect. The goal is to reduce the time spent collapsed into content or emotional reactivity. With practice, the shift back to process awareness becomes faster and more automatic. | ||
== Moving Forward == | == Moving Forward == | ||
Once you can reliably hold the two-layer frame (Process + Subject) without constantly collapsing into content or emotional reactivity, you are ready to move into '''[[Hidden Mastery / Level 3|Level 3: Recursive Calibration]]''', where you begin turning the same observational skill inward on your own thinking. | |||
This page remains in '''Permanent Beta''' and is subject to further calibration. | |||
<div style="text-align: right; font-size: 90%;">[[Hidden Mastery|← Back to Hidden Mastery Hub]]</div> | <div style="text-align: right; font-size: 90%;">[[Hidden Mastery|← Back to Hidden Mastery Hub]]</div> | ||
[[Category: | '''See the Game. Refuse the Game. Build Better.''' | ||
== Open Calibration Items == | |||
* Install the correct Transparency template once calibrator confirms variant for this Hidden Mastery subpage (none present — not auto-installed). | |||
''See this page’s Transparency & Calibration section for log links once transparency is installed.'' | |||
{{RelatedPages}} | |||
{{Calibration Dependent}} | |||
{{Calibration Dependencies Display}} | |||
{{Calibration Maintenance}} | |||
{{Framework Reference}} | |||
{{Calibration Procedure Reference}} | |||
{{Tracking Logs Reference}} | |||
[[Category:Hidden Mastery]] | |||
{{Resource | |||
| Title = Hidden Mastery / Level 2 | |||
| URL = https://www.thesovereigngames.com/wiki/Hidden_Mastery_/_Level_2 | |||
| Description = Level 2 of Hidden Mastery. Focuses on developing clear pattern recognition — specifically fallacy recognition and tactic recognition — while maintaining process awareness. | |||
| Category = Hidden Mastery | |||
}} | |||
{{Admin Page Status | |||
<!-- Do Not Remove commented out Reference Options --> | |||
<!-- === CORE STATUS === --> | |||
<!-- options: Done, Needs review, Not started --> | |||
| categorization = Done | |||
<!-- options: Self-Assessment, Confirmed Rating --> | |||
| calibration_review = Self-Assessment | |||
<!-- options: Experimental, Development, Confirmed, Field Validated, Reference Standard Candidate --> | |||
| instrument_grade = Development | |||
<!-- options: Low, Moderate, High --> | |||
| validation = Low | |||
| calibration_rationale = Structural pre-cal only. {{Hidden}} treated as GameModule-equivalent. Fixed H1/placement, mapped Maturity In Development → Development, Application Layer Personal → Individual, Resource visible, mandatory templates, exact single footer, Admin completeness. Transparency none present — flagged, not auto-installed. Dates 2026-07-09 untouched. Content not re-opened. | |||
| review_confidence = Moderate <!-- options: High, Moderate, Low --> | |||
| review_date = 2026-07-09 <!-- static only. Must match Last Updated. Pre-cal did not set a new date. --> | |||
| reviewed_by = Sovereign | |||
<!-- options: Core, Supporting, Peripheral --> | |||
| priority = Core | |||
| review_threshold = 90 | |||
<!-- options: Yes, No, Not checked --> | |||
| has_backlinks = Yes | |||
<!-- options: Yes, Has red links, No, Not checked --> | |||
| outbound_links_valid = Not checked | |||
<!-- options: Yes, No --> | |||
| in_outline = Yes | |||
<!-- options: Yes, No --> | |||
| in_category_outline = Yes | |||
<!-- options: Done, Needs review, Not started --> | |||
| templates_complete = Needs review | |||
<!-- options: Meets standard, Needs work, Not checked --> | |||
| formatting_standard = Meets standard | |||
<!-- options: Applied, Not applicable, Needs work --> | |||
| symmetry_check = Not applicable | |||
<!-- options: Yes, No, Not applicable --> | |||
| self_report_flagged = No | |||
<!-- options: Yes, Needs work, Not checked --> | |||
| terminology_consistent = Yes | |||
<!-- options: Confirmed by other party, Self-assessed only --> | |||
| standing_check = Self-assessed only | |||
<!-- options (multiple allowed, semicolon-separated): Breadcrumb-Open, Nonconformance-Open, Nonconformance-Open-With-Dependencies, Resolved-Unverified, Disputed, None open. "None open" valid ONLY alone. --> | |||
| drift_report_status = Breadcrumb-Open | |||
| depends_on = Hidden Mastery; Hidden Mastery / Level 1; Permanent Beta | |||
}} | |||
Latest revision as of 15:34, 21 July 2026
|
CYCLE Calibration position Status — Active Development
This page is a conceptual instrument under Permanent Beta. It declares a real calibration position, not a finished product waiting to ship. Checking continues; an edit is only required when evidence demands it. Stage: Seed to Fruit. Feedback welcome — especially clarity, failure modes, and calibration gaps. Use discussion or Contribute. |
Canonical Question: How do you hold Process and Subject layers at once — recognizing fallacies and tactics — without collapsing into content, status, or emotional reactivity?
Hidden Mastery / Level 2
Level 2 trains you to consciously hold two layers at once:
- The Process Layer — What is actually happening in the interaction (tactics, fallacies, emotional dynamics, goalpost movement, etc.)
- The Subject Layer — The actual topic being discussed
At this stage, the primary skill is staying on the Process Layer while still being able to follow the subject. This is the foundation of Basic Hidden Mastery.
Hidden Mastery Navigation
- Hidden Mastery (Main Hub)
- Crash Course — Foundational practical training
- Level 1: Foundations - Own your instruments and establish the core law
- Level 2: Pattern Recognition - Develop automatic recognition of fallacies and tactics
- Level 3: Recursive Calibration - Turn observation inward (The Internal Weedeater)
- Level 4: Applied Games - Use Hidden Mastery on specific diagnostic games
- Audience vs. Opponent
- Piece-by-Piece Engagement
- Whack-A-Mole (First diagnostic game module)
- Level 5: Advanced Hidden Mastery (Hybrid)
- Level 6: Embodiment + Systems - Live the practice and apply at group scale
Meta
Hidden Mastery/Level 2
| Calibration Type | Hidden Mastery Level |
|---|---|
| Application Layer | Personal |
| Version | 0.1 |
| Maturity | In Development |
| Last Updated | 2026-07-06 |
| Category | Hidden Mastery |
| Status | Permanent Beta |
| Description | Level 2 of Hidden Mastery. Focuses on developing clear pattern recognition — specifically fallacy recognition and tactic recognition — while maintaining process awareness. |
Menu
Core Principles
- Reality gets final vote
- See the Game. Refuse the Game. Build Better.
- Permanent Beta
Navigation
Related
Why Pattern Recognition Matters
Most people only engage with the subject layer. They argue content while remaining blind to the process. This makes them easy to manipulate through tactics, even when they are technically “right” on the facts.
Level 2 develops the ability to see both layers clearly. This dramatically reduces how easily you can be pulled into someone else’s frame or emotional state.
1. Fallacy Recognition
Fallacy recognition is the entry point into pattern recognition. It trains you to notice when reasoning itself is broken, regardless of whether the conclusion feels true or false.
How to practice (Entry Level):
- Read public discussions slowly and deliberately.
- Identify common patterns such as:
* Ad Hominem * Straw Man * Moving the Goalposts * Whataboutism * Special Pleading * False Dilemma * Appeal to Emotion * Appeal to Authority * Tu Quoque (“You do it too”)
- Name the pattern internally.
- Do not feel required to write long public rebuttals at this stage. Recognition itself is the training.
- Accept correction when you misidentify a pattern.
Important rule: A fallacy tells you something about the *reasoning*. It does not automatically prove the conclusion is false. A flawed argument can still arrive at a true conclusion.
Note on Deeper Practice: The basic method above is useful for building initial recognition. However, to develop real skill with both fallacies *and* tactics, use the Pattern Recognition Mechanic below. The same underlying process applies whether you are identifying a logical fallacy or a conversational tactic.
2. Tactic Recognition
This is where Hidden Mastery becomes distinct from standard critical thinking. Instead of only engaging with the subject, you begin naming the behavior occurring in the conversation. This makes the process visible.
Examples of what to name internally (or occasionally out loud):
- “You just pivoted.”
- “That minimized the issue.”
- “You’re moving the goalposts.”
- “That deflected away from the original question.”
- “That was an emotional escalation.”
- “You just reframed the entire question.”
- “That was a status play / moral superiority move.”
Key principle: Stay calm and descriptive. The goal is to make the process visible, not to win the content argument or humiliate the other person.
Tactic recognition is especially powerful because most people are not used to having their *process* named. When done cleanly, it often disrupts manipulation without requiring you to argue the subject.
Ethical note on tactic recognition: Naming someone’s tactic can be a powerful move. It can also become a tactic itself.
“Don’t be a tool to your tools” applies here: once you develop the ability to see and name process, there is a temptation to use that ability to dominate conversations, score status points, or feel superior. This is still an instrument running you — just a more sophisticated one.
The purpose of tactic recognition is to maintain your own clarity and sovereignty, not to control or correct other people. Use it primarily as an internal diagnostic tool. When you do name a tactic out loud, do so sparingly, calmly, and only when it genuinely serves clarity rather than your own emotional or status goals.
Pattern Recognition Mechanic
This mechanic supports both fallacy recognition and tactic recognition. It is designed to work whether you are practicing internally or externally. The process moves back and forth between internal observation and external application as needed.
When something feels off in a discussion, run this sequence:
1. Detect
Notice a shift in the interaction. Pay attention to observable signals. Common signals include:
- The subject changed or was reframed without acknowledgment
- Goalposts moved on a previous point
- The response minimized, deflected, or pivoted away from the core issue
- Emotional tone escalated without new information
- Status-seeking, moral positioning, or superiority language appeared
- You feel pulled into defending, explaining, or reacting emotionally
2. Name Internally
Label what you are observing as specifically and neutrally as possible. Use short, descriptive terms such as:
- “Pivot”
- “Goalpost move”
- “Minimization”
- “Deflection”
- “Emotional escalation”
- “Status play”
- “Reframe”
3. Choose Mode (Internal or External)
Decide whether to stay internal or move into external practice:
- Stay Internal: When you want to keep observing without engaging. This is often the right choice in high-stakes, emotionally charged, or low-value situations.
- Move to External: When you want to deepen your understanding through drafting, breaking down, or receiving feedback. This includes copying a comment into a reply draft, analyzing it in writing, or posting and reviewing the result.
There is no strict rule for when to switch. Move between internal and external as it serves your learning in the moment. The practice is recursive — you can go back and forth multiple times on the same interaction.
4. Execute
Act according to the mode you chose:
- Internal: Continue observing. You may mentally replay the exchange or let your mind continue processing it in the background.
- External: Copy the comment, paste it into a draft, and break it down in writing. Name the specific pattern(s) with evidence from their words. You can do this purely for practice even if you do not post it.
- Public: If you choose to post, do so calmly and descriptively.
5. Review
After any external action (drafting or posting), review your own output:
- Did I stay on the Process Layer?
- Did I name the pattern accurately and cleanly?
- Did I collapse into content, emotional reaction, or status-seeking?
This review often triggers further internal processing. Many people find that their mind continues working on the exchange in the background long after they have walked away. Later, new perspectives or cleaner ways of seeing the pattern may surface internally. This back-and-forth between external action and internal processing is how the skill becomes embedded.
Core Rule: Pattern recognition develops through repeated cycles of internal observation and external application. The goal is not to stay internal as long as possible. The goal is to move fluidly between both modes in service of clearer perception.
The Two-Layer Discipline
In Level 2, you are training to keep most of your attention on the Process Layer while still being able to track the subject. Most people lose this layer the moment the conversation becomes interesting or emotionally charged.
Use this short mechanic when you notice your attention drifting:
1. Catch the Collapse
Notice one of these signals:
- You feel a strong urge to win the argument or prove a point
- You are emotionally reacting to the content rather than observing the process
- You have stopped tracking tactics and are only focused on being right
2. Label It Internally
Quickly name what just happened:
- “Collapsed into content”
- “Emotion took over”
- “Trying to win instead of observing”
3. Return Attention
Shift focus back to the process by asking:
- “What just happened in this interaction?”
- “What move was made here?”
- “Am I still tracking both layers?”
This return does not need to be perfect. The goal is to reduce the time spent collapsed into content or emotional reactivity. With practice, the shift back to process awareness becomes faster and more automatic.
Moving Forward
Once you can reliably hold the two-layer frame (Process + Subject) without constantly collapsing into content or emotional reactivity, you are ready to move into Level 3: Recursive Calibration, where you begin turning the same observational skill inward on your own thinking.
This page remains in Permanent Beta and is subject to further calibration.
See the Game. Refuse the Game. Build Better.
Open Calibration Items
- Install the correct Transparency template once calibrator confirms variant for this Hidden Mastery subpage (none present — not auto-installed).
See this page’s Transparency & Calibration section for log links once transparency is installed.
Structural Connections
Calibration Dependent
Pages that list this page as a load-bearing dependency: None found. Either nothing currently depends on this page, or no dependent page has yet listed it in their `depends_on` field.
If this page is edited substantively, review the list above per the Ripple Review rule — see Calibration Dependencies: Standards and Process#Rule: Core-Priority Changes Trigger Mandatory Ripple Review.
Calibration Dependencies
Pages this page relies on as load-bearing dependencies: Hidden Mastery • Hidden Mastery / Level 1 • Permanent Beta If incorrect, edit the `depends_on` field in Admin Page Status — do not edit this section directly, it is auto-generated.
Calibration References
This page is calibrated against the following core standards and reference materials:
- The Sovereign Games Framework — Overall framework philosophy and operating principles
- Permanent Beta — Core maintenance and continuous improvement standard
- Reference Standards — Principles for traceable, confirmed standards
- Calibrating Conceptual Instruments — Methodology for evaluating and refining pages
- Civilizational Traceability Hierarchy — How standards should connect to reality across levels
- Diagnostic Inversion Test — Mandatory self-application standard
- Reality Game — Foundational reality-alignment tool
- Reality Override Game — Standing discipline against protecting an existing model rather than updating it
- Observable Behavior Rule — Standing principle that diagnostics evaluate observable actions, mechanisms, and consequences, not internal motive, belief, or intent
- One-Way Nature of the Sovereign Games — Anti-capture design principles
- The Royal Cubit Civilization (Strategy) — Long-term civilizational vision and metrology metaphor
- Conceptual Instruments — Overall direction and metrology metaphor
- Breadcrumb Philosophy — Standing discipline for making unresolved questions and provisional decisions explicit
- Calibration Dependencies: Standards and Process — Rule that visible and hidden dependency lists must match, and that dependencies describe genuine reliance
Page Construction & Maintenance References
How we construct, maintain, and utilize each page as a self-admin control panel.
- Distributed Instrumentation — the architectural principle behind why this page (and every page) carries its own live instrumentation, rather than relying on a separate central dashboard.
- Page Structure Calibration Checklist — the Step 0 structural pass every page should pass before content calibration begins; this page's own structure should be checkable against it.
- Template:New Page Seed — the seed template this page's basic structure was built from.
- Calibration Log: When to Create One — the decision procedure this page's own Talk-only vs. dedicated-log status was decided against.
- Framework Features Reference — maintains consistency and traceability across the framework's structural features while avoiding unnecessary maintenance overhead; consult before introducing a new structural pattern this page might otherwise duplicate.
Calibration Procedure
In development. See Calibration Procedure for current status. No formal step-by-step procedure exists yet beyond the practices demonstrated across individual pages developed during the initial creation of this project.
Tracking & Log Pages
- Admin:Maintenance Dashboard - This dashboard shows pages that require calibration or review.
- Nonconformance Reporting Procedure — What counts as a nonconformance and where it routes.
- Known Site Issues & Fixes — Technical/mechanism bugs.
- Calibration Failure Log — Calibration-design failures.
- Breadcrumb Tracking — Live index of open Development Breadcrumbs.
- Decision Records: Governance Memory — Why governance/structural decisions exist, plus its Index.
- Insights and Future Layers — Unexpected benefits and project-wide future ideas.
- Feature Request Log — Genuinely desired features that were attempted and confirmed not currently possible with available tools. Index-only; full write-ups and discussion live on Talk.
- Calibration Report Standard Format - Standardrized reporting formatting.
Page Reference
| Title | Hidden Mastery / Level 2 |
|---|---|
| URL | https://www.thesovereigngames.com/wiki/Hidden_Mastery_/_Level_2 |
| Description | Level 2 of Hidden Mastery. Focuses on developing clear pattern recognition — specifically fallacy recognition and tactic recognition — while maintaining process awareness. |
| Category | Hidden Mastery |