Skip to content

6D Foraging Methodology™ — Observable Properties Framework ​

"What gets measured becomes manageable. What gets observed becomes measurable."

Version: 2.0 Created: November 27, 2025 Revised: November 2026 (cost multipliers and invented cascade percentages removed; cascade patterns now counted from the published case library) Status: Production Framework


Executive Summary ​

The 6D Foraging Methodology™ traces how a problem spreads across six dimensions of an organization, using cited evidence at every step. This document provides the Observable Properties Framework — the concrete signals, metrics, trigger keywords, and cascade pathways that make each dimension measurable and actionable.

The Gap This Fills:

  • Before: Abstract categories (Customer, Employee, Revenue, etc.)
  • After: Specific observables, trigger keywords, data sources, and cascade maps

Integration with Cormorant Foraging: Each dimension is analyzed through three lenses:

  • Sound (ChirpIQX): Urgency — How immediate is the signal?
  • Space (PerchIQX): Scope — How widespread is the impact?
  • Time (WakeIQX): Trajectory — Is it improving or degrading?

Framework Architecture ​

┌─────────────────────────────────────────────────────────────────┐
│                    6D IMPACT METHODOLOGY™                       │
│                 Observable Properties Framework                  │
├─────────────────────────────────────────────────────────────────┤
│                                                                 │
│   ┌─────────┐ ┌─────────┐ ┌─────────┐ ┌─────────┐ ┌─────────┐ ┌─────────┐
│   │CUSTOMER │ │EMPLOYEE │ │ REVENUE │ │REGULATORY│ │ QUALITY │ │OPERATION│
│   │   D1    │ │   D2    │ │   D3    │ │   D4    │ │   D5    │ │   D6    │
│   └────┬────┘ └────┬────┘ └────┬────┘ └────┬────┘ └────┬────┘ └────┬────┘
│        │           │           │           │           │           │
│        └───────────┴───────────┴─────┬─────┴───────────┴───────────┘
│                                      │
│                              ┌───────▼───────┐
│                              │   3D LENS     │
│                              ├───────────────┤
│                              │ Sound (Urgency)│
│                              │ Space (Scope)  │
│                              │ Time (Trend)   │
│                              └───────┬───────┘
│                                      │
│                              ┌───────▼───────┐
│                              │ CASCADE MAP   │
│                              │ + CAL SCORING │
│                              └───────────────┘
│                                                                 │
└─────────────────────────────────────────────────────────────────┘

Dimension 1: CUSTOMER IMPACT ​

Core Question: How does this problem affect the people who pay us?

Observable Signals ​

Signal TypeObservableData SourceDetection Speed
ImmediateSupport ticket spikeHelpdesk (Zendesk, ServiceNow)Hours
BehavioralRenewal hesitationSales notes, CRMDays-Weeks
SentimentNPS/CSAT score dropSurvey platformsWeekly
EngagementProduct usage declineAnalytics (Mixpanel, Amplitude)Days
EscalationExec-level complaintsEmail, meeting requestsHours
SilentReduced feature adoptionProduct analyticsWeeks
ChurnCancellation requestsBilling/CRMImmediate
TrustReference refusalsSales team feedbackVariable

Trigger Keywords ​

High Urgency (Sound = 8-10):

"unacceptable"          "breach of contract"      "legal action"
"canceling"             "considering alternatives" "escalating"
"demand refund"         "not what we signed up for"

Medium Urgency (Sound = 4-7):

"disappointed"          "concerned about"         "need clarification"
"frustrating"           "expected better"         "reconsidering"
"will not renew"        "shopping around"

Low Urgency / Early Warning (Sound = 1-3):

"just wondering"        "any updates on"          "is this normal"
"thought it would be"   "not urgent but"          "for future reference"

Metrics ​

Metric TypeMetric NameCalculation
LeadingSupport ticket velocityTickets/day vs 30-day avg
LeadingNPS trendWeek-over-week delta
LeadingFeature adoption rateNew feature usage %
LaggingCustomer churn rateLost customers / Total
LaggingCustomer lifetime valueRevenue × Retention period
LaggingNet revenue retention(Start + Expansion - Churn) / Start

Cascade Pathways ​

