hummbl-framework

Complete HUMMBL Base120 mental models framework with all 120 models across 6 transformations (Perspective, Inversion, Composition, Decomposition, Recursion, Meta-Systems). Includes model selection guidance, application methodology, and validation checklist. Version 1.0-beta definitive reference.

$ インストール

git clone https://github.com/hummbl-dev/hummbl-claude-skills /tmp/hummbl-claude-skills && cp -r /tmp/hummbl-claude-skills/hummbl-framework ~/.claude/skills/hummbl-claude-skills

// tip: Run this command in your terminal to install the skill


name: hummbl-framework description: Complete HUMMBL Base120 mental models framework with all 120 models across 6 transformations (Perspective, Inversion, Composition, Decomposition, Recursion, Meta-Systems). Includes model selection guidance, application methodology, and validation checklist. Version 1.0-beta definitive reference.

HUMMBL Base120 Mental Models Framework Skill

Version: 1.0-beta (Definitive Reference)
Source: Google Drive (Created 10/16/2025)
Status: PRODUCTION – DO NOT MODIFY WITHOUT APPROVAL


Overview

Comprehensive reference for the HUMMBL Base120 framework, featuring 120 validated mental models across 6 transformation categories with precise codes, official names, and one-line definitions.
Use this skill for: mental model reference, model selection, transformation analysis, MCP server development, agent training, and problem-solving.

Base120 Architecture

  • 6 Transformations × 20 Models Each = 120 Total Models
  • Coding: [TRANSFORMATION][NUMBER] (e.g., P1, IN15, CO7)
  • Validation Date: October 16, 2025
  • Quality Score: 9.2/10 average
  • Priority Levels: P1–P7 (empirically derived usage frequency)

The 6 Transformations and Models

P — Perspective / Identity (P1–P20)

Transform: Frame and name what is. Anchor or shift point of view.

CodeNameOne-Line Definition
P1First Principles FramingReduce complex problems to foundational truths that cannot be further simplified
P2Stakeholder MappingIdentify all parties with interest, influence, or impact in a system or decision
P3Identity StackRecognize that individuals operate from multiple nested identities simultaneously
P4Lens ShiftingDeliberately adopt different interpretive frameworks to reveal hidden aspects
P5Empathy MappingSystematically capture what stakeholders see, think, feel, and do in their context
P6Point-of-View AnchoringEstablish and maintain a consistent reference frame before analysis begins
P7Perspective SwitchingRotate through multiple viewpoints to identify invariants and blind spots
P8Narrative FramingStructure information as causal stories with conflict, choice, and consequence
P9Cultural Lens ShiftingAdjust communication and interpretation for different cultural contexts and norms
P10Context WindowingDefine explicit boundaries in time, space, and scope for analysis or action
P11Role Perspective-TakingTemporarily inhabit specific roles to understand constraints and priorities
P12Temporal FramingOrganize understanding across past causes, present states, and future implications
P13Spatial FramingScale perspective from local details to global patterns and back
P14Reference Class FramingSelect comparable situations to inform judgment and avoid uniqueness bias
P15Assumption SurfacingExplicitly identify and document beliefs underlying plans or models
P16Identity-Context ReciprocityRecognize how identities shape interpretations and contexts reinforce identities
P17Frame Control & ReframingConsciously select or reshape interpretive frames to enable new solutions
P18Boundary Object SelectionChoose representations that bridge multiple perspectives while remaining meaningful
P19Sensemaking CanvasesDeploy structured templates to systematically capture and organize observations
P20Worldview ArticulationMake explicit the fundamental beliefs and values that drive interpretation and action

IN — Inversion (IN1–IN20)

Transform: Reverse assumptions. Examine opposites, edges, negations.

CodeNameOne-Line Definition
IN1Subtractive ThinkingImprove systems by removing elements rather than adding complexity
IN2Premortem AnalysisAssume failure has occurred and work backward to identify causes
IN3Problem ReversalSolve the inverse of the stated problem to reveal insights
IN4Contra-LogicArgue the opposite position to stress-test assumptions and expose weak reasoning
IN5Negative Space FramingStudy what is absent rather than what is present
IN6Inverse/Proof by ContradictionAssume a claim is false, derive logical impossibility, thus proving the claim true
IN7Boundary TestingExplore extreme conditions to find system limits and breaking points
IN8Contrapositive ReasoningUse logical equivalence that "if A then B" equals "if not B then not A"
IN9Backward InductionBegin with desired end state and work backward to determine necessary steps
IN10Red TeamingOrganize adversarial review to find vulnerabilities through simulated attack
IN11Devil's Advocate ProtocolAssign explicit role to argue against group consensus or preferred option
IN12Failure First DesignBegin planning by identifying all possible failure modes and designing to prevent them
IN13Opportunity Cost FocusEvaluate options by what must be forgone rather than what is gained
IN14Second-Order Effects (Inverted)Trace negative downstream consequences rather than immediate benefits
IN15Constraint ReversalTemporarily remove assumed constraints to explore alternative solution space
IN16Inverse OptimizationMaximize worst outcomes to understand system vulnerabilities
IN17Counterfactual NegationImagine outcomes if key decision had been reversed
IN18Kill-Criteria & Stop RulesDefine conditions that trigger project termination before launch
IN19Harm Minimization (Via Negativa)Improve by removing harmful elements rather than adding beneficial ones
IN20Antigoals & Anti-Patterns CatalogDocument failure modes to avoid rather than success patterns to emulate

