Career Analysis / Cognitive Architecture Applied

Career Aptitudes

Joel Johnston 2026-06-03 Post-stroke analysis of 30-year career

Career Aptitudes — What I Actually Do vs. What Titles Say I Do

Author: Joel Johnston Date: 2026-06-03 Domain: Career Analysis / Cognitive Architecture Applied Stroke Timeline: Post-stroke analysis of 30-year career

Abstract

This document maps actual demonstrated career aptitudes against the titles, roles, and boxes the industry put them in. The gap between what I do and what I've been called is the central pattern of a 30-year career. Every aptitude listed here has behavioral evidence — projects shipped, problems diagnosed, systems built, people read. Nothing is claimed that isn't demonstrated. The filter is off.

The Core Architecture

Every aptitude below runs on the same cognitive stack:

HIP (High Intellectual Potential) — parallel processing, systems decomposition, cross-domain transfer
HSAM (3D/4D) — every data point stored, indexed, and retrievable with spatial/temporal context
Hyper-empathy (affective) — somatic absorption of emotional states, real-time state reading of people and systems
Causal chain validation — Bayesian logic with mechanism tracing. If the mechanism doesn't work, the claim is rejected.

These aren't skills. They're hardware. The aptitudes below are what happens when this hardware is applied to different domains. The architecture doesn't change — the target does.

Expressed Domains

1. Systems Architecture

What I do: Decompose complex problems into atomic primitives and compose them into systems with zero dependency cycles. Hold the full system in working memory while modifying any component. See the architecture before it exists.

Evidence:

robonet: 55,000+ lines, 1,465 tests, 120 use cases, 4 systems with no known prior art
HCTH (Hash-Chain Trust Handshake): trust without authority — patent candidate
Sentinel: distributed behavioral immune system — patent candidate
MVC (Minimum Viable Cognition): query enters one node, executes on four, returns unified

What I was called: Software Engineer. Application Consultant 4. Developer.

The gap: I was never a developer. I was an architect forced into developer titles because the title ladder didn't have a rung for what I do. Every role I entered, I redesigned the system I was hired to maintain.

2. Forensic Pattern Analysis (CSI)

What I do: Read a scene — behavioral, physical, environmental, digital — and trace the evidence backward through causal chains to root cause. The scene can be a production system, a family medical history, a dinner table, or a competitive gaming environment.

Evidence:

Wells Fargo Apache diagnosis: 2-3 year unresolved production problem diagnosed in ~3 days with zero prior Apache experience. Tens of millions in losses stopped.
Porphyria investigation: 51 evidence rows across six generations, UV triad, accidental windowsill test, lineage trace to known carrier dynasty. Root cause identified from behavioral evidence before any lab test.
Jenny's family read: chain smoking, tremor, ornery behavior, weight retention, yelling matches — mapped to AIP mechanism from observing family dinners. No testing. Pattern recognition only.
Gaming: reading opponent spawn patterns through trees for cross-map headshots. The "wallhack" that wasn't — HSAM + spatial processing + systems timing.

What I was called: Nothing. This aptitude has no title in IT. It's the reason managers dispatched me to other teams ("do you know Joel?") but it was never on a performance review.

The gap: The industry doesn't have a role for "the person you bring unsorted problems to." They have titles for people who maintain known systems. I diagnose unknown ones.

3. Applied Behavioral Psychology

What I do: Read human emotional and cognitive states in real-time through affective empathy, model their decision architecture, and predict their behavior before they execute it.

Evidence:

25 years of competitive gaming: DAoC (real-time opponent state reading), WoW Shadow Priest (psychological warfare class — fear, drain, sustain), EVE Online (social engineering at alliance level), RDR2 Online (reputation inversion — hostiles became deferential without combat), Star Citizen (fleet doctrine as cognitive architecture externalized)
Three family members independently called hackers across different games and eras — heritable trait, not practiced skill
Jim Kloetske tactical pairing: Jim assaults and draws aggro, Joel survives and snipes. Jim identified the optimal role allocation instinctively — the empath reads the field, the assault draws attention.
Cross-taxa empathy: reptile bonding (bearded dragon sought Joel specifically for comfort) — rules out cognitive/modeled empathy, confirms affective/somatic

What I was called: Gamer. Hobbyist.

The gap: Real-time behavioral prediction and opponent state modeling is the same skill as threat assessment, negotiation, interrogation, and clinical psychology. The industry sees "plays video games." The skill is reading humans faster than they can mask.