How it can spread. These are mechanisms to look for, not a ranking of how often each path happens.

CUSTOMER IMPACT
      │
      ├──────────────────────────────────────┐
      ▼                                      ▼
   REVENUE                               EMPLOYEE
   (Lost renewals,                       (Morale hit from
   reduced expansion,                     angry customers,
   refund requests)                       support burnout)
      │                                      │
      ▼                                      ▼
   OPERATIONAL                           QUALITY
   (Resources diverted                   (Rushed fixes,
   to retention efforts)                  corners cut)
      │
      ▼
   REGULATORY
   (Breach of SLA,
   contract violations)

In the published library: Of the 50 cases that start in Customer, the next layer includes Revenue in 29, Quality in 26, Operational in 23, Employee in 5 and Regulatory in 2. Example: UC-305, D1 > D3+D6 > D5 > D4. These are counts from the published library (331 cases with a recorded cascade, as of November 2026, index), not probabilities.

Severity Factors ​

Things that tend to make the same signal more serious. Use them when setting the dimension score; they do not convert into a cost multiplier.

FactorLowerMiddleHigher
Customer SizeSmall accountMid-marketEnterprise/Strategic
Contract TermMonth-to-monthAnnualMulti-year
Reference ValueUnknownIndustry peerMarquee logo
Relationship Length<1 year1-3 years>3 years
Expansion PotentialMaxed outModerateSignificant

3D Scoring (Sound × Space × Time) ​

LensScore 1-3Score 4-6Score 7-10
Sound (Urgency)Feedback surveyDirect complaintLegal threat
Space (Scope)One customerCustomer segmentMarket-wide
Time (Trajectory)First occurrenceRecurring patternAccelerating trend

Dimension Score = Sound × Space × Time ÷ 10


Dimension 2: EMPLOYEE IMPACT ​

Core Question: How does this problem affect the people who work for us?

Observable Signals ​

Signal TypeObservableData SourceDetection Speed
ImmediateOvertime hours spikeTimesheets, HRISDaily
BehavioralMeeting no-showsCalendar analyticsDays
SentimentEngagement score dropPulse surveysWeekly
ProductivityOutput declineProject management toolsWeeks
TurnoverResignation noticesHR systemImmediate
KnowledgeBus factor = 1HEAT heatmapOngoing
HealthSick day increaseHR dataWeeks
SilentReduced participationMeeting notes, Slack activityWeeks

Trigger Keywords ​

High Urgency (Sound = 8-10):

"I'm done"              "putting in notice"       "can't do this anymore"
"looking for other jobs" "burned out"             "hostile environment"
"discrimination"         "harassment"             "unsafe"

Medium Urgency (Sound = 4-7):

"overwhelmed"           "not sustainable"         "need help"
"understaffed"          "no work-life balance"    "thankless"
"underappreciated"      "dead end"               "no growth"

Low Urgency / Early Warning (Sound = 1-3):

"just curious about"    "any development opportunities"  "hypothetically"
"work from home policy" "how do other teams"             "is it just us"

Metrics ​

Metric TypeMetric NameCalculation
LeadingOvertime hoursHours > 40/week
LeadingEngagement pulseSurvey score (1-10)
LeadingMeeting attendanceAttended / Invited
LeadingPTO utilizationDays taken / Days available
LaggingVoluntary turnoverResignations / Headcount
LaggingTime-to-fillDays from req to hire
LaggingKnowledge concentration% of critical tasks with single owner

Cascade Pathways ​

How it can spread. These are mechanisms to look for, not a ranking of how often each path happens.

EMPLOYEE IMPACT
      │
      ├──────────────────────────────────────┐
      ▼                                      ▼
   QUALITY                               OPERATIONAL
   (Mistakes increase,                   (Slower delivery,
   attention drops,                       bottlenecks form,
   shortcuts taken)                       institutional knowledge lost)
      │                                      │
      ▼                                      ▼
   CUSTOMER                              REVENUE
   (Service quality                      (Productivity loss,
   degradation,                           hiring costs,
   responsiveness drops)                  training investment lost)
      │
      ▼
   REGULATORY
   (Compliance gaps,
   safety incidents,
   documentation failures)