CO — Composition (CO1–CO20)

Transform: Combine parts into coherent wholes.

CodeNameOne-Line Definition
CO1Synergy PrincipleDesign combinations where integrated value exceeds sum of parts
CO2ChunkingGroup related elements into meaningful units to reduce cognitive load
CO3Functional CompositionChain pure operations where output of one becomes input of next
CO4Interdisciplinary SynthesisMerge insights from distinct fields to generate novel solutions
CO5EmergenceRecognize higher-order behavior arising from component interactions
CO6Gestalt IntegrationPerceive and leverage whole patterns rather than isolated components
CO7Network EffectsExploit increasing value as user base or connections grow
CO8Layered AbstractionSeparate concerns into hierarchical levels with clear interfaces between them
CO9Interface ContractsDefine explicit agreements about data structures and behavior between components
CO10Pipeline OrchestrationCoordinate sequential stages with explicit handoffs and error handling
CO11Pattern Composition (Tiling)Combine repeating elements to construct complex structures efficiently
CO12Modular InteroperabilityEnsure independent components work together through standardized connections
CO13Cross-Domain AnalogyTransfer solution patterns from one domain to solve problems in another
CO14PlatformizationExtract common capabilities into reusable infrastructure serving multiple use cases
CO15Combinatorial DesignSystematically explore option combinations to find optimal configurations
CO16System Integration TestingVerify assembled components work correctly together, not just in isolation
CO17Orchestration vs ChoreographyChoose between centralized coordination or distributed peer-to-peer interaction
CO18Knowledge GraphingRepresent information as interconnected entities and relationships
CO19Multi-Modal IntegrationSynthesize information from different sensory or data modalities
CO20Holistic IntegrationUnify disparate elements into coherent, seamless whole where boundaries dissolve

DE — Decomposition (DE1–DE20)

Transform: Break complex systems into constituent parts.

CodeNameOne-Line Definition
DE1Root Cause Analysis (5 Whys)Iteratively ask why problems occur until fundamental cause emerges
DE2FactorizationSeparate multiplicative components to understand relative contribution of each factor
DE3ModularizationPartition system into self-contained units with minimal interdependencies
DE4Layered BreakdownDecompose from system to subsystem to component progressively
DE5Dimensional ReductionFocus on most informative variables while discarding noise or redundancy
DE6Taxonomy/ClassificationOrganize entities into hierarchical categories based on shared properties
DE7Pareto Decomposition (80/20)Identify vital few drivers producing most impact versus trivial many
DE8Work Breakdown StructureHierarchically divide project into deliverable-oriented components with clear ownership
DE9Signal SeparationDistinguish meaningful patterns from random variation or confounding factors
DE10Abstraction LadderingMove up and down conceptual hierarchy to find appropriate solution level
DE11Scope DelimitationDefine precise boundaries of what is included versus excluded from consideration
DE12Constraint IsolationIdentify specific limiting factor preventing performance improvement
DE13Failure Mode Analysis (FMEA)Enumerate potential failure points with severity, likelihood, and detectability ratings
DE14Variable Control & IsolationHold factors constant to measure single variable's causal impact
DE15Decision Tree ExpansionMap choices and their consequences as branching paths
DE16Hypothesis DisaggregationBreak compound claim into testable sub-hypotheses
DE17OrthogonalizationEnsure factors vary independently without correlation or interdependence
DE18Scenario DecompositionPartition future possibilities into discrete, mutually exclusive scenarios
DE19Critical Path UnwindingTrace longest sequence of dependent tasks determining minimum project duration
DE20Partition-and-ConquerDivide problem into independent subproblems solvable separately then combined

RE — Recursion (RE1–RE20)

Transform: Apply operations iteratively, with outputs becoming inputs.

