One story per family
Battle Dinghy variants should support the ThreadPlay narrative. Fleet tools should support the Commercial Intelligence narrative.
Public Workshop
This is the map of what I am tinkering with: commercial intelligence tools, timeline-native games, agentic workflows, market experiments, and discovery interfaces. Some are prototypes. Some are product specs. Some are just useful notes becoming systems.
The goal is not to make every repo public-facing. The goal is to turn many scattered build artifacts into a smaller set of understandable project narratives.
Taxonomy
Each bucket collects a family of projects. The public site should promote the family-level story first, then expose repos only when they help explain the work.
Fleet, aftermarket, territory, reseller, VIN, license, land, and customer-intel systems.
Games, predictions, challenges, wagers, and social mechanics designed to happen inside timelines.
AI workflows, research agents, coding agents, memory systems, and operational command surfaces.
Prediction markets, incentive systems, coordination games, ORE-adjacent notes, and market mechanics.
Swipe interfaces, matching systems, preference capture, lightweight curation, and social discovery UX.
AI calibration, personal tools, branding, marketing infrastructure, and utility repos that support the system.
Operating Model
Battle Dinghy variants should support the ThreadPlay narrative. Fleet tools should support the Commercial Intelligence narrative.
The public surface should explain the project. Repos can remain private, archived, duplicated, or experimental behind the scenes.
Each update should be a design note, build note, demo note, or research note rather than a giant launch.
Next
Start with ThreadPlay, FleetRadar, Signal Foundry, Fagan Brain, and SwipeNFT. Everything else can orbit those core stories until it earns a public page.
Open the project index