In the published library: Of the 59 cases that start in Employee, the next layer includes Revenue in 31, Operational in 27, Quality in 18, Customer in 13 and Regulatory in 7. Example: UC-334, D2 > D4+D5 > D6+D1. These are counts from the published library (331 cases with a recorded cascade, as of November 2026, index), not probabilities.

Severity Factors ​

Things that tend to make the same signal more serious. Use them when setting the dimension score; they do not convert into a cost multiplier.

FactorLowerMiddleHigher
Role CriticalityEasily backfilledSpecializedIrreplaceable expertise
Knowledge ConcentrationWell-documentedPartially documentedTribal knowledge only
Team SizeLarge team (redundancy)Medium teamSmall/Solo
Replacement Time<30 days30-90 days>90 days
Training InvestmentEntry levelMid-levelSenior/Specialized

3D Scoring (Sound × Space × Time) ​

LensScore 1-3Score 4-6Score 7-10
Sound (Urgency)GrumblingActive complaintsResignation
Space (Scope)One personOne teamCross-functional
Time (Trajectory)Temporary stressSustained pressureChronic condition

Dimension 3: REVENUE IMPACT ​

Core Question: How does this problem affect money coming in?

Observable Signals ​

Signal TypeObservableData SourceDetection Speed
ImmediateInvoice disputesAR aging reportDays
BehavioralDiscount requestsSales CRMDays
PipelineDeal slippageForecast systemWeekly
PenaltySLA breach paymentsContract managementImmediate
OpportunityLost bidsSales post-mortemsDays
PricingMargin compressionFinancial reportsMonthly
CashPayment cycle lengtheningCash flow analysisWeeks
SilentUpsell/cross-sell declineRevenue analyticsMonths

Trigger Keywords ​

High Urgency (Sound = 8-10):

"penalty clause"        "breach of contract"      "demand refund"
"termination"           "lawsuit"                 "material breach"
"audit finding"         "revenue restatement"     "write-off"

Medium Urgency (Sound = 4-7):

"renegotiate"           "discount"                "credit"
"delayed payment"       "budget cut"              "procurement review"
"competitive bid"       "price matching"          "cost reduction"

Low Urgency / Early Warning (Sound = 1-3):

"next fiscal year"      "budget planning"         "exploring options"
"market conditions"     "strategic review"        "benchmarking"

Metrics ​

Metric TypeMetric NameCalculation
LeadingPipeline velocityDays in stage vs benchmark
LeadingDiscount rateAvg discount % on closed deals
LeadingAR aging% of receivables >60 days
LeadingForecast accuracyActual / Forecasted
LaggingRevenue growthYoY change
LaggingGross margin(Revenue - COGS) / Revenue
LaggingRevenue per employeeTotal revenue / Headcount

Cascade Pathways ​

How it can spread. These are mechanisms to look for, not a ranking of how often each path happens.

REVENUE IMPACT
      │
      ├──────────────────────────────────────┐
      ▼                                      ▼
   OPERATIONAL                           EMPLOYEE
   (Cost cutting,                        (Hiring freeze,
   resource constraints,                  layoffs,
   investment delays)                     morale impact)
      │                                      │
      ▼                                      ▼
   QUALITY                               CUSTOMER
   (Budget cuts to QA,                   (Reduced service,
   cheaper materials,                     slower response,
   reduced testing)                       feature cuts)
      │
      ▼
   REGULATORY
   (Compliance budget cuts,
   audit failures,
   certification lapses)

In the published library: Of the 96 cases that start in Revenue, the next layer includes Operational in 65, Customer in 43, Quality in 32, Regulatory in 20 and Employee in 16. Example: UC-324, D3 > D6+D2 > D5+D1. These are counts from the published library (331 cases with a recorded cascade, as of November 2026, index), not probabilities.

Severity Factors ​

Things that tend to make the same signal more serious. Use them when setting the dimension score; they do not convert into a cost multiplier.

FactorLowerMiddleHigher
Revenue ConcentrationDiversifiedModerate concentrationA few customers carry most revenue
Contract TypeTransactionalAnnualMulti-year committed
Margin ProfileHigh marginAverage marginLow margin
Market PositionCommodityDifferentiatedMonopoly/Niche
SeasonalityEvenly distributedSome concentrationHighly seasonal

