How a CEO sees the entire workforce — in a split second.
Colleen talks to her executives. Executives talk to their directors. Directors to their managers. The portal monitors every layer in between — and surfaces the break in the chain the moment it forms.
Sales CrewForrest · 3 in dorsal state since Mon AM
⚑ Source identified3 specific reps · regulation collapse · 26 hr ago
Recommended action: Run a Pause Protocol with the 3 reps before tomorrow's RFP pitch. Estimated AR-recovery delta: +$31K
Win/Loss Rate
Importance 9/10Window rolling 30 days−$120K projected
5
▼ from 7
Trace the Source
Win/Loss Source Trace · auto-detected
Colonial ParkingWin/Loss ▼ 7 → 5 · 30-day window
Sales DivisionVP Smith · 12 RFPs in flight, close rate dropped 18%
DC RegionDirector Jones · 4 active proposals, 3 stalled at follow-up
Sales Crew2 reps showing −3pt confidence drop in last 5 calls
⚑ Source identified2 specific reps · sympathetic state during cold-call window
Recommended action: Coaching pause + role-play before next pitch. Reciprocity Rule: VP joins their next 2 calls as observer. Estimated close-rate recovery: +11% in 14 days.
Customer Retention
Importance 8/10Window rolling 90 days−$33K at risk
3 members in dorsal state — second consecutive day.
Upcoming Events
Mary Faith · Events Director
Tomorrow10:00 AM
RFP Pitch · Mercer Real Estate
Sales Crew · Forrest · $200K opportunity
Watch
Friday5:00 PM
AR Deadline · Q1 reconciliation
Finance · linked to AR Reduction priority
Hard
Mon May 59:00 AM
Q2 Board Meeting Prep
Mary Faith · 6 deliverables tracked
Plan
Thu May 82:00 PM
Renewal Call · Federal Government Account
Customer Service · linked to Retention priority
Routine
May 15All day
Quarterly Facility Audit · 12 garages
Operations · linked to Facility Checklists priority
Plan
Trajectory30-day company state
OpsForce Composite6.4▼ 0.6 from 30d high
Wellness Composite6.2▼ 0.4 from 30d high
Distance-to-CTZ0.42CTZ ETA · ~47 days at current rate
Why this number matters
The traffic-ticket principle
A speeding ticket on a clean record is nothing. The same ticket on a record three points from suspension is a wall. The ticket didn't change — the system did.
Distance-to-CTZ is the system's current resilience to a single shock. 0.00 = at the bifurcation threshold. 1.00 = full reserves; one event absorbs cleanly.
At 0.42, Colonial sits in the second category for any moderate-magnitude V4 event in the next ~47 days. That is the *radius of vulnerability* — not a forecast, a state.
The product does not predict the ticket. It measures the driver.
Apr 11 · 30-day high (OpsForce 8.4)Apr 27 · Wellness leading-indicator drops firstApr 28 · AR slips 7 → 6 (one day after wellness drop)
Variable Degradation Map
V1 — V5 · 90-day Δ
V1━ 0.0
V2e▼ 1.4
V2m▼ 0.8
V2p▼ 1.7
V5▼ 0.3
Universal Signature Score
vs. 13-case baseline
Failure Signature Match22%
V5 still high · V1 grooves not yet rigid · early-warning territory, not crisis
Thrive Signature Match64%
V5 awake at CEO scope · V3 actively scanned · V2 reserves recoverable
Reading: Colonial currently sits in recoverable territory. The V2 depletion is real but the V5 brake is intact — same configuration that preceded LEGO's 2003–2017 turnaround and Adobe's 2013 Creative Cloud traversal. Window for V2e replenishment is open for the next 14 days.
Pattern Match · 13-Case LibraryClosest match · live ranking
Sales Division's current V2p signature — sustained Orange under performance Green at the executive layer — matches the Boeing 737 MAX program profile 11 weeks before Lion Air. The differential: Colonial's V5 is intact (Colleen scans actively), so the same trajectory does not imply the same outcome. Boeing's V5 was suppressed by cost-discipline grooves; Colonial's is functional.
▶ INTERVENTION WINDOW · NEXT 14 DAYS
CaseOutMatch%
Boeing 737 MAX · 2018FAIL73%
LEGO turnaround · 2003–17THRIVE67%
Adobe Creative Cloud · 2013THRIVE61%
Sears Holdings · 2005–18FAIL54%
Microsoft / Nadella · 2014THRIVE48%
Netflix streaming pivot · 2007–13THRIVE42%
Blockbuster · 2010FAIL38%
Apple / Jobs return · 1997THRIVE31%
Lehman Brothers · 2008FAIL24%
WeWork · 2019FAIL18%
Theranos · 2015FAIL12%
Enron · 2001FAIL9%
FTX · 2022FAIL6%
What-If SimulatorForward stress test · projected dB/dt
Press a scenario to simulate
Same V4 event, three different system states. The trigger is the same — only the driver changes. This is the traffic-ticket principle: the system state at the moment the trigger lands is what determines the outcome.
RestedCLEAN RECORD
Distance-to-CTZ0.71
CTZ ETA180+ days
Absorbed. Backfill via internal succession; trajectory unchanged.
Current3 PT FROM SUSP.
Distance-to-CTZ0.18
CTZ ETA~19 days
High risk. Three coupled CTZs within radius — V2e Sales, V5 succession, V1 AR groove.
DepletedSUSPENSION
Distance-to-CTZ0.04
CTZ ETA~5 days
Bifurcation likely. Five+ fuses inside single-event radius. Cascade to AR + Win/Loss + retention probable.
Pre-position · Current stateBackfill plan in 7 days · V5 succession audit · V2e protect for the bench. Closing the gap from Current toward Rested adds ~28 days to CTZ ETA.
Intervention Window CalendarWhere each lever has highest leverage · next 90 days
Engine-derived · not management-set
NOW · NEXT 14 DAYS
V2e Replenishment · Sales Division
Aggregate fuel reserves at 58% (▼ 1.4 over 90 days). Highest-ROI window opens before the next pitch cycle. Mechanism: load reduction + recovery cadence, not new hires.
⚡ HIGH LEVERAGE
DAYS 14 — 30
V5 Succession Audit · Sales VP role
Active scan of leadership bench depth. Quiet pre-positioning: who absorbs which priorities if V4 hits next quarter. Closes the failure-pattern gap most strongly.
⚡ HIGH LEVERAGE
DAYS 30 — 60
V1 PL redistribution · AR groove
AR is currently the load-bearing groove. Open a parallel attractor (Customer Retention) that absorbs PL when the AR groove is stressed. Prevents the Blockbuster pattern.
◆ MEDIUM
DAYS 30 — 90
V3 active scanning · DC commercial RE
Quarterly red-team session on macro V3. Treat dynamic environment as terrain, not threat. Inputs feed the simulator above.
◆ MEDIUM
DAYS 60 — 90
V4 pre-positioning · communications playbooks
Rehearsed responses to top-3 V4 events (key departure, missed quarter, RFP loss). Standing by means lower numerator amplification when triggers hit.
○ LOW (PREP)
Trust ContractWhat this engine will never do
Section 23 · Privacy & Compliance Architecture
∅
No content scanning
Slack, Teams, email, chat — never read by the engine. Only voluntary daily check-ins from the Wellness app.
⊘
No determinative use in employment
Engine outputs cannot be the basis of termination, promotion, compensation, or PIP decisions. Contractually prohibited.
⊗
No mandatory biometric
Wearables are opt-in only. No camera, no voice analysis, no fingerprint — anything BIPA-adjacent is off-limits.
⊕
No cross-tenant data movement
Colonial's data lives in its own logically isolated tenant. The engine learns from public case data, not customer data.
Compliance perimeter: ADA · NLRA · CCPA / CPRA · NY SHIELD · IL BIPA · EU/UK GDPR. Data integrity is the moat — surveillance-style competitors carry latent legal liability AND produce gameable data. Consent-first is not a constraint; it is the architecture.
The Bridgepattern detection across the dual state
Sales team dorsal spike began Monday — same day AR slipped 7 → 6. Pattern match: prior 3 occurrences of this co-movement led to AR drops of 8–12% within the following two weeks.
Recommended action: Run a Pause Protocol with the sales team before tomorrow's RFP pitch. Time-to-action: ~22 hours. Estimated AR-recovery delta if applied: +$31K.
The Operating Force Equation
How your OpsForce Composite is calculated
Your priority importance rankings drive the weights. The composite rises and falls in real time as scores, deadlines, and workforce regulation move.
Importance. The importance you assigned to each priority (1–10). High-importance items compound via the Po exponent — your top picks dominate the composite by design.
si(t)
Current Score. Live performance on each priority, from the operating system.
κ(Di)
Dollar Magnitude. Bigger-revenue priorities push harder on the composite.
τi(t)
Deadline Tension. An AR target due Friday weighs more on Wednesday than on Monday.
R(t)
Workforce Regulation. Comes directly from the right-panel Wellness equation. This is the coupling — Wellness leads Operations through this term.
Market Environment. Sector tailwind or headwind, seasonal factors.
ε(t)
Noise. The unpredicted — stochastic events outside the model.
The Coupling — why Wellness leads Operations
R(t) in the denominator is the output of the right-panel Wellness equation. When workforce regulation drops, R drops, the denominator shrinks, and your OpsForce Composite falls 24–48 hours later. The leading-indicator behavior is not a trend we observe — it is a mathematical consequence of how the two equations couple. Wellness leads Operations by design.
Why this equation works
Numerator
Strategic intent becomes mathematical weight. Importance rankings are raised to a power (Po), so high-importance priorities compound rather than just add. This mirrors how real organizations actually allocate cognitive bandwidth — leaders concentrate attention on the few that matter most, not equally across all eight. The dollar amplifier κ(Di) ties every priority to revenue or cost saved, which is what makes the composite CFO-defensible at every layer.
Denominator
The denominator captures resistance to performance. Time-to-deadline tension τ(t) and operational drag Φops both grow as the company encounters friction. But the load-bearing term is R(t) — workforce regulation. When teams are regulated, R is high, the denominator is large, and the composite is stable. When regulation collapses, R shrinks, the denominator shrinks, and the composite falls — even if priorities themselves haven't changed.
Coupling
R(t) is not a parameter — it is the output of the Wellness equation on the right panel. The two sides of the dashboard are one coupled dynamical system. This is why the leading-indicator behavior emerges automatically: regulation moves first because it appears inside the operations equation, not next to it. Polyvagal science says nervous-system state shifts in seconds; operational consequence shows up in days. The 24–48 hour lag is the integration time of the coupled system.
Stochastic
The noise term ε(t) keeps the model honest. Real organizations are not deterministic — markets shift, employees get sick, weather closes garages. The model does not pretend to predict every event. It predicts the structural moves: when regulation drops 1.0 points, expect operational drift of 0.3–0.7 points within 36 hours. The noise term absorbs everything outside that pattern.
Watch the coupling
Wellness drops first → Operations follow ~24 hours later
The teal line moves first. The brass line follows within ~24 hours. Same data, two equations, one coupled system. In Colonial's pilot, the system will demonstrate this pattern repeatedly — each operational drop preceded by a measurable workforce-regulation drop one to two days earlier. That is the predictive signal.
Prediction horizons
How far ahead OpsForce can see
24 hours is the floor. The further the system runs at Colonial, the further forward it sees — different mechanisms unlock at each horizon.
Day 1Week 1Month 13 Mo6 Mo1 Yr
Biological Lag
1–2 days
Available Day 1
Trend Velocity
3–7 days
After ~2 weeks
Cumulative Load
2–4 weeks
After ~6 weeks
Pattern Recognition
1–3 months
After ~6 months
Anticipatory
Event-driven
Available Day 1
The system gets smarter the longer it runs. By month 12 of the Colonial pilot, OpsForce will know your company's rhythms better than your management team — because it has watched every employee's nervous-system state across every operational cycle, and it remembers.