What does your Ruby workspace look like?

[sidbhatt11]

RWM was built around one specific pain: multiple Ruby packages in one repository — shared libs, a few deployable apps, path dependencies in Gemfiles, and CI that should only test what changed.

But the Ruby landscape is shifting under our feet. Hanami, Dry, and ROM have joined forces as Hanakai, Hanami 3.0 just shipped, and modular architectures — slices, extracted gems, engines, plain-old multi-gem repos — are a live conversation again. Rails is not the only shape Ruby comes in anymore, and monorepo conventions built for one world may pinch in another.

Since rwm collects zero data (no telemetry, ever), I genuinely don't know what your workspaces look like. So — tell me:

• How many packages live in your repo (or the repo you wish was structured)? 3? 15? 100?
• What's the mix — one app and many libs? Several apps sharing a domain layer?
• What are they built with? Rails, Hanami/Hanakai, Sinatra, Roda, plain gems, something else?
• What do you use today to hold it together — hand-rolled rake tasks, CI path filters, a Makefile, Nx-envy, nothing?
• Which rwm convention would you fight? libs/ + apps/? "The git root is the workspace root"? "Apps are leaf nodes — nothing depends on an app"?

Partial answers welcome. "We tried a Ruby monorepo and gave up because X" is just as useful as a success story — maybe more. This thread is the closest thing rwm has to a user survey, and it's the only kind it will ever run.