3D Scoring (Sound × Space × Time) ​

LensScore 1-3Score 4-6Score 7-10
Sound (Urgency)Future riskCurrent quarter impactImmediate cash crisis
Space (Scope)One dealProduct lineCompany-wide
Time (Trajectory)One-time hitQuarterly patternStructural decline

Dimension 4: REGULATORY IMPACT ​

Core Question: How does this problem affect our compliance and legal standing?

Observable Signals ​

Signal TypeObservableData SourceDetection Speed
ImmediateAudit findingCompliance reportsDays
BehavioralDocumentation gapsProcess auditsWeeks
ViolationNon-compliance noticeLegal/ComplianceImmediate
ExposureMissing certificationsCompliance trackerMonthly
TrainingExpired certificationsLMS/HR systemOngoing
ProcessDeviation from standardQuality reviewsWeeks
SilentPolicy not followedInternal auditsMonths
ExternalRegulatory inquiryLegal departmentImmediate

Trigger Keywords ​

High Urgency (Sound = 8-10):

"violation"             "fine"                    "penalty"
"cease and desist"      "investigation"           "lawsuit"
"material weakness"     "regulatory action"       "license suspended"
"criminal"              "fraud"                   "subpoena"

Medium Urgency (Sound = 4-7):

"audit finding"         "non-compliance"          "remediation required"
"certification gap"     "documentation missing"   "policy violation"
"deadline approaching"  "renewal pending"         "inspection scheduled"

Low Urgency / Early Warning (Sound = 1-3):

"new regulation"        "industry guidance"       "best practice"
"peer comparison"       "voluntary disclosure"    "proactive review"

Metrics ​

Metric TypeMetric NameCalculation
LeadingOpen audit findingsCount of unresolved
LeadingCertification currencyDays until expiration
LeadingPolicy acknowledgment% of employees current
LeadingTraining completionRequired training %
LaggingRegulatory finesDollar amount / year
LaggingAudit opinionClean / Qualified / Adverse
LaggingCompliance incidentsCount per year

Cascade Pathways ​

How it can spread. These are mechanisms to look for, not a ranking of how often each path happens.

REGULATORY IMPACT
      │
      ├──────────────────────────────────────┐
      ▼                                      ▼
   REVENUE                               CUSTOMER
   (Fines, penalties,                    (Trust erosion,
   contract terminations,                 public disclosure,
   market access loss)                    reputation damage)
      │                                      │
      ▼                                      ▼
   OPERATIONAL                           EMPLOYEE
   (Remediation efforts,                 (Compliance burden,
   process changes,                       blame culture,
   system modifications)                  legal exposure)
      │
      ▼
   QUALITY
   (Rushed compliance fixes,
   resource diversion,
   attention split)

In the published library: Of the 57 cases that start in Regulatory, the next layer includes Revenue in 36, Operational in 29, Customer in 25, Quality in 14 and Employee in 11. Example: UC-326, D4 > D6+D3 > D1+D2. These are counts from the published library (331 cases with a recorded cascade, as of November 2026, index), not probabilities.

Severity Factors ​

Things that tend to make the same signal more serious. Use them when setting the dimension score; they do not convert into a cost multiplier.

FactorLowerMiddleHigher
Industry RegulationLightModerateHeavily regulated (finance, healthcare)
Violation SeverityAdministrativeMaterialCriminal/Fraud
Public ExposureInternal onlyIndustry disclosurePublic/Media
Repeat OffenseFirst occurrencePatternWillful/Repeated
Remediation ComplexitySimple fixProcess changeSystemic overhaul

3D Scoring (Sound × Space × Time) ​

LensScore 1-3Score 4-6Score 7-10
Sound (Urgency)Best practice gapAudit findingActive investigation
Space (Scope)One processOne departmentEnterprise-wide
Time (Trajectory)First instancePattern emergingChronic non-compliance

Dimension 5: QUALITY IMPACT ​

Core Question: How does this problem affect what we deliver?

Observable Signals ​

