Selected projects
A changing shelf of public writing, private systems, and working experiments, each named by its purpose, present state, and limits.
Working ledger
These projects are far enough along to describe honestly. Most remain local or private by design. Public links appear only when the public surface is the point.
An intentionally small public notebook connecting relational practice, field notes, and useful technology. It stays hand-built and static so the work can remain direct, legible, and easy to revise.
The architecture is deliberately quiet: plain HTML, shared CSS, and no build system between an idea and the page.
A growing shelf of essays and practices about telling the truth without turning truth into a weapon, or private relationships into public evidence.
Read the current workA local research-to-action system that tracks public Codex developments, preserves source context, and turns useful findings into a risk-gated backlog instead of another unread feed.
Reports, source snapshots, and project state remain local.
A clinician-supervised brainstorming framework built around readiness gates, source controls, and output safety checks. It is designed to expose missing information and unsafe certainty, not automate clinical judgment.
Education and quality-improvement use only. Not validated or intended for live patient care.
A local compliance aid for licensure, certification, continuing education, evidence gaps, and deadline calendars. It turns scattered obligations into one reviewable readiness picture.
Portal passwords are not stored. Official access remains supervised and source-driven.
A privacy-aware review workflow that turns authorized, derived source summaries into de-identified workday and connection briefs while keeping coverage gaps and uncertainty visible.
Raw transcript dumps are intentionally excluded from durable review artifacts.
Public boundary
A private internal tool supporting authorized bookkeeping and accounting review. This site exposes only static compliance and connection-boundary documentation, never financial data or access to the private runtime.
View the public policiesBuild principles
Start with the real friction and the person who has to live with the result.
Keep sensitive state close, minimize data movement, and publish only what belongs in public.
Consequential actions stay visible, bounded, and under deliberate control.
Name uncertainty, failure modes, and present boundaries as part of the work itself.