Projects and patterns with explicit evidence classifications. A public artifact demonstrates something inspectable; it does not automatically prove adoption or business impact.
This page remains a curated evidence surface. Browse the broader public-safe project index for independent project-type, business-model, distribution, and runtime classifications.
A sanitized reference pattern for data contracts, validation gates, release lanes, rollback behavior, and cost checks in a governed analytics promotion path.
Claim boundary: This is a generalized professional pattern, not a named engagement, public deployment record, or measured customer outcome.
No public observed outcome is claimed.
A sanitized reference architecture that treats compliance, analytics delivery, and ML feature access as one governed release path.
Claim boundary: Illustrative timings and architectural targets are not reported as measured engagement outcomes.
No public observed outcome is claimed.
Open-source implementation and contribution work on Python statechart semantics, actors, clocks, and XState-compatible workflow definitions.
Claim boundary: The repository is implementation evidence for an evolving prototype; it is not evidence of production adoption, durability, or operational outcomes.
No public observed outcome is claimed.
A live interactive story prototype used to explore narrative state, choice, and cross-surface interaction design.
Claim boundary: Live means the prototype is publicly accessible; it does not imply a finished commercial game, broad playtesting, or independent validation.
No public observed outcome is claimed.
An internal editorial project that audited whether published labels were supported by the depth and structure of the underlying writing.
Claim boundary: This is a first-person internal retrospective, not external client work or independent validation.
No public observed outcome is claimed.
An independent research program that compares data-science stacks while holding the source, question, transformations, and acceptance criteria constant.
Claim boundary: 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 outcome: 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.
Claim boundary: 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.
No public observed outcome is claimed.
A research prototype for running deterministic, traceable simulations of operational decisions and policy alternatives.
Claim boundary: There is no public runtime, live customer data, calibrated business model, forecast, digital twin, or external validation in the initial record.
No public observed outcome is claimed.