Signal TypeObservableData SourceDetection Speed
ImmediateDefect rate spikeQA systemHours-Days
BehavioralRework hours increaseTimesheetsDays
CustomerComplaint volume upSupport systemDays
SafetyIncident reportsEHS systemImmediate
ReturnsProduct returnsLogistics/RMADays
ProcessSpecification deviationsQuality auditsWeeks
SilentWorkarounds createdTribal knowledge, interviewsMonths
InspectionRejection rateManufacturing QCImmediate

Trigger Keywords ​

High Urgency (Sound = 8-10):

"recall"                "safety incident"         "injury"
"critical defect"       "system failure"          "data breach"
"contamination"         "fatality"                "major outage"

Medium Urgency (Sound = 4-7):

"defect"                "rework"                  "redo"
"didn't meet spec"      "out of tolerance"        "failed inspection"
"customer complaint"    "return"                  "warranty claim"

Low Urgency / Early Warning (Sound = 1-3):

"workaround"            "manual fix"              "known issue"
"tech debt"             "legacy limitation"       "needs improvement"
"minor issue"           "cosmetic defect"         "edge case"

Metrics ​

Metric TypeMetric NameCalculation
LeadingFirst-pass yieldGood units / Total units
LeadingDefect detection rateDefects found internally / Total
LeadingCode coverage% of code with tests
LeadingTechnical debt ratioDebt remediation time / Dev time
LaggingCustomer-reported defectsCount per release/period
LaggingCost of qualityPrevention + Appraisal + Failure costs
LaggingWarranty costsClaims / Revenue

Cascade Pathways ​

How it can spread. These are mechanisms to look for, not a ranking of how often each path happens.

QUALITY IMPACT
      │
      ├──────────────────────────────────────┐
      ▼                                      ▼
   CUSTOMER                              OPERATIONAL
   (Dissatisfaction,                     (Rework cycles,
   trust erosion,                         resource diversion,
   churn risk)                            schedule delays)
      │                                      │
      ▼                                      ▼
   REVENUE                               EMPLOYEE
   (Warranty costs,                      (Frustration,
   refunds, penalties,                    overtime for fixes,
   lost sales)                            blame culture)
      │
      ▼
   REGULATORY
   (Safety violations,
   certification risk,
   mandatory recalls)

In the published library: Of the 81 cases that start in Quality, the next layer includes Operational in 45, Revenue in 39, Customer in 29, Regulatory in 13 and Employee in 12. Example: UC-338, D5 > D3+D6 > D2+D1. These are counts from the published library (331 cases with a recorded cascade, as of November 2026, index), not probabilities.

Severity Factors ​

Things that tend to make the same signal more serious. Use them when setting the dimension score; they do not convert into a cost multiplier.

FactorLowerMiddleHigher
Detection PointInternal QACustomer-foundField failure
Safety ImpactNonePotentialActual injury
Scope of DefectSingle unitBatch/LotSystemic design
Fix ComplexityPatch/UpdateReworkRecall/Replace
Brand SensitivityB2B commodityConsumer productPremium brand

3D Scoring (Sound × Space × Time) ​

LensScore 1-3Score 4-6Score 7-10
Sound (Urgency)Cosmetic issueFunctional defectSafety critical
Space (Scope)One unitBatch/ReleaseAll production
Time (Trajectory)Isolated incidentRecurringSystemic/Chronic

Dimension 6: OPERATIONAL IMPACT ​

Core Question: How does this problem affect how we work?

Observable Signals ​

Signal TypeObservableData SourceDetection Speed
ImmediateSystem downtimeMonitoring/APMMinutes
BehavioralManual workaroundsProcess documentationWeeks
BottleneckQueue length increaseWorkflow systemsDays
CycleProcessing time upMetrics dashboardsDays
ResourceContention/ConflictsProject managementDays
CapacityUtilization spikeResource planningDays
SilentShadow processesInterviews, observationMonths
IntegrationHandoff failuresCross-team metricsWeeks

Trigger Keywords ​

High Urgency (Sound = 8-10):

"system down"           "outage"                  "critical failure"
"data loss"             "cannot operate"          "business stopped"
"disaster recovery"     "incident"                "P1/Sev1"

Medium Urgency (Sound = 4-7):

