Iceboard
ProductionDigital hockey coaching platform for drawing, animating, and sharing plays with a professional whiteboard workflow and AI assistant support.
Production tools and experiments
This is the application surface of the main site: production tools, operator-facing workflows, and focused demos built to make the broader CodingEnvironment system concrete.
The main site explains the system and the work. This page is where those claims resolve into software you can actually open, inspect, and use.
These are the tools already shaped around concrete use cases: coaching workflows, statistical support, analytics exploration, project operations, and knowledge access.
Digital hockey coaching platform for drawing, animating, and sharing plays with a professional whiteboard workflow and AI assistant support.
Interactive statistical exploration and expert support environment built around real JMP workflows instead of generic analysis theater.
Explore live manufacturing and telemetry datasets with ranking, correlation, and notebook-ready analysis paths without dropping into raw code first.
Lightweight project and task management with kanban workflows, drag-and-drop organization, and enough structure to be useful without process bloat.
Coding workbench for experimentation and prototyping when an idea needs structure, context, and instrumentation before it deserves a full product shell.
Curated personal knowledge library with private access for family and close friends. Sign in to browse and download.
Smaller surfaces for validating focused ideas. These stay visible, but they are labeled clearly so the production tools and exploratory work do not blur together.
Two technical books built from working systems: an executable MCP agent lab with DSPy, and a visual engineering manual for personal cognitive infrastructure with OpenClaw.
Fit common statistical distributions to uploaded data and inspect the result quickly when you need a fast diagnostic rather than a full analysis environment.
The apps domain now follows the same typography, header structure, navigation behavior, and visual rhythm as the main site, so it feels like one system instead of a detached microsite.
Apps carrying real workflows stay grouped together, while demos and exploratory tools remain visible without pretending they have the same maturity or operating expectation.
The header keeps the main site routes and contact affordances intact, so users can move between the explanation layer and the application layer without losing orientation.