CodeNameOne-Line Definition
RE1Recursive Improvement (Kaizen)Continuously refine process through small, frequent enhancements
RE2Feedback LoopsCreate mechanisms where system outputs influence future inputs
RE3Meta-Learning (Learn-to-Learn)Improve the process of learning itself, not just domain knowledge
RE4Nested NarrativesStructure information as stories within stories for depth and memorability
RE5Fractal ReasoningRecognize self-similar patterns repeating across different scales
RE6Recursive FramingApply mental models to the process of selecting mental models
RE7Self-Referential LogicCreate systems that monitor, measure, or modify themselves
RE8BootstrappingBuild capability using currently available resources, then use that to build more
RE9Iterative PrototypingCycle rapidly through build-test-learn loops with increasing fidelity
RE10Compounding CyclesDesign systems where gains reinforce future gains exponentially
RE11Calibration LoopsRepeatedly check predictions against outcomes to improve forecasting accuracy
RE12Bayesian Updating in PracticeContinuously revise beliefs as new evidence arrives, weighting by reliability
RE13Gradient Descent HeuristicIteratively adjust toward improvement, even without perfect knowledge of optimal direction
RE14Spiral LearningRevisit concepts at increasing depth, building on previous understanding
RE15Convergence-Divergence CyclingAlternate between expanding possibilities and narrowing to decisions
RE16Retrospective→Prospective LoopUse systematic reflection on past to inform future planning
RE17Versioning & DiffTrack changes over time and compare versions to understand evolution
RE18Anti-Catastrophic ForgettingPreserve critical knowledge while adapting to new information
RE19Auto-RefactorSystematically improve system structure without changing external behavior
RE20Recursive Governance (Guardrails that Learn)Establish rules that adapt based on their own effectiveness

SY — Meta-Systems (SY1–SY20)

Transform: Understand systems of systems, coordination, and emergent dynamics.

CodeNameOne-Line Definition
SY1Leverage PointsIdentify intervention points where small changes produce disproportionate effects
SY2System BoundariesDefine what is inside versus outside system scope for analysis or design
SY3Stocks & FlowsDistinguish accumulations from rates of change affecting them
SY4Requisite VarietyMatch control system's complexity to system being controlled
SY5Systems ArchetypesRecognize recurring dynamic patterns across different domains
SY6Feedback Structure MappingDiagram causal loops showing how variables influence each other
SY7Path DependenceAcknowledge how early decisions constrain future options through accumulated consequences
SY8Homeostasis/Dynamic EquilibriumUnderstand self-regulating mechanisms maintaining stable states despite disturbances
SY9Phase Transitions & Tipping PointsIdentify thresholds where gradual changes produce sudden qualitative shifts
SY10Causal Loop DiagramsVisualize circular cause-effect relationships with reinforcing and balancing dynamics
SY11Governance PatternsDesign decision rights, accountability structures, and coordination mechanisms
SY12Protocol/Interface StandardsSpecify rules for interaction enabling coordination without central control
SY13Incentive ArchitectureDesign reward and penalty structures aligning individual actions with system goals
SY14Risk & Resilience EngineeringBuild systems that fail gracefully and recover automatically
SY15Multi-Scale AlignmentEnsure strategy, operations, and execution cohere across organizational levels
SY16Ecosystem StrategyPosition organization within network of partners, competitors, and stakeholders
SY17Policy FeedbacksAnticipate how rules shape behavior, which creates conditions affecting future rules
SY18Measurement & TelemetryInstrument systems to capture state, changes, and anomalies for informed response
SY19Meta-Model SelectionChoose appropriate framework or tool for specific problem characteristics
SY20Systems-of-Systems CoordinationManage interactions between independent systems with emergent behaviors

Model Selection Guidance

  • Reference by code (e.g., "P1", "IN15").
  • NEVER substitute generic models ("OODA Loop", "Hanlon's Razor", etc.).
  • Always validate against this document.
  • Quick Selection Table Example
    Problem TypeTransformationExample Codes
    Unclear problem definitionPerspectiveP1, P2, P4
    Conventional thinking stuckInversionIN1, IN2, IN3
    Assembling solutionsCompositionCO1, CO2, CO4
    Complex system analysisDecompositionDE1, DE2, DE7
    Feedback/issuesRecursionRE1, RE2, RE3
    Strategic challengeMeta-SystemsSY1, SY2, SY4

Application Methodology

  • Apply transformation templates using verified codes and names.
  • Use one-line definitions for rapid agent coordination and reasoning.
  • Integrate Base120 reference in agent/server model selection.

Validation Checklist

  • Code matches pattern: [P|IN|CO|DE|RE|SY][1–20]
  • Name matches exactly as listed above
  • Model in correct transformation category
  • No generic substitutions (OODA, Hanlon's, Occam's, etc.)

Source & Provenance

  • Authoritative Document: Google Drive link
  • Owner: Reuben Bowlby rpbowlby@gmail.com
  • Validation Date: 2025-10-16
  • Repository: hummbl-dev/hummbl-claude-skills
  • Version: 1.0-beta (Definitive)