"workaround"            "manual process"          "bottleneck"
"waiting on"            "blocked by"              "delayed"
"capacity issue"        "resource conflict"       "slow"

Low Urgency / Early Warning (Sound = 1-3):

"inefficient"           "could be better"         "nice to have"
"tech debt"             "legacy system"           "someday"
"minor friction"        "slight delay"            "process improvement"

Metrics ​

Metric TypeMetric NameCalculation
LeadingSystem uptimeAvailable time / Total time
LeadingCycle timeTime from start to completion
LeadingQueue depthItems waiting / Processing rate
LeadingResource utilizationAllocated / Available
LaggingIncidents per periodCount of P1/P2 incidents
LaggingMean time to recoveryAvg incident resolution time
LaggingProcess efficiencyValue-add time / Total time

Cascade Pathways ​

How it can spread. These are mechanisms to look for, not a ranking of how often each path happens.

OPERATIONAL IMPACT
      │
      ├─────────────────────────────────────────────────────┐
      ▼                          ▼                          ▼
   QUALITY                   EMPLOYEE                    REVENUE
   (Rushed work,             (Frustration,              (Delivery delays,
   corners cut,               overtime,                   penalties,
   reduced testing)           burnout)                    lost opportunities)
      │                          │                          │
      ▼                          ▼                          ▼
   CUSTOMER                  CUSTOMER                   REGULATORY
   (Late delivery,           (Poor service,             (Compliance gaps,
   quality issues)            slow response)             missed deadlines)

In the published library: Of the 74 cases that start in Operational, the next layer includes Revenue in 55, Quality in 35, Customer in 33, Employee in 11 and Regulatory in 11. Example: UC-335, D6 > D2+D5 > D4+D1. These are counts from the published library (331 cases with a recorded cascade, as of November 2026, index), not probabilities.

Severity Factors ​

Things that tend to make the same signal more serious. Use them when setting the dimension score; they do not convert into a cost multiplier.

FactorLowerMiddleHigher
System CriticalitySupport systemCore businessRevenue-generating
Dependency ChainStandaloneSome dependenciesHighly interconnected
Recovery OptionsQuick failoverManual recoveryNo backup
Business TimingOff-peakNormal operationsPeak/Critical period
Automation LevelHighly automatedPartially automatedManual processes

3D Scoring (Sound × Space × Time) ​

LensScore 1-3Score 4-6Score 7-10
Sound (Urgency)Efficiency opportunityBottleneckSystem down
Space (Scope)One processOne departmentCross-functional
Time (Trajectory)Temporary spikeRecurring issueChronic condition

CASCADE PATHWAY MASTER MAP ​

                         ┌─────────────────────────────────────────────────┐
                         │              PROBLEM ORIGIN                      │
                         │         (Identify starting dimension)            │
                         └─────────────────────────┬───────────────────────┘
                                                   │
           ┌───────────────────────────────────────┼───────────────────────────────────────┐
           │                                       │                                       │
           ▼                                       ▼                                       ▼
    ┌─────────────┐                        ┌─────────────┐                        ┌─────────────┐
    │  CUSTOMER   │◄──────────────────────►│  EMPLOYEE   │◄──────────────────────►│  REVENUE    │
    │     D1      │                        │     D2      │                        │     D3      │
    └──────┬──────┘                        └──────┬──────┘                        └──────┬──────┘
           │                                      │                                      │
           │         ┌────────────────────────────┼────────────────────────────┐         │
           │         │                            │                            │         │
           │         ▼                            ▼                            ▼         │
           │  ┌─────────────┐              ┌─────────────┐              ┌─────────────┐  │
           └─►│ REGULATORY  │◄────────────►│  QUALITY    │◄────────────►│ OPERATIONAL │◄─┘
              │     D4      │              │     D5      │              │     D6      │
              └─────────────┘              └─────────────┘              └─────────────┘

                         ┌─────────────────────────────────────────────────┐
                         │               CASCADE SPREAD                    │
                         │                                                 │
                         │   Each dimension can trigger any other          │
                         │   Pathway strength varies by problem type       │
                         │   Multiple simultaneous cascades possible       │
                         │                                                 │
                         └─────────────────────────────────────────────────┘

