Timothy Wheels#
Systems Architect. Sovereign Operator.
Infrastructure that stays online - physical, digital, cognitive.
Operational Routing#
About
A 20-year circuit from Chef to IT Operations - where pressure, precision, and uptime were learned the hard way.
Frameworks
RME reliability models, threat analysis, and failure-mode design - built for real systems, not slide decks.
Awareness In Action
Live process health checks and systemic audits - spotting drift before it becomes downtime.
CYW Framework
An introduction to the Control Your World methodology: structure, agency, and operational clarity.
Poetry
Spoken-word performances exploring the friction between humans, machines, and survival.
Deep Specs#
Looking for the core OS?
Start at /deep-specs/ for the architectural overview, then visit https://cyw-os.com for the live deployment.
Virgil OS loop: Observe → Escalate → Document → Resume.
Why This Exists Operations break down when every decision is treated as urgent and handled by whoever is available. Reliable systems route the right decisions to the right specialists and enforce verification steps before deployment.
This protocol keeps decisions traceable, auditable, and aligned with uptime.
The Routing Stack Level 1: Frontline Triage
Classify the issue, isolate impact, and prevent escalation.
Level 2: Domain Specialist
Assign to the tech with the most relevant system context.
...
The Purpose of Gates Every system needs checkpoints that stop defects from moving downstream. Quality gates enforce the pause required to verify safety, stability, and traceability.
These gates are designed to fit within active operations without slowing momentum.
The Four Gate Model Gate 1: Pre-Work Readiness
Tools, parts, and lockout steps confirmed. No improvisation.
Gate 2: Change Integrity
Work completed to spec. Torque, alignment, and calibration verified.
Gate 3: Operational Validation
System runs under real load without alarms or drift.
...
UX-audited. Updated quarterly. Last updated: 2026-01-31
Talking Points Reliability is the outcome of disciplined preventative maintenance. A clear failure chain beats a vague root cause. Every sensor is a signal, not a suggestion. The Systems Translation Matrix: Bridging IT and RME Industrial Hardware Term Network Engineering Equivalent Operational Logic (The “Why”) Photo-Eye / Sensor Inbound Packet / Ping A sensor trigger is a data packet arriving at an interface. If the ping is dropped, the system loses visibility of the asset. PLC (Programmable Logic Controller) Router / Gateway The PLC is the brain of the subnet. It routes physical inputs to outputs based on pre-defined logic. Conveyor Encoder Clock Rate / Synchronization Just as bit-timing prevents collisions, encoder pulses ensure physical packets do not collide on the belt. Solenoid / Actuator Switch Port / Execution The physical act of diverting a package is a switching decision. The solenoid is the physical port that opens to route traffic. E-Stop / Interlock Firewall / Kill Switch An E-Stop is a hardware-level drop-all rule. It is the ultimate safety protocol. VFD (Variable Frequency Drive) Bandwidth / Throughput Control A VFD regulates motor speed like QoS regulates traffic flow. It prevents buffer bloat at induction points. Strategic Application “I treat a Sortation System as a physical LAN. The packages are the packets, the conveyor is the medium, and the PLC is the router. When throughput drops, I do not just look for a mechanical jam; I look for where the signal-to-noise ratio in the sensor logic is failing.”
...
UX-audited. Updated quarterly. Last updated: 2025-01-31
The first instinct when something breaks is to fix it. The second instinct - the one that separates operators from engineers - is to understand why it broke.
I learned this lesson in a kitchen at 7 PM on a Saturday. The salamander stopped heating. The line cook’s instinct: crank it higher. My instinct, learned from watching equipment fail too many times: check the pilot light first. Thirty seconds of diagnosis saved us from replacing a working thermostat or, worse, flooding the kitchen with unburned gas.
...
UX-audited. Updated quarterly. Last updated: 2025-01-31
The first time my deployment pipeline failed silently, I didn’t know for three days.
The site loaded. Pages rendered. Everything looked fine. But somewhere between my local build and the CDN, a file had been modified - cached incorrectly, served stale, hash mismatch invisible. I only discovered it when a reader emailed asking why a page showed outdated content.
That’s when I understood: “it works” is not the same as “it’s correct.”
...