Dataform + BigQuery Governance
I designed a release pattern that brings data contracts, cost checks, ownership, and rollback into one promotion path.
Sanitized reference pattern; no measured customer outcome.
Software, reference architectures, and creative projects. Explore what I contributed and inspect the artifacts behind the work.
I designed a release pattern that brings data contracts, cost checks, ownership, and rollback into one promotion path.
Sanitized reference pattern; no measured customer outcome.
A sanitized reference architecture that treats compliance, analytics delivery, and ML feature access as one governed release path.
Illustrative timings and architectural targets are not reported as measured engagement outcomes.
I implement and contribute Python statechart semantics, actors, and XState-compatible workflow definitions.
Evolving prototype; not a durable workflow engine.

I lead and implement an interactive story exploring narrative state, choice, and small acts of care.
Public story prototype; not a finished commercial game.
An internal editorial project that audited whether published labels were supported by the depth and structure of the underlying writing.
This is a first-person internal retrospective, not external client work or independent validation.
An independent research program that compares data-science stacks while holding the source, question, transformations, and acceptance criteria constant.
The artifacts demonstrate matching aggregate run summaries for one small descriptive clustering workload; they do not establish identical month-level assignments, universal language performance, production adoption, causal economic regimes, forecasts, or customer outcomes.
Observed: The preserved 2006-2025 Elixir and Python run records report matching profile counts, centroids, inertia, and conclusions after matching arbitrary cluster labels.
Two private practice projects used to develop a shared evidence contract for sports forecasts, decisions, positions, and evaluations without real-money functionality.
The public case study documents architecture and governance. It is not public source, a live product, a real-money system, customer validation, or evidence of improved forecasting outcomes.
A research prototype for running deterministic, traceable simulations of operational decisions and policy alternatives.
There is no public runtime, live customer data, calibrated business model, forecast, digital twin, or external validation in the initial record.
At the studio
Review warehouse model changes with requirements, validation, and cost evidence together.
Public product preview. SaaS and warehouse integrations are in development.
Inspect whether a high-value CRM outcome is supported by the associated call evidence.
In development. Export-based evaluation is the starting point; SaaS is not generally available.
Turn a week of recipes into a meal plan and a practical shopping checklist.
Web and iOS implementations in development. Local storage; no cross-device sync.
Explore public signals through a fictional zombie lens, with inspectable sources.
Web and iOS prototypes. The Z-Index is not a probability or emergency alert. Readiness tools are future work.