What the Published Library Shows ​

Counts from the published library (331 cases with a recorded cascade, as of November 2026, index). These are counts of what was recorded, not probabilities.

DimensionOrigin ofReached in (any layer)Lands in the last layer
D1 Customer50301 of 33165 of 331
D2 Employee59295 of 331132 of 331
D3 Revenue96304 of 33118 of 331
D4 Regulatory57285 of 331158 of 331
D5 Quality81294 of 33149 of 331
D6 Operational74312 of 33133 of 331
OriginNext layer includes (count of cases)
D1 Customer (50)Revenue 29, Quality 26, Operational 23, Employee 5, Regulatory 2
D2 Employee (59)Revenue 31, Operational 27, Quality 18, Customer 13, Regulatory 7
D3 Revenue (96)Operational 65, Customer 43, Quality 32, Regulatory 20, Employee 16
D4 Regulatory (57)Revenue 36, Operational 29, Customer 25, Quality 14, Employee 11
D5 Quality (81)Operational 45, Revenue 39, Customer 29, Regulatory 13, Employee 12
D6 Operational (74)Revenue 55, Quality 35, Customer 33, Employee 11, Regulatory 11

A case can have more than one origin, and a layer often holds two dimensions, so rows can add up to more than their totals. Regulatory lands last more often than any other dimension. Revenue is the most common origin but rarely the last stop.


SCORING METHODOLOGY ​

Step 1: Identify Observable Signals ​

For each dimension, document observed signals:

┌─────────────────────────────────────────────────────────┐
│ Dimension: [NAME]                                       │
├─────────────────────────────────────────────────────────┤
│ Signals Observed:                                       │
│ □ Immediate: _________________________________          │
│ □ Behavioral: ________________________________          │
│ □ Silent: ____________________________________          │
│                                                         │
│ Trigger Keywords Found:                                 │
│ □ High Urgency: ______________________________          │
│ □ Medium Urgency: ____________________________          │
│ □ Low Urgency: _______________________________          │
│                                                         │
│ Data Sources Checked:                                   │
│ □ ____________________________________________          │
│ □ ____________________________________________          │
└─────────────────────────────────────────────────────────┘

Step 2: Score Each Dimension (0-100) ​

Score each dimension the evidence reaches. The 3D Lens is one way to think the score through. Leave out dimensions the evidence does not reach; not every case scores all six.

DimensionSound (1-10)Space (1-10)Time (1-10)Dimension ScoreEvidence
Customer
Employee
Revenue
Regulatory
Quality
Operational

Dimension Score = (Sound × Space × Time) ÷ 10

Step 3: Map the Cascade ​

Trace the order the problem spreads in, layer by layer, with evidence for each step:

ORIGIN: [Dimension] — score ___/100
   │
   ├── Next layer: [Dimension] — score ___/100
   │       └── Evidence: _______________________ (cited, not assumed)
   │
   ├── Next layer: [Dimension] — score ___/100
   │       └── Evidence: _______________________
   │
   └── Later layer: [Dimension] — score ___/100
           └── Evidence: _______________________

Notation: origin > first layer > next layer   (e.g. D5 > D2+D6 > D4+D1)

Step 4: Score with CAL ​

The scoring belongs to CAL (spec v1.2.0):

Chirp      = average of the scored dimensions
DRIFT      = |Methodology − Performance|      (each 0-100)
Confidence = the analyst's 0-1 rating of evidence quality
FETCH      = Chirp × DRIFT × Confidence
FETCH levelWhen
EXECUTEFETCH ≥ T (high priority at 2T or above)
CONFIRMFETCH ≥ 0.75T
QUEUEFETCH ≥ 0.5T
WAITbelow 0.5T

T is the threshold, 1,000 by default.

Step 5: Write the Verdict ​

The written verdict (EXECUTE, MONITOR, WATCH, COUNTER…) is the analyst's own reading of the cascade. It can differ from the FETCH level. A prognostic case also records triggers and a review date, so it can be graded later.

Earlier versions of this framework had a multiplier step and a "total impact" dollar step. Neither came from published cases and both have been removed.


APPLICATION EXAMPLE: UC-335 ​

