cbrowser 18.63.0 → 18.63.2

package/docs/traits/Trait-MentalModelRigidity.md

@@ -1,228 +0,0 @@
-> **This documentation is no longer maintained here.**
->
-> For the latest version, please visit: **[Mental Model Rigidity](https://cbrowser.ai/docs/Trait-MentalModelRigidity)**
-
----
-
-# Mental Model Rigidity
-
-**Category**: Tier 5 - Perception Traits
-**Scale**: 0.0 (highly flexible) to 1.0 (highly rigid)
-
-## Definition
-
-Mental Model Rigidity describes the degree to which users resist updating their internal representations of how systems work when confronted with contradictory evidence. In web and UI contexts, this trait determines how quickly users adapt to interface changes, redesigns, or unexpected behaviors. Users with high mental model rigidity persist in applying outdated interaction patterns, require multiple disconfirming experiences before adjusting their approach, and experience significant frustration when interfaces deviate from their expectations. Users with low rigidity rapidly incorporate new information and adapt their behavior to match current system states.
-
-## Research Foundation
-
-### Primary Citation
-
-> "Mental models are working models that are constructed from knowledge, perception, and inference. People reason by mentally manipulating these models to simulate possible states of affairs. The more deeply entrenched a model, the more evidence is required to revise or abandon it."
-> — Johnson-Laird, P. N., 1983, p. 397
-
-**Full Citation (APA 7):**
-Johnson-Laird, P. N. (1983). *Mental models: Towards a cognitive science of language, inference, and consciousness*. Harvard University Press.
-
-**ISBN**: 978-0674568815
-
-### Supporting Research
-
-> "Users who have developed strong expectations about interface behavior require an average of 3-5 disconfirming experiences before updating their mental model of how the system operates."
-> — Carroll, J. M., & Rosson, M. B., 1987, p. 86
-
-**Full Citation (APA 7):**
-Carroll, J. M., & Rosson, M. B. (1987). Paradox of the active user. In J. M. Carroll (Ed.), *Interfacing thought: Cognitive aspects of human-computer interaction* (pp. 80-111). MIT Press.
-
-**ISBN**: 978-0262530637
-
-### Key Numerical Values
-
-| Metric | Value | Source |
-|--------|-------|--------|
-| Disconfirmations needed to update model | 3-5 experiences | Carroll & Rosson (1987) |
-| Mental model formation time | 2-4 interactions | Norman (1983) |
-| Relearning cost after redesign | 40-60% productivity loss initially | Nielsen (2010) |
-| Interface change adaptation period | 1-3 weeks for major changes | Sears & Jacko (2007) |
-| Error rate post-redesign | 300-400% increase initially | Tognazzini (2003) |
-| Working memory chunks for model | 3-4 active elements | Johnson-Laird (1983) |
-| Model revision resistance | 65% persist despite single failure | Rouse & Morris (1986) |
-
-## Behavioral Levels
-
-| Value | Label | Behaviors |
-|-------|-------|-----------|
-| 0.0-0.2 | Very Flexible | Immediately adapts to interface changes; updates expectations after single disconfirming event; explores new features without prior assumptions; recovers quickly from errors by trying alternative approaches; embraces redesigns without complaint; treats each interaction as learning opportunity |
-| 0.2-0.4 | Flexible | Adapts to changes within 2-3 disconfirming experiences; initially tries familiar patterns but quickly pivots; shows mild surprise at interface changes but adjusts; willing to read help content for new features; accepts redesigns after brief acclimation period; experiments with different approaches when blocked |
-| 0.4-0.6 | Moderate | Requires 3-4 disconfirming experiences to update model; shows visible frustration when familiar patterns fail; attempts old methods repeatedly before adapting; may vocalize "this used to work"; moderate resistance to redesigns; eventually adapts but with notable effort and time |
-| 0.6-0.8 | Rigid | Persists with outdated patterns through 5-6 failures; expresses strong frustration with interface changes; repeatedly clicks where buttons "should be" based on prior experience; blames system for not working "correctly"; strong resistance to redesigns; may seek workarounds to maintain old patterns; frequently requests "old version" |
-| 0.8-1.0 | Very Rigid | Requires 7+ disconfirming experiences before considering model update; intense frustration and potential abandonment when patterns fail; refuses to acknowledge interface has changed; persistent muscle-memory errors; may avoid features that have been redesigned; seeks external help rather than exploring; considers any change "broken"; may switch to competitor products to maintain familiar patterns |
-
-## Web/UI Manifestations
-
-### Common Scenarios Where Mental Model Rigidity Affects Users
-
-**Navigation Redesigns**
-- User clicks where navigation menu used to be after site redesign
-- Expects dropdown behavior but encounters mega-menu
-- Seeks hamburger menu on desktop after mobile experience
-- Looks for footer links in header after site reorganization
-
-**Form Interaction Patterns**
-- Expects Tab key to advance fields but interface uses Enter
-- Assumes clicking submit saves draft (prior experience) but it doesn't
-- Expects date picker but encounters free-form text field
-- Assumes asterisk means optional (prior app) when it means required
-
-**E-commerce Flows**
-- Expects "Add to Cart" in product image area after pattern change
-- Looks for cart icon in top-right after redesign moved it left
-- Assumes checkout is multi-page when now single-page
-- Expects shipping address before payment (old flow was reversed)
-
-**Modal and Dialog Patterns**
-- Clicks outside modal expecting dismissal when it requires button click
-- Expects "X" in top-right when close button is bottom-left
-- Assumes Escape key closes modal when it doesn't
-- Expects confirmation on dialog but action is immediate
-
-**Search Behavior**
-- Uses search syntax from prior interface that doesn't work here
-- Expects autocomplete but interface requires explicit submit
-- Assumes search scope is entire site when it's section-specific
-- Expects results page but gets inline dropdown suggestions
-
-**Authentication Patterns**
-- Enters username then password, but interface asks email first
-- Expects "Remember me" checkbox that doesn't exist
-- Looks for social login options in different position
-- Assumes password visible toggle is checkbox when it's icon
-
-## Estimated Trait Correlations
-
-> *Correlation estimates are derived from related research findings and theoretical models. Empirical calibration is planned ([GitHub #95](https://github.com/alexandriashai/cbrowser/issues/95)).*
-
-| Related Trait | Correlation | Mechanism |
-|---------------|-------------|-----------|
-| Transfer Learning | r = -0.55 | High transfer learning enables rapid model updates |
-| Procedural Fluency | r = 0.42 | Automated procedures increase rigidity |
-| Patience | r = -0.35 | Impatient users less willing to persist through model updates |
-| Persistence | r = 0.38 | Highly persistent users may over-persist with wrong model |
-| Self-Efficacy | r = -0.28 | Low self-efficacy increases defensive rigidity |
-| Curiosity | r = -0.45 | Curious users more willing to explore new patterns |
-
-## The Model Update Process
-
-### Stages of Mental Model Revision
-
-1. **Initial Failure**: Expected action produces unexpected result
-2. **Retry Phase**: User attempts same action with minor variations
-3. **Frustration Point**: After 2-3 failures, emotional response emerges
-4. **Exploration Phase**: Begins trying alternative approaches
-5. **Insight Moment**: Discovers correct pattern
-6. **Integration**: New pattern begins overwriting old model
-7. **Consolidation**: 5-10 successful repetitions cement new model
-
-### Factors Affecting Update Speed
-
-| Factor | Effect on Rigidity |
-|--------|-------------------|
-| Prior experience depth | More experience = more rigid |
-| Time since last use | Longer gap = more flexible |
-| Emotional investment | Higher investment = more rigid |
-| Similarity to old pattern | More similar = harder to distinguish |
-| Explicit instruction | Direct teaching accelerates update |
-| Multiple simultaneous changes | Increases update difficulty |
-
-## Design Implications
-
-### For High Mental Model Rigidity Users
-
-- Provide transitional interfaces during redesigns
-- Implement "bridge" patterns that honor old and new behaviors
-- Add prominent "What's New" tours for redesigns
-- Maintain familiar anchor points in new designs
-- Use animation to show where elements moved
-- Provide search for features ("Where is Cart?")
-- Allow "classic mode" during transition periods
-- Use progressive disclosure for major changes
-- Add inline hints for changed behaviors
-- Implement ghost images showing old element locations
-
-### For Low Mental Model Rigidity Users
-
-- Can deploy redesigns with minimal onboarding
-- Brief changelog notifications sufficient
-- Will discover changes through exploration
-- Requires less hand-holding during transitions
-
-## Persona Values
-
-| Persona | Value | Rationale |
-|---------|-------|-----------|
-| Rushing Rachel | 0.55 | Time pressure discourages exploration, increases reliance on habits |
-| Careful Carlos | 0.65 | Methodical patterns become entrenched through repeated verification |
-| Distracted Dave | 0.45 | Distractibility prevents deep model formation, enabling flexibility |
-| Senior Sam | 0.80 | Long experience creates deeply entrenched expectations |
-| Focused Fiona | 0.50 | Deep task focus creates strong models but allows analytical updates |
-| Anxious Annie | 0.70 | Anxiety drives preference for predictable, familiar patterns |
-| Mobile Mike | 0.40 | Diverse app experiences create flexible cross-platform expectations |
-| Power User Pete | 0.60 | Expert patterns are efficient but resistant to change |
-| First-Time Freddie | 0.20 | No prior experience means no rigid expectations |
-
-## Measurement Approaches
-
-### Experimental Paradigms
-
-1. **Interface modification studies**: Measure errors after interface change
-2. **Transfer tasks**: Test performance on new version of familiar system
-3. **Think-aloud protocols**: Capture explicit expectations during exploration
-4. **Error recovery analysis**: Time and attempts to recover from model mismatch
-
-### Web-Specific Metrics
-
-- Click heatmap comparison before/after redesign
-- Error rate spike duration after changes
-- Time to first successful task completion post-change
-- Support ticket volume after interface updates
-- A/B test showing new vs. maintained patterns
-
-## Interaction with Change Blindness
-
-Mental Model Rigidity and [Change Blindness](./Trait-ChangeBlindness.md) interact in complex ways:
-
-| Scenario | High Rigidity + High Blindness | High Rigidity + Low Blindness |
-|----------|-------------------------------|------------------------------|
-| UI Redesign | May not notice changes AND struggle when discovered | Notices changes immediately, resists adapting |
-| Error states | Misses error AND repeats same action | Notices error but persists with failed approach |
-| New features | Overlooks new options AND wouldn't use them | Sees new features but avoids them |
-
-## See Also
-
-- [Change Blindness](./Trait-ChangeBlindness.md) - Related perceptual limitation
-- [Transfer Learning](./Trait-TransferLearning.md) - Ability to apply knowledge across contexts
-- [Procedural Fluency](./Trait-ProceduralFluency.md) - Automated interaction patterns
-- [Persistence](./Trait-Persistence.md) - Continuing despite obstacles
-- [Trait Index](./Trait-Index.md) - Complete trait listing
-- [Senior Sam](../personas/Persona-SeniorSam) - High rigidity persona
-
-## Bibliography
-
-Carroll, J. M., & Rosson, M. B. (1987). Paradox of the active user. In J. M. Carroll (Ed.), *Interfacing thought: Cognitive aspects of human-computer interaction* (pp. 80-111). MIT Press.
-
-Gentner, D., & Stevens, A. L. (Eds.). (1983). *Mental models*. Lawrence Erlbaum Associates.
-
-Johnson-Laird, P. N. (1983). *Mental models: Towards a cognitive science of language, inference, and consciousness*. Harvard University Press.
-
-Nielsen, J. (2010). Website response times. *Nielsen Norman Group*. https://www.nngroup.com/articles/website-response-times/
-
-Norman, D. A. (1983). Some observations on mental models. In D. Gentner & A. L. Stevens (Eds.), *Mental models* (pp. 7-14). Lawrence Erlbaum Associates.
-
-Norman, D. A. (2013). *The design of everyday things* (Revised and expanded ed.). Basic Books.
-
-Rouse, W. B., & Morris, N. M. (1986). On looking into the black box: Prospects and limits in the search for mental models. *Psychological Bulletin*, 100(3), 349-363. https://doi.org/10.1037/0033-2909.100.3.349
-
-Sears, A., & Jacko, J. A. (Eds.). (2007). *The human-computer interaction handbook: Fundamentals, evolving technologies and emerging applications* (2nd ed.). CRC Press.
-
-Tognazzini, B. (2003). First principles of interaction design. *AskTog*. https://asktog.com/atc/principles-of-interaction-design/
-
-Young, R. M. (1983). Surrogates and mappings: Two kinds of conceptual models for interactive devices. In D. Gentner & A. L. Stevens (Eds.), *Mental models* (pp. 35-52). Lawrence Erlbaum Associates.

package/docs/traits/Trait-MetacognitivePlanning.md

@@ -1,164 +0,0 @@
-> **This documentation is no longer maintained here.**
->
-> For the latest version, please visit: **[Metacognitive Planning](https://cbrowser.ai/docs/Trait-MetacognitivePlanning)**
-
----
-
-# Metacognitive Planning
-
-**Category**: Tier 4 - Planning Traits
-**Scale**: 0.0 (low) to 1.0 (high)
-
-## Definition
-
-Metacognitive Planning measures a user's ability to think about their own thinking processes, monitor their progress toward goals, and strategically adjust their approach when encountering obstacles. Users with high metacognitive planning actively set sub-goals, predict potential difficulties, evaluate their understanding, and modify their strategies based on ongoing self-assessment. In web interfaces, this manifests as users who pause to consider "What am I trying to accomplish?", "Is this approach working?", and "What should I try next?" Low metacognitive planners tend to react to interfaces without systematic strategy, often clicking impulsively without considering whether their current approach is effective.
-
-## Research Foundation
-
-### Primary Citation
-
-> "Metacognition refers to one's knowledge concerning one's own cognitive processes and products or anything related to them... Metacognition refers, among other things, to the active monitoring and consequent regulation and orchestration of these processes in relation to the cognitive objects or data on which they bear, usually in the service of some concrete goal or objective."
-> -- Flavell, 1979, p. 906
-
-**Full Citation (APA 7):**
-Flavell, J. H. (1979). Metacognition and cognitive monitoring: A new area of cognitive-developmental inquiry. *American Psychologist*, 34(10), 906-911.
-
-**DOI**: https://doi.org/10.1037/0003-066X.34.10.906
-
-### Supporting Research
-
-> "Metacognitive monitoring accuracy varies widely, with estimates ranging from 50% to 90% accuracy depending on task domain and individual differences."
-> -- Dunlosky & Metcalfe, 2009
-
-**Full Citation (APA 7):**
-Dunlosky, J., & Metcalfe, J. (2009). *Metacognition*. SAGE Publications.
-
-### Key Numerical Values
-
-| Metric | Value | Source |
-|--------|-------|--------|
-| Monitoring accuracy range | 50-90% | Dunlosky & Metcalfe (2009) |
-| Planning time overhead | 15-30% of task time | Nelson & Narens (1990) |
-| Error detection rate (high metacog) | 78% | Veenman et al. (2006) |
-| Error detection rate (low metacog) | 34% | Veenman et al. (2006) |
-| Strategy switch threshold | 3-5 failed attempts | Winne & Hadwin (1998) |
-| Goal monitoring frequency | Every 30-60 seconds | Azevedo & Cromley (2004) |
-
-## Behavioral Levels
-
-| Value | Label | Behaviors |
-|-------|-------|-----------|
-| 0.0-0.2 | Very Low | Clicks without strategy; does not recognize when lost; repeats failed actions 5+ times; never pauses to assess progress; blames interface rather than adjusting approach; cannot articulate what they are trying to do; abandons without trying alternatives |
-| 0.2-0.4 | Low | Minimal self-monitoring; recognizes being stuck only after 4+ failed attempts; rarely forms explicit sub-goals; limited awareness of confusion; may eventually try a different approach but without clear reasoning; difficulty remembering what has already been tried |
-| 0.4-0.6 | Moderate | Sets basic goals before starting; monitors progress intermittently; recognizes being stuck after 2-3 failed attempts; can articulate current objective when asked; considers 1-2 alternative approaches; occasionally backtracks strategically; uses browser back button appropriately |
-| 0.6-0.8 | High | Plans approach before clicking; sets explicit sub-goals; monitors progress every 30-60 seconds; recognizes confusion quickly (1-2 attempts); maintains mental model of site structure; strategically explores navigation; remembers and avoids previously failed paths; uses landmarks for orientation |
-| 0.8-1.0 | Very High | Systematic pre-planning with explicit sub-goals; continuous self-monitoring; immediately recognizes when approach is not working; maintains detailed mental map of explored areas; strategic use of browser history, tabs, and search; articulates reasoning aloud or internally; actively predicts outcomes before clicking; efficient backtracking and path correction |
-
-## Web/UI Behavioral Patterns
-
-### Navigation Strategy
-
-| Level | Observed Behavior |
-|-------|-------------------|
-| Very Low | Random clicking; no clear path; returns to homepage repeatedly without learning |
-| Low | Trial-and-error with limited memory; may try same wrong path twice |
-| Moderate | Follows logical paths; uses breadcrumbs when available |
-| High | Scans navigation structure first; forms mental map before deep navigation |
-| Very High | Uses site map, search strategically; opens multiple tabs for comparison |
-
-### Form Completion
-
-| Level | Observed Behavior |
-|-------|-------------------|
-| Very Low | Fills fields randomly; submits without reviewing; surprised by errors |
-| Low | Sequential filling; minimal preview; errors discovered one at a time |
-| Moderate | Reads form overview first; groups related fields; reviews before submit |
-| High | Plans required information before starting; has documents ready |
-| Very High | Pre-reads all fields; prepares all information; validates progressively |
-
-### Error Recovery
-
-| Level | Observed Behavior |
-|-------|-------------------|
-| Very Low | Clicks same broken button repeatedly; does not read error messages |
-| Low | Eventually tries different button; error messages partially read |
-| Moderate | Reads error message; tries suggested fix; seeks help if fix fails |
-| High | Diagnoses error cause; tries multiple systematic solutions |
-| Very High | Prevents errors through preview; when errors occur, uses systematic debugging |
-
-## Estimated Trait Correlations
-
-> *Correlation estimates are derived from related research findings and theoretical models. Empirical calibration is planned ([GitHub #95](https://github.com/alexandriashai/cbrowser/issues/95)).*
-
-| Related Trait | Correlation | Research Basis |
-|---------------|-------------|----------------|
-| [Working Memory](./Trait-WorkingMemory.md) | r = 0.58 | Metacognitive monitoring requires maintaining current state and goals in working memory (Veenman et al., 2006) |
-| [Persistence](./Trait-Persistence.md) | r = 0.42 | High metacognition enables more effective persistence through strategic adjustment rather than mere repetition (Schraw & Dennison, 1994) |
-| [Comprehension](./Trait-Comprehension.md) | r = 0.51 | Metacognitive awareness improves comprehension monitoring and repair (Flavell, 1979) |
-| [Self-Efficacy](./Trait-SelfEfficacy.md) | r = 0.47 | Self-awareness of capabilities relates to self-efficacy beliefs (Bandura, 1986) |
-| [Satisficing](./Trait-Satisficing.md) | r = -0.35 | High metacognition tends toward maximizing through deliberate evaluation (Simon, 1956) |
-
-## Persona Values
-
-| Persona | Value | Rationale |
-|---------|-------|-----------|
-| power-user | 0.85 | Experts develop strong metacognitive skills through experience |
-| first-timer | 0.35 | Novices lack domain-specific metacognitive strategies |
-| elderly-user | 0.60 | Life experience provides general metacognition despite tech unfamiliarity |
-| impatient-user | 0.25 | Impatience conflicts with reflective self-monitoring |
-| screen-reader-user | 0.75 | Accessibility navigation requires strategic planning |
-| mobile-user | 0.45 | Touch interaction somewhat reduces reflective planning |
-| anxious-user | 0.55 | Anxiety can either enhance or impair metacognition |
-
-## Implementation in CBrowser
-
-### State Tracking
-
-```typescript
-interface MetacognitiveState {
-  currentGoal: string;
-  subGoals: string[];
-  progressEstimate: number;  // 0-1
-  strategySwitches: number;
-  failedAttemptsSinceSwitch: number;
-  exploredPaths: Set<string>;
-  mentalMapQuality: number;  // 0-1
-  lastMonitoringCheck: number;  // timestamp
-}
-```
-
-### Behavioral Modifiers
-
-- **Planning pause**: High metacognition adds 1-3 second pause before first action on new page
-- **Progress checking**: Frequency of goal-state comparison based on trait level
-- **Strategy switching**: Threshold for abandoning current approach (3-5 attempts for low, 1-2 for high)
-- **Path memory**: High metacognition maintains explored path history to avoid revisiting
-
-## See Also
-
-- [Trait-WorkingMemory](./Trait-WorkingMemory.md) - Capacity for maintaining goals and state
-- [Trait-ProceduralFluency](./Trait-ProceduralFluency.md) - Executing learned procedures efficiently
-- [Trait-TransferLearning](./Trait-TransferLearning.md) - Applying strategies across domains
-- [Trait-Comprehension](./Trait-Comprehension.md) - Understanding interface conventions
-- [Cognitive-User-Simulation](../COGNITIVE-SIMULATION.md) - Main simulation documentation
-- [Persona-Index](../personas/Persona-Index.md) - Pre-configured trait combinations
-
-## Bibliography
-
-Azevedo, R., & Cromley, J. G. (2004). Does training on self-regulated learning facilitate students' learning with hypermedia? *Journal of Educational Psychology*, 96(3), 523-535. https://doi.org/10.1037/0022-0663.96.3.523
-
-Bandura, A. (1986). *Social foundations of thought and action: A social cognitive theory*. Prentice-Hall.
-
-Dunlosky, J., & Metcalfe, J. (2009). *Metacognition*. SAGE Publications.
-
-Flavell, J. H. (1979). Metacognition and cognitive monitoring: A new area of cognitive-developmental inquiry. *American Psychologist*, 34(10), 906-911. https://doi.org/10.1037/0003-066X.34.10.906
-
-Nelson, T. O., & Narens, L. (1990). Metamemory: A theoretical framework and new findings. In G. H. Bower (Ed.), *The psychology of learning and motivation* (Vol. 26, pp. 125-173). Academic Press.
-
-Schraw, G., & Dennison, R. S. (1994). Assessing metacognitive awareness. *Contemporary Educational Psychology*, 19(4), 460-475. https://doi.org/10.1006/ceps.1994.1033
-
-Simon, H. A. (1956). Rational choice and the structure of the environment. *Psychological Review*, 63(2), 129-138. https://doi.org/10.1037/h0042769
-
-Veenman, M. V. J., Van Hout-Wolters, B. H. A. M., & Afflerbach, P. (2006). Metacognition and learning: Conceptual and methodological considerations. *Metacognition and Learning*, 1(1), 3-14. https://doi.org/10.1007/s11409-006-6893-0
-
-Winne, P. H., & Hadwin, A. F. (1998). Studying as self-regulated learning. In D. J. Hacker, J. Dunlosky, & A. C. Graesser (Eds.), *Metacognition in educational theory and practice* (pp. 277-304). Lawrence Erlbaum Associates.

package/docs/traits/Trait-Patience.md

@@ -1,137 +0,0 @@
-> **This documentation is no longer maintained here.**
->
-> For the latest version, please visit: **[Patience](https://cbrowser.ai/docs/Trait-Patience)**
-
----
-
-# Patience
-
-**Category**: Tier 1 - Core Traits
-**Scale**: 0.0 (very impatient) to 1.0 (very patient)
-
-## Definition
-
-Patience represents a user's tolerance for delays, loading times, and waiting periods during web interactions. This trait fundamentally affects how long users will wait before abandoning a task, clicking away from slow-loading pages, or becoming frustrated with unresponsive interfaces. Users with low patience rapidly escalate through frustration states and are quick to seek alternatives, while highly patient users will persist through delays and give systems time to respond before making judgments.
-
-## Research Foundation
-
-### Primary Citation
-
-> "Users start to feel that the system is not responding after about 8 seconds of delay... After this point, users become increasingly frustrated and are likely to abandon the page or repeat their action."
-> - Nah, 2004, p. 156
-
-**Full Citation (APA 7):**
-Nah, F. F.-H. (2004). A study on tolerable waiting time: How long are Web users willing to wait? *Behaviour & Information Technology*, 23(3), 153-163. https://doi.org/10.1080/01449290410001669914
-
-**DOI**: https://doi.org/10.1080/01449290410001669914
-
-### Supporting Research
-
-> "The acceptable response time depends on the complexity of the operation, with simple operations requiring faster responses (2 seconds) and complex operations tolerating longer delays (up to 10 seconds)."
-> - Nielsen, 1993, p. 135
-
-**Full Citation (APA 7):**
-Nielsen, J. (1993). *Usability Engineering*. Academic Press. ISBN 978-0125184069
-
-### Key Numerical Values
-
-| Metric | Value | Source |
-|--------|-------|--------|
-| Tolerable wait time (simple) | 2 seconds | Nielsen (1993) |
-| Tolerable wait time (complex) | 8-10 seconds | Nah (2004) |
-| Abandonment threshold | 8+ seconds | Nah (2004) |
-| Frustration onset | 3-4 seconds | Forrester Research (2009) |
-| Bounce rate increase per second | 7% | Google (2017) |
-| Mobile abandonment threshold | 3 seconds | Google (2018) |
-| Repeat click probability after 8s | 68% | Nah (2004) |
-
-## Behavioral Levels
-
-| Value | Label | Behaviors |
-|-------|-------|-----------|
-| 0.0-0.2 | Very Impatient | Abandons pages after 2-3 seconds of load time. Clicks multiple times on slow buttons. Opens multiple tabs to "hedge bets." Becomes visibly frustrated at any delay. Will leave checkout if any step takes more than 2 seconds. Rarely waits for animations to complete. |
-| 0.2-0.4 | Impatient | Tolerates 3-5 seconds of delay before frustration. Frequently refreshes slow pages. May abandon complex forms if validation is slow. Prefers instant feedback over thorough processing. Skips introductory animations. Uses back button aggressively when pages don't load quickly. |
-| 0.4-0.6 | Moderate | Standard 8-10 second tolerance per Nah (2004). Will wait for reasonable loading if progress indicators are shown. May become frustrated with repeated delays but persists for high-value tasks. Accepts loading spinners as normal. Waits for search results but may refine query if too slow. |
-| 0.6-0.8 | Patient | Tolerates 15-20 seconds for complex operations. Reads loading messages and status updates. Willing to wait for quality content. Doesn't reflexively click repeatedly. Understands that complex operations take time. Rarely abandons due to speed alone. |
-| 0.8-1.0 | Very Patient | Tolerates 30+ seconds for important tasks. Reads terms and conditions fully. Waits for complete page loads before interacting. Never double-clicks out of impatience. Willing to retry failed operations. Provides patience buffer for first-time site visits. |
-
-## Estimated Trait Correlations
-
-> *Correlation estimates are derived from related research findings and theoretical models. Empirical calibration is planned ([GitHub #95](https://github.com/alexandriashai/cbrowser/issues/95)).*
-
-| Related Trait | Correlation | Mechanism |
-|---------------|-------------|-----------|
-| [Persistence](./Trait-Persistence.md) | r = 0.45 | Both load on conscientiousness factor; patient users persist longer |
-| [Resilience](../traits/Trait-Resilience) | r = 0.38 | Patient users recover better from delays |
-| [Self-Efficacy](../traits/Trait-SelfEfficacy) | r = 0.32 | Confident users wait longer, believing success is coming |
-| [Risk Tolerance](./Trait-RiskTolerance.md) | r = -0.22 | Impatient users take more shortcuts (risky behavior) |
-| [FOMO](../traits/Trait-FOMO) | r = -0.41 | FOMO drives impatience to not miss out |
-
-## Impact on Web Behavior
-
-### Page Load Tolerance
-
-```
-Very Impatient (0.0-0.2): Abandons at 2-3 seconds
-Impatient (0.2-0.4): Abandons at 4-5 seconds
-Moderate (0.4-0.6): Abandons at 8-10 seconds (baseline)
-Patient (0.6-0.8): Tolerates 15-20 seconds
-Very Patient (0.8-1.0): Tolerates 30+ seconds
-```
-
-### Form Completion
-
-- **Low patience**: Abandons multi-step forms, skips optional fields, frustrated by validation delays
-- **High patience**: Completes all fields, reads instructions, waits for async validation
-
-### Error Recovery
-
-- **Low patience**: Immediately retries or leaves after first error
-- **High patience**: Reads error messages, tries suggested solutions, waits for support
-
-## Persona Values
-
-| Persona | Patience Value | Rationale |
-|---------|----------------|-----------|
-| [Rushed Professional](../personas/Persona-RushedProfessional) | 0.2 | Time-pressured, multitasking, low tolerance |
-| [Anxious First-Timer](../personas/Persona-AnxiousFirstTimer) | 0.3 | Nervous but slightly more willing to wait when unsure |
-| [Distracted Parent](../personas/Persona-DistractedParent) | 0.25 | Frequent interruptions reduce patience |
-| [Methodical Senior](../personas/Persona-MethodicalSenior) | 0.85 | Takes time, reads carefully, not rushed |
-| [Tech-Savvy Explorer](../personas/Persona-TechSavvyExplorer) | 0.6 | Moderate patience, expects performance |
-| [Accessibility User](../personas/Persona-AccessibilityUser) | 0.7 | Accustomed to slower interactions |
-
-## UX Design Implications
-
-### For Low-Patience Users
-- Implement skeleton screens instead of spinners
-- Show progress indicators for operations > 1 second
-- Lazy load below-fold content
-- Prefetch likely next pages
-- Avoid blocking interactions during background operations
-
-### For High-Patience Users
-- Can show more detailed loading states
-- May include richer loading animations
-- Less need for aggressive optimization
-- Can use interstitial pages for important information
-
-## See Also
-
-- [Trait Index](./Trait-Index.md) - All cognitive traits
-- [Persistence](./Trait-Persistence.md) - Related grit trait
-- [Working Memory](./Trait-WorkingMemory.md) - Affects wait perception
-- [Persona Index](../personas/Persona-Index.md) - Pre-configured personas
-
-## Bibliography
-
-Forrester Research. (2009). *eCommerce Web site performance today*. Forrester Research Report.
-
-Google. (2017). Find out how you stack up to new industry benchmarks for mobile page speed. *Think with Google*. https://www.thinkwithgoogle.com/marketing-strategies/app-and-mobile/mobile-page-speed-new-industry-benchmarks/
-
-Google. (2018). The need for mobile speed: How mobile latency impacts publisher revenue. *DoubleClick by Google*. https://www.doubleclickbygoogle.com/articles/mobile-speed-matters/
-
-Nah, F. F.-H. (2004). A study on tolerable waiting time: How long are Web users willing to wait? *Behaviour & Information Technology*, 23(3), 153-163. https://doi.org/10.1080/01449290410001669914
-
-Nielsen, J. (1993). *Usability Engineering*. Academic Press. ISBN 978-0125184069
-
-Nielsen, J. (1999). *Designing Web Usability: The Practice of Simplicity*. New Riders Publishing.