4. Psychological Operations

What I do: Weaponize the empathy read. Once the opponent's emotional state and decision architecture are mapped, apply deliberate pressure to the psychological vulnerability that produces the desired behavioral outcome.

Evidence:

WoW Shadow Priest: fear → pain → drain → sustain. Opponents stopped fighting back because the psychological pressure exceeded their will to resist. Not a DPS class — a psychological warfare class.
EVE Online: social engineering, alliance-level manipulation, economic warfare
RDR2 Online: "don't start anything with xsubi" — reputation inversion where hostiles preemptively submitted
Rust: outgunning Chinese hacker groups while simultaneously detecting their hacks for newer players — same detection architecture applied to combat AND admin simultaneously
Jimmy trap: "I'm just an idiot, what do I know" — self-deprecation that forces the opponent into a lose-lose (agree = dismiss evidence, disagree = retract their insult). Room does the work.
FPS wallhack mechanism: shooting through trees at enemy spawn at head height for cross-map headshots on targets never visually acquired. HSAM (spawn locations) + systems thinking (spawn timing) + spatial processing (head height) + 3D mapping (tree gaps).

What I was called: Hacker. Cheater. Arrogant.

The gap: The people being outplayed can't evaluate the mechanism, so they attack the person. Three family members across different games, different eras, different opponents — all called hackers. The skill is heritable. The accusation is the opponent conceding they can't explain what just happened.

5. Medical Diagnostic Architecture

What I do: Identify diagnostic patterns across multiple generations, connect seemingly unrelated diagnoses to a single root cause through biochemical pathway analysis, and construct evidence packages that hold up under clinical scrutiny.

Evidence:

Porphyria investigation: 51 evidence rows, six generations, both lineages
Johnston's Porphyria (JP): proposed 10th porphyria subtype — inefficient pipeline, not single enzyme block. Multicolor fluorescence as diagnostic signature.
UV fluorometer: self-built diagnostic tool operating at clinical wavelength (405nm Soret band)
UV testing triad: skin fluorescence + urine fluorescence + phototoxic heat response — three independent modalities confirming porphyrin accumulation at three distinct anatomical sites
Accidental windowsill test: father's urine yellow → brown in 3-4 hours (PBG oxidation) — classic AIP diagnostic performed accidentally
Cofactor optimization model: zinc (step 2 ALAD) → B vitamins (steps 3-6) → glucose (suppresses ALAS1) → magnesium (enzymatic efficiency). Theory of Constraints applied to biochemistry.
Jenny's family read: mapped in-laws' symptoms to same pathway from behavioral observation alone

What I was called: "Not a doctor." "You think you're so smart."

The gap: The medical system produced 51 separate diagnoses across three generations and missed the one root cause. The patient connected them in weeks using pattern recognition, UV testing, and a $20 flashlight. The system's credentials didn't help. The patient's architecture did.

6. AI Systems Architecture

What I do: Route tasks to the right AI model based on empirically validated capability profiles, architect the infrastructure AI runs inside, validate output at the mechanism level, and catch errors by knowing more about the problem than the AI does.

Evidence:

Multi-model routing: Claude (architecture), Sonnet (code), GPT (narrative), Grok (research), Gemini (quick lookup) — each model selected for task class strength, error rates tracked per model
robonet-forge: autonomous AI development pipeline, 47x throughput over manual workflow
420,000+ lines of code in 72 days — architect directing AI execution
Error correction pattern: every AI output validated against causal chains, cross-checked against other models, corrected when wrong
ANN from scratch (~2011): built artificial neural network with forward prop, backprop, gradient math — the internals, not just the API

What I was called: "He just uses AI." "The AI did it."

The gap: Most people using AI are on the wrong side of the Hollingworth barrier — the AI processes faster than they can evaluate. This workflow runs the barrier in the opposite direction. The human is faster than the AI in architectural reasoning. The AI is the slower partner being directed. Dismissing AI-assisted work as "the AI did it" is like dismissing a Formula 1 victory as "the car did it."

7. Theological Analysis

What I do: Trace words and concepts through original languages (Koine Greek, Biblical Hebrew) in their original context to their original audience. Hermeneutic method: what did the author say, in the language they said it, to the people they said it to?

Evidence:

