Bag of Holding — Constraint-Governed Knowledge Workbench
A local-first knowledge operating system for governed documents, reversible lifecycle management, and review-safe LLM integration. Built for environments where decisions carry consequence.
/public/assets/patient-8bit.png.
Healthcare AI Solutions Analyst | Clinical Workflow & Governance Systems
I work at the boundary between clinical operations and technical systems. My work translates frontline workflow, documentation burden, and operational ambiguity into structured tools, safer AI touchpoints, and systems that can be evaluated instead of merely trusted.
Email: paultpeck@gmail.com
Location: Columbus, OH (remote or hybrid preferred)
Location: Columbus, OH
Work: Remote or hybrid, healthcare technology, informatics, workflow, documentation, AI governance
I take a small number of workflow and documentation consults. I'm not an agency and I'm not selling a finished product — if your problem looks like the ones on this chart, write me.
Start a conversationTL;DR: Clinical triage, emergency care, rehab operations, EHR documentation, local-first software, governed AI, biological systems, ecommerce infrastructure.
My work is systems-first because my background has been systems-heavy. I have worked inside clinical environments where unclear handoffs create risk, remote workflows where documentation becomes infrastructure, and technical projects where a system is only useful if it behaves safely under constraint.
Most recent clinical work: remote triage, chronic care, and documentation-heavy healthcare operations.
Earlier acute and post-acute work shaped how I think about handoffs, failure modes, and cognitive load.
In parallel with nursing: software that supports judgment without becoming unaccountable infrastructure.
Work outside traditional software categories that informs how I think about resilience, feedback, and constraints.
A non-exhaustive list of organizations whose systems and workflows have shaped how I think.
I do not treat AI as the intervention by default. Often the useful intervention is upstream: naming the workflow, reducing ambiguity, strengthening documentation, and deciding where automation is safe enough to test.
A system can look successful while quietly transferring burden to the people inside it. These are the signals I watch before trusting the story the dashboard tells.
This is the condensed chart. The full record lives in the resume (PDF).
This section is where projects and case studies live. The common thread is not the category of the project. It is the pattern of the problem.
A local-first knowledge operating system for governed documents, reversible lifecycle management, and review-safe LLM integration. Built for environments where decisions carry consequence.
A simulated assistant dashboard for testing voice commands, tool review, and memory access before any real microphone, camera, or hardware exists.
A general latent-state framework for diagnosing whether a system remains viable under load, even when dashboards still appear stable.
A Flutter desktop command center for tracking what is active, blocked, due today, and ready for phone handoff without cloud sync or telemetry.
A decoupled robot-control prototype where LLM output becomes intent proposal, passes a safety gate, and only then reaches bounded actuators—demonstrating constraint-aware reasoning before motion authority.
Controller-first Linux media center for games, apps, and streaming
● orange rows are public repos not yet filed on this chart — they surface here automatically.
TL;DR: Short essays and working notes on clinical systems, AI governance, documentation, workflow geometry, cognitive load, and the strange middle ground between disciplines.
The notes section is not a traditional blog. It is closer to a public notebook: observations, working language, project reflections, and attempts to name patterns before the categories fully settle.
Why the same job loss can produce radically different outcomes depending on the buffers around it.
How systems preserve visible stability by consuming the reserves of the people inside them.
What a pediatric cardiac handover, a Formula 1 pit crew, and my garden taught me about seeing systems from another angle.
What nursing taught me about AI, workflow design, and carrying judgment across systems.
How Coheronia became a small Godot survival sandbox with a verification spine: task queues, ledgers, review passes, and in-engine smoke tests.
A field note on exposing Project Atlas to ChatGPT through a narrow OAuth-gated MCP connector without widening the local system's trust boundary.
Why several recent projects start with local ownership, visible state, and human review before adding AI or automation.
A short note on why my AI prototypes route language through intent, finite actions, safety checks, and review instead of direct execution.
How project state, documentation, screenshots, and public proof artifacts drift unless update loops are part of the workflow.
A practical note on turning local workbenches, prototypes, and utilities into portfolio artifacts without overstating production readiness.
A systems-level look at why overtime persists—and what it reveals about capacity, measurement, and hidden structural failure.
A short story about drift, memory, and what happens when a system stops forcing agreement and begins to reveal what actually holds.
A structured coherence diagnostic using cross-cultural music as a dataset.
An opening essay on coherence, expression, and why music makes system behavior easier to hear.
These notes will change over time. E-MyR is intentionally a living chart, not a frozen snapshot.
TL;DR: Resume, credentials, source links, and professional verification.
I keep public claims conservative. Where possible, I prefer concrete artifacts, visible systems, and bounded evidence over inflated positioning.
FL RN9613731, Unencumbered, Expires 07/31/2026
License status can be verified via the Nursys QuickConfirm portal.
ADN — Nursing, 2012 · Chamberlain College of Nursing