​
Tremor Projects Appendix

Tremor is a reference implementation and operating example, not the product itself. This page explains the two project umbrellas that carry the company’s work and how to read their authored definitions. Use it to understand which project owns which branch of the company goal tree.

​
How To Read This Page

  1. Start with the branch coverage column.
  2. Use the milestones to understand what each project is trying to land.
  3. Follow the source link for the full authored project brief.
  4. Treat the projects as execution umbrellas, not as generic portfolio items.

​
Project Map

ProjectOwnerBranch CoverageMilestonesSource
Tremor Flight PlanSydPlatform foundation, Sensory engine, Launch readinessAuthoritative state model; local mesh transport; rule ingestion and synthesis; board ingestion and calibration; timing, haptics, and audio; render and simulation fidelity; milestone control and RAID; regression harness and QA automation; release safety and dual-screen readinessTremor Projects
Tremor Studio OpsProgram ManagerStudio operationsLab readiness and device health; budget and runway discipline; approvals and onboarding hygieneTremor Projects

​
Operating Model

The project split is deliberate:
  • Tremor Flight Plan carries the product-facing delivery spine.
  • Tremor Studio Ops carries the recurring operating cadence and the support work that keeps delivery unblocked.
That separation makes the corpus easier to scan and makes the company graph easier to maintain.

​
Source Set

SourceWhy It Matters
Projects READMEQuick index and branch coverage summary
Tremor Flight PlanDelivery roadmap and phase structure
Tremor Studio OpsOperating cadence and support work
Phase 1 workstreamExample of a closed operations workstream

​
Reading Tip

If the work changes the product, start with Flight Plan. If the work keeps the company healthy, start with Studio Ops.