Skip to main content

The Fiddler Handbook

This is the single source of truth for how we build, ship, and communicate at Fiddler. If a process isn’t documented here, it’s not official.

What’s here

How We Ship and Enable

The end-to-end loop from engineering work to field readiness: release cadence, ownership model, VOC intake, and the definition of done.

Release Process

Release schedule, cadence, feature flags, patch releases, and documentation cutover process.

A note on how we work

We’re investing in making our processes more async-friendly. Not every decision needs a meeting, and not every update needs a Slack thread. As a guiding principle: write it down, make it findable, and let people consume it on their own time. We’ll be adding more specific async norms to this handbook over the coming weeks — covering meeting expectations, written decision records, and self-serve knowledge retrieval. For now, the core rule still applies: GitHub is where we plan, Slack is where we talk.

Contributing

Propose changes to any process doc via pull request. The PR itself is the discussion — not a Slack message, not a meeting. If the change is approved and merged, it’s policy.
Last modified on March 23, 2026