YardMesh by Hubsays

YardMesh by Hubsays

Model it. Run it. See what you forgot.

YardMesh is a work-in-progress tool for exploring how systems behave before they become real workflows. We’re currently developing the interactive version privately. For now, these are a few of the flows and ideas we’re testing.

  • Status · In development
  • On the bench

See the systems ↓ Meet the builder ↗

What

Explore the gap before the workflow is real.

Place people, work, gates, and ownership. Put the model under pressure. Inspect what stalled — and who was missing. Diagrams describe. Automations act. YardMesh sits in between.

Systems

Flows and ideas on the bench.

Conceptual plates from the notebook. The interactive build is still in the workshop.

Example 01

THE MISSING OWNER

Ownership gap Intake Review ??? OWNER unnamed Action hop stops

Work reaches Hands with no named owner. Name the owner — or the hop stops.

Conceptual plate

Example 02

FRIDAY LUNCH

In the model Orders Prep Pass Service Dishwashing NOT IN MODEL omitted

Capacity and dependency under rush — one omitted actor shows what you forgot.

Conceptual plate

Example 03 · Principle

OBSERVATION IS NOT AUTHORITY

Signal → Propose → Gate → Act Signal Model / Bot PROPOSE Human Gate authority ACT break before act

Capture can be precise. Acting still needs a responsible hand.

Principle plate

Example 04 · On the bench

SAME PRINCIPLE · DIFFERENT FLOOR

SaaS ↔ ops · ownership gap SaaS ticket ??? OWNER handoff Floor task ??? ON THE BENCH Same principle · different floor

Same ownership principle across floors. Still on the bench — not released as a public interactive floor.

On the bench

Status

ON THE BENCH · IN DEVELOPMENT

  • Interactive version in development
  • Released when ready

Built in public, released when it’s ready. The interactive build is still in the workshop.

Principles

Ideas we keep coming back to.

  • Observation is not authority Signals and models may propose. A human gate decides before action.
  • Ownership must be named Unowned hops stop. The gap is the lesson.
  • The model is not the world Omitted actors still exist — Friday Lunch’s dishwasher sits outside the box.

Who

Hubsays builds YardMesh.

A small studio building playable systems — in public, and at our own pace. Built by Brendan Davies · Product & Operations Builder · Meet the builder ↗

FAQ

Short answers.

What is YardMesh?
A work-in-progress tool for exploring how systems behave before they become real workflows.
Where is the interactive version?
Still in the workshop. These plates are flows and ideas we’re testing.
What kinds of systems does it explore?
Operational handoffs: ownership gaps, omitted dependencies, and the line between observation and authority.
Who builds it?
Hubsays. Meet the builder ↗.