UC-335, "Thirty-Six to Find One", a published case about an AI-assisted survey of the Nazca geoglyphs.

Dimension Scores ​

DimensionScore
Customer (D1)58
Employee (D2)76
Revenue (D3)not scored
Regulatory (D4)64
Quality (D5)78
Operational (D6)82 (origin)

Cascade ​

D6 > D2+D5 > D4+D1

Operational first, then Employee and Quality, then Regulatory and Customer.

CAL Score ​

Chirp      = (58 + 76 + 64 + 78 + 82) ÷ 5 = 71.6
DRIFT      = |90 − 46| = 44           (Methodology 90, Performance 46)
Confidence = 0.84
FETCH      = 71.6 × 44 × 0.84 = 2,646

2,646 is above 2T, so the FETCH level is EXECUTE at high priority. The analyst's verdict is MONITOR. That is the verdict being a separate reading, as Step 5 describes.


QUICK REFERENCE CARD ​

Dimension Checklist ​

DDimensionCore QuestionKey Metric
1CustomerHow does this affect who pays us?NPS, Churn Rate
2EmployeeHow does this affect who works for us?Turnover, Engagement
3RevenueHow does this affect money coming in?AR Aging, Margin
4RegulatoryHow does this affect our compliance?Audit Findings, Fines
5QualityHow does this affect what we deliver?Defect Rate, Rework
6OperationalHow does this affect how we work?Uptime, Cycle Time

3D Quick Reference ​

LensQuestionLow (1-3)Medium (4-6)High (7-10)
SoundHow urgent?Future riskCurrent issueCrisis
SpaceHow widespread?IsolatedDepartmentEnterprise
TimeGetting better or worse?One-timeRecurringAccelerating

CAL Quick Reference ​

TermDefinition
ChirpAverage of the scored dimensions
DRIFT|Methodology − Performance|
ConfidenceAnalyst's 0-1 rating of evidence quality
FETCHChirp × DRIFT × Confidence
LevelsEXECUTE ≥ T (high priority ≥ 2T), CONFIRM ≥ 0.75T, QUEUE ≥ 0.5T, WAIT below; T defaults to 1,000

INTEGRATION WITH CORMORANT FORAGING ​

The 6D Observable Properties Framework extends the Cormorant Foraging methodology:

Cormorant (3D)6D Impact Application
Sound (ChirpIQX)Urgency scoring for each dimension
Space (PerchIQX)Scope mapping across dimensions
Time (WakeIQX)Trajectory tracking over cascade levels

Formula:

Dimension Score = (Sound × Space × Time) ÷ 10

Where each factor is scored 1-10:
- Sound = Urgency of signals
- Space = Scope of impact
- Time  = Trajectory (1 = one-time, 10 = accelerating)

Dimension scores then feed CAL's Chirp, the average of the scored dimensions. There is no weighted 6D total.

The void has structure. This framework measures it. 🪶


APPENDIX: INDUSTRY VARIATIONS ​

Healthcare ​

Standard DimensionHealthcare VariationKey Observable
CustomerPatient OutcomesReadmission rates, HCAHPS scores
QualityClinical QualityInfection rates, mortality rates
RegulatoryHIPAA/CMS ComplianceAudit findings, reimbursement risk

Financial Services ​

Standard DimensionFinServ VariationKey Observable
CustomerClient TrustAUM flows, relationship tenure
RegulatorySEC/FINRA/OCCExamination findings, capital ratios
QualityTrade AccuracyError rates, break resolution time

Manufacturing ​

Standard DimensionManufacturing VariationKey Observable
QualityProduction QualityFirst-pass yield, scrap rate
OperationalProduction EfficiencyOEE, changeover time
RegulatorySafety/EnvironmentalOSHA incidents, EPA compliance

SaaS/Technology ​

Standard DimensionSaaS VariationKey Observable
CustomerUser ExperienceAdoption rate, feature usage
OperationalSystem ReliabilityUptime, incident frequency
QualityTechnical DebtCode coverage, bug escape rate

End of 6D Observable Properties Framework

Version: 2.0 Feedback: Document learnings from field application


"Most analysis stops at the visible cost. They miss the cascade. Now you can see it."

6D Foraging Methodology™ — StratIQX