// Obsidiancloud — Chad Dutcher's resume site, deployable build.
// Fullscreen, responsive, drawer pinned to viewport.
const CHAD = {
name: "Chad Dutcher",
alias: "Obsidian",
domain: "obsidiancloud.org",
title: "IT Infrastructure & Cloud Engineer",
email: "chad.obsidiancloud@gmail.com",
linkedin: "https://www.linkedin.com/in/chad-dutcher-1a280892/",
github: "https://github.com/RavenObsidianCloud",
resume: "resume.pdf",
location: "Fresno/Clovis CA · Seattle · Remote",
status: "Open to work",
eyebrow: "IT Infrastructure · Cloud Engineering · AI Systems",
sub: "T3 workstation tech turned cloud builder.\nI make infrastructure that actually holds.",
phone: "559-649-8355",
tagline:
"Eight years in healthcare IT — six at Tier 3 supporting 1,500+ users across 30+ clinical sites at Santé Health System. Now deep in GCP, Python automation, and local AI — building things that work in production, not just demos. Air Force veteran. Currently open to infrastructure and cloud roles in Fresno/Clovis, Seattle, or remote.",
};
const EXPERTISE = [
{
id: "infra", kicker: "Core", title: "Workstation & Infrastructure",
desc: "Tier 3 support for 1,500+ users across 30+ clinical sites. Epic & NextGen EHR, Imprivata SSO, AD/SCCM/Intune, hardware lifecycle, and full facility build-outs in HIPAA-compliant environments.",
story: {
lede: "I spent six years as the person other techs called when the ticket wouldn't close.",
paragraphs: [
"At Tier 3, the easy problems have already been ruled out by the time the ticket reaches you. What's left are the network of small contradictions — the imaging workstation that drops AD trust every fourth reboot, the SCCM task sequence that fails on one OU but not the others, the badge reader that works in the morning and dies after 2pm.",
"I came to love this work because it rewards reading carefully. Logs over guesses. Patterns over hunches. Documenting the fix so the Tier 1 desk can close the next one without me — at Santé I mentored a team of four Tier 1 techs on troubleshooting methodology and ticket documentation.",
"By the end of my time at Santé I was the escalation point for workstation, imaging, EHR (Epic, NextGen) and hardware across 30+ clinical sites — 1,500+ users in clinical environments where downtime has a price tag in patient minutes."
],
stack: ["Epic EHR", "NextGen EHR", "Imprivata OneSign", "Active Directory", "Group Policy", "SCCM / Intune", "O365 Admin", "HIPAA", "Hardware lifecycle", "Structured cabling"],
proof: [
{ value: "1,500+", label: "Users supported" },
{ value: "30+", label: "Clinical sites" },
{ value: "6yrs", label: "Tier 3 at Santé" },
],
},
},
{
id: "cloud", kicker: "Cloud", title: "GCP & Cloud Engineering",
desc: "GCP Associate Cloud Engineer in progress (June 2026). Terraform, serverless architecture, Conversational Agents, Compute Engine, hands-on with 60+ labs.",
story: {
lede: "Cloud isn't a different job. It's the same discipline at a different blast radius.",
paragraphs: [
"I'm working toward the GCP Associate Cloud Engineer exam in June 2026 — but I learn by building, so the cert is the receipt, not the goal. The work that produced it is in my GitHub: a Terraform-provisioned TeamSpeak server, a GCP Conversational Agents phone system, a half-dozen Compute Engine + Cloud Functions experiments.",
"What I'm chasing is fluency: writing the infra-as-code first, picking the right compute primitive for the workload, sizing for cost not for ego, and leaving the next person a README they can actually use.",
"60+ hands-on labs and counting. The TeamSpeak project is the portfolio piece — start with a problem, end with a deployable artefact and a teardown script."
],
stack: ["GCP", "Terraform", "Compute Engine", "Cloud Functions", "Conversational Agents", "Firestore", "VPC / Firewall", "IAM"],
proof: [
{ value: "Jun 2026", label: "GCP ACE target" },
{ value: "60+", label: "Hands-on labs" },
{ value: "IaC", label: "Terraform-first" },
],
},
},
{
id: "ai", kicker: "Automation", title: "Python & AI Pipelines",
desc: "Production Python agent tools, local LLM pipelines with Ollama/Qwen, ticket triage automation. Runs on Pop!_OS with AMD 7900 XTX.",
story: {
lede: "Most AI demos break on Monday. I build the boring version that doesn't.",
paragraphs: [
"My home stack runs Ollama with Qwen 3 8B and 32B on an AMD 7900 XTX under Pop!_OS — and on top of it, four Python tools I actually use: agent.py for general triage, agent-heavy.py for the longer-context work, triage.py for ticket classification, and ticket_queue.py for the queue itself.",
"The point isn't the model. It's the loop around the model: prompts versioned in git, JSON schemas the agent has to obey, structured logs of every call, fallbacks when a tool errors. The same hygiene I'd apply to any other production service.",
"When I pitched Claude Enterprise adoption to IT leadership at Santé, the deck wasn't about how clever the model was. It was about which tickets we could safely automate, how we'd measure regret, and what the rollback plan looked like."
],
stack: ["Python", "Ollama", "Qwen 3 8B / 32B", "Pop!_OS", "AMD 7900 XTX", "Pydantic", "Tool use / function calling"],
proof: [
{ value: "4", label: "Production agents" },
{ value: "Local", label: "On-prem inference" },
{ value: "Live", label: "Daily-driver use" },
],
},
},
{
id: "veteran", kicker: "Security", title: "Veteran · Cleared",
desc: "USAF Security Forces. Inactive Secret clearance eligible for reinstatement. Process-driven, high-stakes-environment mindset.",
story: {
lede: "The Air Force taught me to slow down in the moments that matter most.",
paragraphs: [
"USAF Security Forces, Sep 2007 – Jan 2009 (A1C) — base security, access control, and law enforcement operations. The work shaped a habit of mind I still rely on every day in IT: follow the procedure, log the action, communicate with your team, escalate cleanly.",
"I held a Secret clearance during my service. It's now inactive, but eligible for reinstatement. That history matters for roles involving regulated data, healthcare compliance, government work, or any environment where the cost of a misstep is measured in something other than a Jira ticket."
],
stack: ["USAF Security Forces", "Law enforcement", "Procedural discipline", "Team coordination", "Inactive Secret clearance"],
proof: [
{ value: "USAF", label: "Honorable service" },
{ value: "Secret", label: "Inactive · reinstatable" },
{ value: "HIPAA", label: "Healthcare environment" },
],
},
},
];
const PROJECTS = [
{
id: "agent-pipeline", type: "Python · Local AI", title: "AI Agent Pipeline",
desc: "Four production Python tools — agent.py, agent-heavy.py, triage.py, ticket_queue.py — running on a local Ollama stack with Qwen 3 8B/32B. Built for real ticket triage and queue management workflows.",
github: "https://github.com/RavenObsidianCloud/TicketAgent",
story: {
lede: "A local-first agent stack that actually closes tickets.",
problem: "Help desk queues fill up faster than humans can categorise them. Most of the routing decisions are mechanical — but the cost of getting one wrong is real, so blind automation isn't safe.",
approach: "Four focused tools rather than one mega-agent. Each one does a single job, exposes a JSON contract, and writes structured logs. The agents call into a local Ollama instance running Qwen 3 — no data leaves the machine.",
details: [
"agent.py — general-purpose triage with tool calling",
"agent-heavy.py — long-context analyses and summaries",
"triage.py — classification with confidence + reasons",
"ticket_queue.py — queue state, pickup, deadlines",
],
stack: ["Python 3", "Ollama", "Qwen 3 8B / 32B", "Pydantic schemas", "structlog", "Local-first"],
learned: "Smaller, well-scoped agents beat one big agent every time. The schema is the product.",
},
},
{
id: "call-agent", type: "Dialogflow CX · Santé HQ", title: "AI Call-Routing Prototype",
desc: "Dialogflow CX call-routing solution developed at Santé Health System targeting the claims and customer help departments at HQ. Phased rollout designed to deflect routine call volume from front-desk staff before handing off to a human.",
github: "https://github.com/RavenObsidianCloud/AI-Call-Agent",
story: {
lede: "A phone tree, but it actually listens.",
problem: "Santé's claims and customer help departments at HQ were spending hours a day on routine inbound calls — eligibility lookups, hours, basic routing — that could have been triaged by a well-trained agent before reaching a human.",
approach: "Built on Dialogflow CX (now Google Conversational Agents). Designed as a phased rollout: start with the easiest, lowest-risk call categories, measure deflection rate and caller satisfaction, expand intents from there. Webhook fulfillment for live data lookups, and a clean blind-transfer to a human whenever the agent isn't confident.",
details: [
"Built for Santé HQ — claims & customer help departments",
"Phased rollout: deflect the easy categories first, expand carefully",
"Webhook fulfillment for live data lookups",
"Blind transfer with context preserved when escalation needed",
],
stack: ["Dialogflow CX", "Google Conversational Agents", "Cloud Functions", "STT / TTS", "Python webhooks", "Phased rollout"],
learned: "The hardest part isn't the AI. It's modelling the knowledge base so the agent can look things up under time pressure — and being honest about which calls aren't safe to automate yet.",
},
},
{
id: "cvcrsa", type: "Client Build-Out · Healthcare", title: "CVCRSA Facility Expansion",
desc: "End-to-end IT build-out for the Central Valley Colon & Rectal Surgical Associates clinical expansion. Pre-construction conduit planning through completion, four enterprise contractors in play, completed on the August 2025 deadline.",
github: null,
images: [
{ src: "images/cvcrsa/02-rack.jpg", caption: "Patch panels and UPS, cabled and labelled. Plywood mount, ICC racks, Cat6 home runs." },
{ src: "images/cvcrsa/01-construction.jpg", caption: "Mid-build — ceiling tiles out, low-voltage conduit being pulled through the new space." },
{ src: "images/cvcrsa/03-desk-cables.jpg", caption: "Reception workstation under the hood — cable management hidden under a lift-up panel." },
{ src: "images/cvcrsa/04-finished-desk.jpg", caption: "Reception live and logging in. Dual-monitor diagnostic setup, ready for staff on day one." },
],
story: {
lede: "Walls don't move once they're up. Get the conduit right the first time.",
problem: "CVCRSA needed a complete IT build-out for a major clinical facility expansion — from gut/demolition through opening day. Hard deadline: August 2025. Multiple vendors. Healthcare meant no slack for downtime.",
approach: "Started in the pre-construction phase, working with the project planner to make sure low-voltage conduit was specified correctly for Cat cable runs before walls closed up. Then managed the physical hardware deployment and architected the network infrastructure for the expanded space. Kept four enterprise contractors aligned on a shared timeline.",
details: [
"Pre-construction conduit planning — Cat6 runs sized before drywall",
"Full hardware deployment across the expanded clinical suite",
"Network infrastructure architected for the new space",
"Vendor coordination: Christensen, PNA, Valley Telecom, Superior Design",
"Completed on the August 2025 deadline",
],
stack: ["Structured cabling (Cat5e/Cat6)", "Low-voltage conduit planning", "Network switch config", "Hardware procurement", "Vendor management"],
learned: "The IT scope of a clinical build-out is written before the building exists. Earn a seat at the pre-construction table.",
},
},
{
id: "thg-suite-106", type: "Client Build-Out · Healthcare", title: "THG Suite 106 Clinical Expansion",
desc: "Full technical furnishing of a newly constructed clinical suite at The Heart Group of Fresno — hardware procurement, multi-monitor diagnostic workstations, MFPs, wiring — plus a mid-project scope change from CT to ultrasound that meant adapting the entire hardware plan on the fly.",
github: null,
story: {
lede: "The suite's purpose changed halfway through. The deadline didn't.",
problem: "A newly constructed clinical suite at The Heart Group needed full technical furnishing — workstations, MFPs, wiring, peripherals — plus the relocation of specialized CVDX and sonographer staff with diagnostic equipment that can't take downtime.",
approach: "Procured and deployed multi-monitor diagnostic workstations, high-capacity MFPs, and the network wiring to support them. Coordinated directly with client-side vendors in addition to Santé's. When the suite's purpose shifted mid-project from a CT room to an ultrasound room, re-scoped hardware and infrastructure to match — without slipping the schedule.",
details: [
"Multi-monitor diagnostic workstations for clinical staff",
"Network wiring and high-capacity MFPs across the suite",
"Specialized staff relocation (CVDX team, sonographers)",
"Adapted hardware plan when scope changed from CT to ultrasound",
"Cross-organizational vendor management",
],
stack: ["Hardware procurement", "Diagnostic workstation setup", "Network wiring", "Vendor coordination", "Change management"],
learned: "Scope changes are inevitable in clinical construction. Build a hardware plan that can absorb a 'CT becomes ultrasound' phone call without slipping the deadline.",
},
},
{
id: "teamspeak-gcp", type: "GCP · Terraform", title: "TeamSpeak Server on GCP",
desc: "Terraform-provisioned TeamSpeak 3 server on Google Cloud Platform. Compute Engine, VPC networking, firewall rules, startup scripts, and cost management — built as a hands-on GCP ACE exam portfolio project.",
github: "https://github.com/RavenObsidianCloud/TeamSpeak-Server-on-GCP",
story: {
lede: "ACE prep as a real artefact, not just labs.",
problem: "Studying for a cloud cert by clicking through Qwiklabs is fine — but the gaps show up when you try to stand up something real, end to end, with cost ceilings.",
approach: "Built a complete TeamSpeak 3 deployment on GCP, provisioned entirely through Terraform. Compute Engine VM, custom VPC, firewall scoped to UDP voice ports, startup script that installs and configures TS3, plus teardown so the project's cost goes to zero when I'm not using it.",
details: [
"Terraform for everything — no console clicks",
"Cost-capped — teardown returns the project to $0",
"Startup script bootstraps TS3 from a clean image",
"Repo includes the full README so a recruiter can read it cold",
],
stack: ["Terraform", "GCP Compute Engine", "VPC / Firewall", "Bash startup scripts", "Cost management"],
learned: "Cert prep that produces a repo beats cert prep that produces a score. Both is best.",
},
},
{
id: "pesttrack", type: "PWA · Firebase · React", title: "PestTrack Pro",
desc: "Multi-branch pest control business management PWA. Role-based access for technicians and managers, inventory tracking, low-stock alerts, and monthly reporting. React + TypeScript + Firebase — deployed and live.",
github: "https://github.com/RavenObsidianCloud/pesttrack-pro",
story: {
lede: "Built for a real business, deployed and in use.",
problem: "A multi-branch pest control operation was tracking inventory and routes on paper and group chat. Techs needed something offline-friendly; managers needed a dashboard.",
approach: "A PWA so it installs to a phone and survives bad cell coverage. Firebase Auth with role-based rules — techs see their routes and stock, managers see everything. Inventory drops in real time, low-stock alerts go out automatically, monthly reports compile themselves.",
details: [
"Role-based access — tech / manager / owner",
"Offline-capable PWA installable on Android & iOS",
"Inventory + low-stock alerts",
"Monthly reporting baked in",
],
stack: ["React", "TypeScript", "Firebase Auth", "Firestore", "Firebase Hosting", "PWA / Service Worker"],
learned: "Real users don't care about your framework. They care that the app loads in the truck with one bar of signal.",
},
},
{
id: "homelab", type: "Self-Hosted · Linux", title: "obsidiancloud.org Home Stack",
desc: "Open WebUI via Tailscale Funnel, persistent local AI assistant, custom domain, Pop!_OS host with AMD 7900 XTX GPU. Daily-driver production setup.",
github: null,
story: {
lede: "The lab that pays for itself in skills.",
problem: "I wanted a real production environment for the agents and LLM work — not a laptop demo, not a paid cloud account I'd flinch at every month.",
approach: "A Pop!_OS workstation with an AMD 7900 XTX as the GPU, exposed safely over Tailscale Funnel under my own domain. Open WebUI as the front door, Ollama serving the models, and the agent tooling running locally with persistent context.",
details: [
"Tailscale Funnel for safe public exposure — no open ports",
"Open WebUI on top of Ollama",
"AMD 7900 XTX — 24GB VRAM, runs Qwen 3 32B comfortably",
"Cost: $0 / month after hardware",
],
stack: ["Pop!_OS", "Tailscale Funnel", "Open WebUI", "Ollama", "Nginx", "Custom domain"],
learned: "Owning the stack end-to-end is the fastest way to get fluent. Bills focus the mind.",
},
},
];
const EXPERIENCE = [
{
dates: ["Oct 2019 —", "Mar 2026"],
role: "Tier 3 / Workstation Tech III",
org: "Santé Health System · Fresno/Clovis, CA · 30+ clinical sites",
body: "Tier 3 endpoint and infrastructure support for 1,500+ users across 30+ clinical sites. Final escalation point for workstation, imaging, Epic/NextGen EHR, and hardware issues; mentored a Tier 1 team of four on troubleshooting methodology and ticket documentation. Led IT build-outs for the CVCRSA expansion and THG Suite 106. Managed enterprise Janus/Uniguest digital signage upgrade (v3 → v5) including ExchangeEWS calendar integration. Built Giva CC Autofill Chrome extension to speed up ticketing. Developed a Dialogflow CX AI call-routing prototype for claims and customer help. Pitched Claude Enterprise adoption to IT leadership. Started via Robert Half contract in Oct 2019, converted to full-time March 2020.",
tags: ["Epic EHR", "NextGen EHR", "Imprivata SSO", "Active Directory", "SCCM / Intune", "Healthcare IT", "Tier 3", "Dialogflow CX", "Chrome Extension Dev"],
},
{
dates: ["2026 —", "Present"],
role: "IT Consultant",
org: "Dr. Samia Ghaffar · New Practice Setup · Clovis, CA",
body: "Independent engagement scoping and standing up full IT infrastructure for a new medical practice. Network design, device procurement, cloud integration, and ongoing support.",
tags: ["Consulting", "Practice Setup", "Network Design", "Healthcare"],
},
{
dates: ["Jan 2018 —", "May 2019"],
role: "IT Support Specialist — EHR",
org: "Kings Medical Group · Hanford, CA",
body: "Technical support for the eClinicalWorks EHR platform across clinical sites — troubleshooting application issues and workflow disruptions, hardware and software installation, and onsite/remote support coordinated around patient-care hours.",
tags: ["eClinicalWorks", "EHR Support", "Hardware", "Clinical IT"],
},
{
dates: ["Sep 2007 —", "Jan 2009"],
role: "Security Forces Specialist (A1C)",
org: "United States Air Force",
body: "Base security, access control, and law enforcement operations. Developed high-pressure decision-making, procedural discipline, and team coordination under operational conditions. Held Secret clearance — now inactive, eligible for reinstatement.",
tags: ["Secret Clearance", "Law Enforcement", "Operations", "Veteran"],
},
];
const STACK = [
{ label: "GCP (ACE in progress)", featured: true },
{ label: "Python", featured: true },
{ label: "Terraform", featured: true },
{ label: "Epic EHR", featured: true },
{ label: "NextGen EHR", featured: true },
{ label: "eClinicalWorks" },
{ label: "Imprivata OneSign" },
{ label: "HIPAA" },
{ label: "Active Directory" }, { label: "Group Policy" },
{ label: "SCCM / Intune" }, { label: "O365 Admin" },
{ label: "Windows Server" }, { label: "Linux / Pop!_OS" },
{ label: "Networking" }, { label: "Structured Cabling" },
{ label: "Dialogflow CX" }, { label: "Conversational Agents" },
{ label: "Compute Engine" }, { label: "Cloud Functions" },
{ label: "Firebase" }, { label: "Ollama" },
{ label: "React" }, { label: "TypeScript" },
{ label: "Tailscale" }, { label: "Open WebUI" },
{ label: "Giva ITSM" }, { label: "Chrome Extension Dev" },
{ label: "Bash" }, { label: "Git" },
];
function Evolved() {
const [open, setOpen] = React.useState(null); // {kind, id}
React.useEffect(() => {
const onKey = (e) => { if (e.key === "Escape") setOpen(null); };
window.addEventListener("keydown", onKey);
return () => window.removeEventListener("keydown", onKey);
}, []);
// Lock body scroll when drawer is open
React.useEffect(() => {
document.body.style.overflow = open ? "hidden" : "";
return () => { document.body.style.overflow = ""; };
}, [open]);
const openItem = open
? open.kind === "expertise"
? EXPERTISE.find(x => x.id === open.id)
: PROJECTS.find(x => x.id === open.id)
: null;
return (