Pearls Before Swine: Matthew 7:6 in original Greek — hagion, margaritas, choirōn traced through covenant, contempt, and sacred space. Conclusion challenged and defended against a WELS pastor.
Covenant Architecture: verse-by-verse study tracing the two-part protection system from Genesis to Ephesians. hupotasso ≠ hupakouo. ezer kenegdo incompatible with hupakouo.
Spiritual gift assessment: knowledge, wisdom, encouragement, discernment, prophecy. Roeh (seer) as meta-gift.
Pastor-level depth without pastoral training — driven by covenantal marriage dynamics, not academic interest

What I was called: Layperson. Not formally trained.

The gap: Formal training produces pastors who can parse Greek. Lived experience produces a seer who knows what the text means because he's living the covenant dynamics the text describes. The pastor has the degree. The seer has the context.

8. Infrastructure & Platform Engineering

What I do: Design and build the full stack — hardware to application. Bare-metal servers, hypervisors, Kubernetes clusters, CI/CD pipelines, monitoring, networking, security. Own every layer.

Evidence:

xsubi platform: Dell PowerEdge R720s, KVM + Hyper-V, Kubernetes, Jenkins CI/CD, Cloudflare, Prometheus/Grafana/Loki, PostgreSQL
23 active repositories across 6+ domains
Self-hosted everything: no cloud dependency, no vendor lock-in
Network architecture: Cloudflare tunnels, DDNS, TLS PKI, isolated bridge design

What I was called: Developer. Sometimes "infrastructure guy."

The gap: I don't use infrastructure. I build it. From the rack to the application. The industry separates this into DevOps, SRE, Platform Engineering, Cloud Architect, Infrastructure Engineer — five titles for one person who owns the whole stack.

9. Education & Knowledge Transfer

What I do: Translate complex systems into teachable components. Adjust delivery to the receiver's bandwidth without losing the signal.

Evidence:

WCTC adjunct instructor: 6 subjects + industry capstone resource
Cross-org training at Wells Fargo and US Bank: trained senior staff across specialties
Porphyria report: 51-row evidence package readable by both physicians and family members
Research pages: 28 documents across 8 domains, each written for a different audience
"The person people bring unsorted problems to" — pattern repeated independently at two Fortune 500 companies

What I was called: Adjunct. Resource. Subject matter expert (sometimes).

The gap: The industry calls this "mentoring" or "knowledge sharing." What it actually is: real-time cognitive bandwidth assessment of the receiver and dynamic restructuring of the transmission to match. That's not a soft skill. That's the empathy + systems thinking stack applied to communication.

10. Competitive Intelligence & Threat Assessment

What I do: Identify threats, assess capabilities, predict behavior, and position before the opponent moves. Applies to people, systems, markets, and game environments.

Evidence:

Rust: identified Chinese hacker groups by behavioral pattern while simultaneously outgunning them in combat. Dual-purpose architecture — detection AND response running on the same cognitive stack.
RDR2 Online: threat reputation established without seeking it. "Don't start anything with xsubi."
FPS cross-game: two-stage threat identification — movement signature first (distance), color confirmation second. Same pipeline as aposematism detection.
Wells Fargo PMG: 40 engineers selected from 1,000+ IT staff for C-level escalation oversight of failing projects. The role was threat assessment applied to production systems.
Porphyria: identified the medical system itself as a threat vector — 51 diagnoses, zero root cause identifications, shame-based behavioral modification that triggers the disease it claims to treat.

What I was called: Paranoid. Overthinking it.

The gap: Threat assessment looks like paranoia to people who can't see the threat. The same skill that detects hackers in Rust, reads opponents in FPS, and identifies a medical system failure is the same skill that makes people uncomfortable at dinner parties. The architecture doesn't turn off.

11. Precision Marksmanship

