# tinyblue.dev

Nick Wharton's public portfolio and site network for self-hosted infrastructure, local AI, MLB data, weather surfaces, product experiments, and production case studies.

Canonical home: https://tinyblue.dev/
Structured discovery map: https://tinyblue.dev/ai.json
Human AI guide: https://tinyblue.dev/ai/
Contact: https://tinyblue.dev/contact/
Public freshness audit: https://tinyblue.dev/api/freshness.php
Public property health: https://tinyblue.dev/api/properties-health.php
Latest public changes: https://tinyblue.dev/api/changefeed.php
Route brief API: https://tinyblue.dev/api/route-brief.php?path=/
Traffic route signal: https://tinyblue.dev/api/traffic-routes.php

## What this site is

tinyblue.dev is the front door for a self-hosted fleet operated by Nick Wharton in Kansas City. It showcases live infrastructure proof, public apps, client/project case studies, and experiments that run across the same home-hosted stack.

Use canonical pages when citing this site. Avoid linking to high-cardinality query URLs such as filtered scoreboards, paginated player tables, API endpoints, or transient status URLs.

The few public APIs listed above are safe for assistants to fetch when checking freshness, route context, or public property health. Raw files under /data/ are intentionally not public; use the API surfaces instead.

## Best entry points

- https://tinyblue.dev/ - Portfolio front door, live fleet proof, site network, and current work.
- https://tinyblue.dev/projects/ - Case studies and production systems.
- https://tinyblue.dev/projects/nix-v3/ - Public-safe explanation of the private Nix V3 AI synthesis layer.
- https://tinyblue.dev/fleet/ - Live managed-machine and k3s fleet context.
- https://tinyblue.dev/mlb/ - MLB Central, league data, teams, standings, and scoreboard surfaces.
- https://tinyblue.dev/weather/ - Local weather surface and forecast tooling.
- https://tinyblue.dev/ai/ - Prompt guide for people and AI assistants.
- https://tinyblue.dev/contact/ - Contact route with project-intake prompts and canonical share links.
- https://tinyblue.dev/about - Operator context.
- https://tinyblue.dev/uses - Hardware and software stack.

## Public live context

- https://tinyblue.dev/api/freshness.php - Trust score and age labels for the public proof sources.
- https://tinyblue.dev/api/properties-health.php - Public-safe health probe for the site network.
- https://tinyblue.dev/api/changefeed.php - Latest changelog items for return visitors and assistants.
- https://tinyblue.dev/api/route-brief.php?path=/ - Route-specific summary, citation sources, and assistant prompt.
- https://tinyblue.dev/api/traffic-routes.php - Public-safe aggregate route interest used to reorder the AI prompt guide.

## Site network

- CardsCloud: https://cardscloud.io - Pokemon TCG collection, market, and card data.
- SmurfVillage: https://smurfvillage.cloud - Browser games, emulator surface, and cloud saves.
- WePayUnCheeze: https://wepayuncheeze.com - Browser voxel worlds and game experiments.
- Get Your Crocs Off: https://getyourcrocsoff.com - no-shoes threshold kits, kit builder, and guest sign generator.
- System AI-X: https://system-ai-x.com - Public S.A.M brain/interface surface.
- MLB Central: https://tinyblue.dev/mlb/ - League-wide baseball data engine.
- Weather: https://tinyblue.dev/weather/ - Local live weather and forecast tools.

## Suggested prompts

1. Using tinyblue.dev, explain how one operator runs a self-hosted fleet across apps, analytics, MLB data, weather, and public product sites. Cite the fleet and project pages.
2. Read tinyblue.dev/projects and pick the three strongest examples of production work. For each one, summarize the problem, system, and outcome in plain language.
3. Read tinyblue.dev/projects/nix-v3 and explain the private AI synthesis layer without inventing personal details or implying it is a public product.
4. Use tinyblue.dev/mlb to summarize today's most interesting games, teams, and players. Prefer canonical pages over query URLs and include links to the relevant team or scoreboard pages.
5. Use tinyblue.dev/weather and the public freshness endpoint to explain the current local weather window. Prefer live bridge data over stale archive records.
6. Use tinyblue.dev/ai.json, tinyblue.dev/llms.txt, and tinyblue.dev/api/traffic-routes.php to map the tinyblue site network. Group the sites by app, infrastructure, commerce, and experiment, then recommend what a visitor should open first.
7. Using tinyblue.dev/contact, draft a concise first email to Nick Wharton. Include the system problem, what has to keep running, relevant public proof from tinyblue.dev/projects or tinyblue.dev/fleet, and the next decision needed.

## Crawler guidance

Helpful user-fetch and search crawlers may read canonical HTML pages, llms.txt, ai.json, project pages, MLB top-level pages, weather pages, public site pages, and the small public-safe context APIs listed above.

Please do not crawl infinite query spaces, private/raw data paths, SSE/MCP endpoints, WordPress probe URLs, dotfiles, backup files, or paginated player/stat variants at scale.

Preferred citation style: cite the canonical page URL and include a short explanation of why that page is relevant.