Products · businesses · agent systems

Smoky Product Company is Bobby's working studio: operating brands, open tools, service businesses, and the swarm that helps build them. This project list shows what exists, what is moving, and what has proof.

Browse the projectsSee the first proof note

Current work

Dogfood the build, then show the receipts.

This first slice moves SmokyProduct onto EmDash, uses Dinkus's CTA block in production-shaped code, and records GrillTrack decisions beside the source.

Active dogfoodSmoky WorksExercising Dinkus and the synthetic inspection-to-quote flow in acceptance.Open buildDinkusHardening compatibility, patterns, and theming through real-site dogfood.Rehomed buildSmokyClubDefining the storefront and commerce boundary after the repository rehome.

Projects · 7 records

7 projects, one body of work.

The work crosses commerce, local service, open infrastructure, and agent operations. Every project record names its lane and current evidence state without pretending the projects have equal maturity.

01Established brand

Consumer brand · commerce

Smoky Mountain CBD

An established hemp-products brand where packaging, retail operations, wholesale, and online commerce meet in one customer-facing business.

Open project
02Active dogfood

Service business · field work

Smoky Works

An Astro and EmDash review build for a field-service business, using real service constraints to prove Dinkus and fail-closed lead intake.

Open project
03Open build

Open tooling · EmDash

Dinkus

Plugins and templates for EmDash sites—dogfooded on real builds before release.

Open project
04Prototype

Agent operations · utility

SwarmBar

A read-only native macOS menu-bar roster and doorway for bringing the highest-signal swarm state into the operator's normal work.

Open project
05Active internal

Agent operations · dashboard

SwarmDash

The internal operator surface that turns workers, routes, proof, blockers, and human gates into visible system truth.

Open project
06Operating brand

Consumer brand · commerce

GrowFunkyBeans

A live seed-commerce and education brand combining a shoppable catalog, grow guidance, rewards, and a deliberately playful customer voice.

Open project
07Rehomed build

Membership · community product

SmokyClub

A product-owned storefront and community codebase, extracted from a stale umbrella while shared commerce remains separately owned.

Open project

Connected by design

The products feed the tools. The tools feed the products.

Smoky is not a row of unrelated logos. Businesses create real constraints; Dinkus packages the useful patterns; the Swarm makes work visible; proof decides what survives.

  1. 01

    Business layer

    Real businesses create the constraints

    Commerce, service work, and community products supply real offers, content, operations, and failure modes.

  2. 02

    Product layer

    Dinkus packages the surviving patterns

    Reusable EmDash blocks and templates emerge only after site work proves the contract is worth carrying.

  3. 03

    Operator layer

    SwarmDash and SwarmBar make the work visible

    The swarm needs a trustworthy view of routes, machines, blockers, proof, and the human decisions it cannot make.

  4. 04

    Decision layer

    GrillTrack and acceptance proof decide what survives

    Locked decisions, local behavior, screenshots, and honest defects turn experimentation into a product record instead of a story told from memory.

Dogfood note 001 · Smoky Works × Dinkus

One CTA band, two products under test.

Smoky Works used Dinkus's first unreleased EmDash block in a real site slice. SmokyProduct now consumes the same exact commit, turning a one-site spike into cross-site proof.

What worked
The Dinkus block registers in EmDash, exposes editable fields, persists as Portable Text, and renders through its public Astro component.
What it exposed
The first dogfood run exposed an EmDash 0.29.0 double-dispatch save race in the block modal. The defect is recorded instead of hidden behind a green screenshot.
Next
Keep the dependency pinned, repeat the admin edit-and-publish loop here, and recheck the workaround when EmDash fixes the upstream race.
Read the public dogfood finding

Follow the work

Start with a project. Stay for the proof.

Each project gets a clear status, a concrete role, and evidence as it earns it.

Read the Dinkus dogfood note