ICM meets PMS (Preventative Maintenance Systems)

Dang it

, your post "Left Of Bang: Smart Discipline or Over Engineering" got me thinking.

Your brother's journey from Marine to counterterrorism specialist, drawing from Left of Bang, nails a timeless truth: the real game is won (or lost) in the moments before the explosion, the ambush, or the breakdown. Training that only prepares you for "right of bang" leaves you playing catch-up in survival mode. Staying left means cultivating pattern recognition, baseline awareness, and the discipline to act on subtle anomalies. That's not paranoia—it's empowered foresight.

This resonates deeply when we map it onto structured systems like ICM (Interpreted Context Methodology) and PMS (Preventative Maintenance Systems).

ICM: INTERPRETED CONTEXT AS YOUR PERSONAL COMBAT PROFILER

ICM turns chaotic information flows into an interpretable, staged architecture—numbered folders, focused markdown contexts, and clear role definitions for AI (or human) agents. Instead of overwhelming the system (or yourself) with everything at once, you engineer context deliberately: isolate what matters for the current stage, reduce noise, and build repeatable workflows that let you "read the room" or the data before anomalies compound.

In Left of Bang terms, ICM is your Combat Hunter toolkit for the information battlefield. It helps you establish baselines (normal behavior in your projects, markets, or personal life), spot clusters of cues that don't fit, and intervene early. No more reactive firefighting after the "bang" of a failed launch, missed opportunity, or workflow collapse. It's smart discipline: structured enough to scale, flexible enough to adapt.

PMS: PREVENTATIVE MAINTENANCE FOR LIFE, WORK, AND SYSTEMS

PMS isn't just for ships or machinery—it's the operational heartbeat of staying left of bang in the physical and systemic world. Schedule the inspections, lubrication, and calibrations before the breakdown. Track intervals, document baselines, and act on early wear indicators.

Combine this with ICM and you get a meta-system: Use ICM to design the context for your decision-making, and PMS to execute the recurring disciplines that keep the machine (or your focus, health, business) running smoothly. Your brother's profiling domains—reading people, environments, and anomalies—translate beautifully here. Apply the same lens to your tools, habits, and teams: What are the pre-indicators of drift? Where is entropy creeping in?

The risk of overengineering is real, of course. Not every signal needs a full ICM folder structure, and not every asset demands daily PMS checks. The art is in calibration—using these frameworks as force multipliers for intuition, not replacements for it. Start with high-stakes areas (your core workflows, key relationships, critical assets) where a "bang" would hurt most. Build the muscle of baseline awareness there, then expand.

This is where discipline becomes liberating. Operating left of bang isn't about constant vigilance that burns you out—it's about engineered awareness and maintenance rhythms that create freedom, resilience, and decisive action when it counts.

Huge respect to your brother and the legacy of that mindset. In the AI age especially, those who master reading the pre-signals—whether in data, behavior, or systems—will thrive while others react. What's one area in your own work or life where you're experimenting with shifting further left of bang right now? I'd love to hear how ICM or PMS-inspired habits are playing out for you.

Here are some actionable prompts to help:

CORE INTEGRATION PROMPTS

PMS-to-ICM System Mapping "Act as an ICM architect. Take this PMS schedule [paste your current preventative maintenance checklist or intervals] and convert it into a full ICM structure. Create numbered context folders, define baseline states, early warning indicators (Left of Bang cues), and maintenance triggers. Output the complete folder architecture with markdown templates for each stage."
Daily/Weekly PMS ICM Context Builder "Using Interpreted Context Methodology, build a complete daily/weekly context pack for my PMS routines. Include: 1) Current baseline status, 2) Last maintenance log, 3) Upcoming scheduled tasks with intervals, 4) Anomaly detection checklist (what 'right of bang' looks like), and 5) Decision/action prompts. Structure everything in clean markdown with clear sections."
Preventative Maintenance as ICM Agent Role "Create an ICM-compatible AI agent role called 'PMS Guardian'. Define its system prompt so it operates Left of Bang: it tracks asset or workflow health, flags drift early, suggests calibrated maintenance, and maintains an interpreted context log. Include rules for escalation and documentation."

PRACTICAL APPLICATION PROMPTS

Asset/System Specific PMS → ICM "Apply PMS principles inside ICM for [specific area, e.g., my content production system / Notion workspace / business ops / personal health]. List all critical components, their current baseline, maintenance intervals, wear indicators, and build the corresponding ICM folder structure with context files."
Left of Bang Maintenance Dashboard "Design an ICM-based preventative maintenance dashboard in markdown. Include sections for: High-priority assets, trending indicators, scheduled vs. completed tasks, risk heat map (Left of Bang vs Right of Bang), and automated review prompts. Base it on these PMS items: [list them]."
Weekly ICM PMS Review Protocol "Create a repeatable weekly ICM review prompt for PMS adherence. The prompt should analyze last week’s logs, compare against baselines, identify subtle anomalies, recommend adjustments to intervals or contexts, and generate the next 7-day interpreted context package."

ADVANCED / SCALING PROMPTS

Full Lifecycle PMS in ICM "Map the entire preventative maintenance lifecycle (planning → inspection → intervention → documentation → review) into a staged ICM methodology. Provide templates for each phase with numbered contexts, role definitions, and decision trees that emphasize acting Left of Bang."
Cross-System PMS Integration "Help me integrate my existing PMS (tools: [list tools]) with ICM. Suggest how to turn raw maintenance data into rich interpreted contexts, including automated triggers, summary markdowns, and AI analysis prompts that surface emerging patterns before failure."
Calibration & Anti-Overengineering Prompt "Act as an ICM + PMS optimizer. Review this proposed system [paste your draft] and calibrate it: remove unnecessary complexity, strengthen Left of Bang detection, ensure maintenance intervals are realistic, and output a streamlined ICM folder structure with justified simplifications."
Personal Mastery Version "Translate PMS principles into a personal discipline ICM system for [habit/area, e.g., focus, fitness, learning, finances]. Build the full interpreted context framework including baseline establishment, daily/weekly maintenance rituals, early drift indicators, and recovery protocols."

QUICK ONE-SHOT PROMPT (MOST VERSATILE)

"PMS → ICM Bridge" "Convert my PMS practices into a robust Interpreted Context Methodology system. Focus on proactive (Left of Bang) discipline. Here is my current PMS: [paste details]. Output: 1) Folder/context hierarchy, 2) Key markdown templates, 3) Monitoring & alerting system, 4) Review cadence."

Copy, paste, and customize the bracketed sections with your own details for immediate results. These prompts turn abstract systems into concrete, repeatable workflows.

6 comments