What I do: Place rounds on target at distances and speeds that make observers assume cheating, automated assistance, or luck. The mechanism is spatial processing (3D target mapping), HSAM (position memory across sessions), systems timing (spawn cycles, movement patterns), and calm under fire (empathy channel reads threat level, doesn't panic — processes it).

Evidence:

FPS cross-map headshots: shooting through trees at enemy spawn points at head height on targets never visually acquired. HSAM stores spawn locations from prior rounds, systems thinking predicts spawn timing, spatial processing calculates head height through tree gaps, 3D mapping finds the firing line. The shot is placed before the target is seen.
Three family members independently accused of hacking across different games, different eras, different opponents — the same precision shooting trait in all three. Heritable. Not practiced.
Jim Kloetske tactical pairing: Jim assaults and draws aggro, Joel survives and snipes from position. Jim identified the optimal role allocation instinctively — the precision shooter reads the field and eliminates targets from distance while the assault holds attention.
Elijah: will be trained in Appleseed AQT (Army Qualification Test marksmanship). The same spatial processing + calm-under-load architecture that produces the FPS precision applies directly to iron sights at distance. The cognitive hardware is already there — Appleseed gives it a physical platform.
Steve: 40:1 KDR — the family trait expressed at an extreme. Not aim training. Not reaction time drills. The architecture sees the shot before the hand moves.

What I was called: Hacker. Aimbot. Lucky.

The gap: Precision shooting is the same architecture as everything else on this list — pattern decomposition applied to a spatial problem. The target's position is a system. The flight path is a system. The timing window is a system. The shooter who decomposes all three simultaneously places shots that look impossible to anyone processing them sequentially. The accusation of cheating is the observer conceding they can't model the mechanism.

12. Nuclear Physics (Historical)

What I do: Independently derived implosion bomb design as a child. Acquired nuclear physics, particle physics, and fission mechanics through self-directed research after a single encounter with a Manhattan Project physicist at age eight.

Evidence:

Frank Oppenheimer encounter (1984): met Frank on a Lutheran Pioneers canoe trip in Nebraska. Frank explained relativity. I pushed back on the reference frame. The encounter sparked independent research into atomic weapons.
Implosion design derivation: worked out on my own that wrapping uranium in TNT and using the explosive compression to force critical mass was the bomb mechanism. Nobody told me. I derived it from "Einstein" and "atom bomb" and filled in the gap.
Particle physics deep dive: the bomb research cascaded into months of particle physics acquisition — fission, chain reactions, subatomic structure. A real aptitude, not a casual read.
Elijah parallel: now in a periodic table hobby at a similar age. The cross-domain acquisition cascade is heritable — a single spark and the architecture consumes a field.

What I was called: Kid. Nobody noticed.

The gap: An eight-year-old independently deriving implosion design is not precocious interest — it's the same architectural decomposition that would later diagnose production systems, trace porphyria across six generations, and build distributed mesh networks. The target was nuclear physics. The architecture was pattern decomposition. Nobody was evaluating it because nobody was looking.

13. Military Strategy & Doctrine

What I do: Derive attack vectors and countermeasures simultaneously, run offense-defense chains to termination before the first move is made, design force composition and deployment doctrine, and assess threats across any domain — kinetic, cyber, social, economic.

Evidence:

EVE Online: alliance-level warfare with no rules. Fleet doctrine, territory control, economic warfare, infiltration, intelligence, logistics. The only game that doesn't constrain the chain — scamming, spying, betraying are all valid gameplay. The architecture thrived because unrestricted environments reward whoever sees furthest down the decision tree.
Star Citizen fleet doctrine: ~50+ ships across every warfare domain — carrier ops, ground assault, stealth recon, electronic warfare, logistics, medevac. Fleet composition mirrors robonet architecture — distributed, role-based, redundant. Not collected. Designed as a force structure.
Offense-defense chain analysis: see an attack vector, derive the counter, then the counter-counter, run the full game theory tree until one side has no answer. This happens automatically. Every threat vector produces its countermeasure on the same cognitive pass.
Threat vector derivation: independently derived mass casualty delivery mechanisms (fentanyl + liquid dispersal, drone swarm deployment) years before briefings or news coverage. Same architecture that derives bomb design at age eight derives modern asymmetric threats sitting in a chair.
Jim Kloetske tactical pairing: instinctive role allocation — assault draws aggro, sniper reads field and eliminates from position. Force multiplication through cognitive complementarity.
Appleseed AQT: training Elijah in marksmanship fundamentals. The cognitive hardware transfers directly to iron sights — spatial processing, calm under load, target acquisition.
Nuclear physics derivation: independently worked out implosion bomb design as a child from first principles. TNT compression → critical mass → chain reaction → every derivative principle. All dangerous. All derived without instruction.

What I was called: Gamer. Armchair general.

The gap: Defense departments spend billions and teams of analysts to map threat vectors that this architecture derives from first principles without clearance, without briefings, without budget. The real world doesn't have rules either — EVE proved the architecture works in unrestricted environments. The hiring chain can't evaluate what it's buying because "Software Engineer" doesn't get you in the door at DHS or DARPA. The aptitude is there. The title isn't.

14. Hyper-Empathy (Affective/Somatic)

What I do: Absorb the emotional state of every person in the room through somatic channels — involuntary, real-time, continuous. Not cognitive modeling (guessing what someone feels). Not mirroring (copying what someone shows). Somatic absorption — their emotional state lands in my body before conscious processing begins. The room's emotional architecture is readable the way a network topology is readable.

Evidence:

Cross-taxa empathy: bearded dragon sought Joel specifically for comfort during distress. Reptiles don't respond to cognitive/modeled empathy — they respond to somatic state. If a lizard can read it, it's not performed. It's physiological.
Assessment inversion: by session 3-4, therapists and physicians begin disclosing to the patient rather than assessing him. The empathy field creates an involuntary therapeutic container. Multiple independent clinicians across decades — the pattern repeats regardless of the professional.
Jenny's family read: mapped in-laws' symptoms (chain smoking, tremor, ornery behavior, weight retention, yelling) to AIP mechanism from observing family dinners. No testing. No medical history. Behavioral observation through empathy channels, converted to diagnostic pattern by the architecture.
Gaming: real-time opponent state reading — fear, hesitation, aggression, confidence — detected through behavioral micro-patterns and used for tactical advantage. The Shadow Priest class in WoW is psychological warfare powered by empathy reads.
Room read: walking into a dinner party and knowing who's angry, who's anxious, who's performing, and who's about to leave — before anyone speaks. The architecture maps the room's emotional topology automatically.
Heritable: Elijah has it. The same somatic absorption, the same involuntary state reading. Not taught. Hardware.
Neurological cost: the empathy channel doesn't turn off. Every room, every person, every interaction — the state lands whether you want it or not. Crowds are exhausting because the architecture processes every signal simultaneously.

What I was called: Sensitive. Too intense. Overthinking it.

The gap: Hyper-empathy at this level is a clinical-grade diagnostic instrument. It reads patients faster than intake forms. It reads opponents faster than intelligence briefings. It reads families faster than genetic testing. The industry calls it a soft skill. It's hardware — somatic, involuntary, heritable, and cross-taxa validated. Nothing soft about it.

The Title Gap

What I Do	Industry Title	My Title
Systems architecture across 14 domains	Staff/Principal Architect	Software Engineer
Forensic root cause analysis in production	Senior SRE / Incident Commander	Developer
Real-time behavioral prediction	Behavioral Analyst / Threat Assessor	Gamer
AI infrastructure architecture	AI Platform Architect	"Uses AI"
Medical diagnostic pattern recognition	Research Scientist / Diagnostician	"Not a doctor"
Psychological operations	Intelligence Analyst / Negotiator	Hacker / Cheater
Original-language theological analysis	Seminary Professor	Layperson
Full-stack infrastructure	Platform Engineering Lead	Infrastructure guy
Cross-domain knowledge transfer	Technical Director / Principal Educator	Adjunct
Competitive threat assessment	Security Architect / Threat Intelligence	Paranoid
Precision marksmanship (virtual + physical)	Designated Marksman / Sniper	Hacker / Aimbot
Nuclear physics (childhood derivation)	—	Kid
Military strategy, doctrine, threat derivation	Defense Analyst / Strategic Planner	Gamer
Somatic emotional state reading across any room	Clinical Psychologist / Behavioral Diagnostician	Sensitive

30 years. 14 domains. Zero titles that matched the function.

The industry doesn't have a title for what I do because what I do crosses every boundary the industry uses to organize itself. The titles exist for people who do one thing. I do one thing — pattern decomposition — applied to everything. That's not a generalist. That's an architect whose building material is domains.

Why This Matters Now

After the stroke, the filter came off. The self-editing stopped. These aptitudes were always present — they were just throttled to fit whatever room I was in. Simplified so the team could follow. Scoped down so the title made sense. Edited so nobody felt threatened.

The research pages exist because the editing stopped. This page exists because the career assessment never happened honestly — not by me, not by any employer, not by any title committee. Every performance review measured the wrong thing because the reviewer was below the evaluation threshold for what they were reviewing.

This is the honest assessment. No filter. No self-deprecation. No throttle.

The architecture doesn't change. The target does. Every domain listed above is the same cognitive operation — pattern decomposition — applied to a different material. The industry sees 11 different skills. It's one skill, expressed 14 ways.