​
Tremor Tasks Appendix

Tremor is a reference implementation and operating example, not the product itself. This page summarizes the task corpus so you can see the issue graph and the recurring operating cadence in one place. The task layer is where the company becomes executable: issues attach to the roadmap, and routines keep the operating loop alive.

​
How To Read This Page

  1. Read the task type first: issue or routine.
  2. Check the branch goal and project to see where the task belongs.
  3. Use the assignee to identify the owning lane.
  4. Open the source task when you need acceptance criteria or schedule details.

​
Task Inventory

​
Starter issues

TaskBranch GoalProjectAssigneePurposeSource
Founder strategy approvalShip Tremor alphaTremor Flight PlanSydFounder strategy and approval backlogTremor Tasks
PM RAID milestonesLaunch readinessTremor Studio OpsProgram ManagerPM RAID and milestone controlTremor Tasks
Platform authoritative statePlatform foundationTremor Flight PlanCo-Engineering Lead APlatform authoritative state and local networkingTremor Tasks
Sensory simulation fidelitySensory engineTremor Flight PlanCo-Engineering Lead BSensory simulation and fidelity validationTremor Tasks
Systems network transportPlatform foundationTremor Flight PlanSystems Network EngineerSystems network transportTremor Tasks
GenAI rule ingestionPlatform foundationTremor Flight PlanGenAI ArchitectRule ingestion and synthesisTremor Tasks
DevSecOps release safetyLaunch readinessTremor Studio OpsDevSecOps EngineerRelease safetyTremor Tasks
Lead product designer dual-screenLaunch readinessTremor Flight PlanLead Product DesignerDual-screen flowTremor Tasks
Tools QA regression HILLaunch readinessTremor Studio OpsTools QA EngineerRegression and HIL coverageTremor Tasks
SDET automation coverageLaunch readinessTremor Studio OpsSDET EngineerAutomation and coverageTremor Tasks
Admin ops lab readinessStudio operationsTremor Studio OpsAdmin and OpsLab readinessTremor Tasks
DSP audio timingSensory engineTremor Flight PlanDSP Audio EngineerAudio pairing and timingTremor Tasks
Computer vision board ingestionSensory engineTremor Flight PlanComputer Vision and AR EngineerBoard ingestion and calibrationTremor Tasks
Technical artist render pipelineSensory engineTremor Flight PlanTechnical ArtistRender and material pipelineTremor Tasks
Simulation engine chaos harnessSensory engineTremor Flight PlanSimulation EngineerChaos and stress harnessTremor Tasks

​
Recurring routines

RoutineBranch GoalProjectAssigneeScheduleSource
Monday strategy reviewStudio operationsTremor Studio OpsSyd0 9 * * 1 (Australia/Sydney)Tremor Tasks
Tuesday roadmap and RAID reviewLaunch readinessTremor Studio OpsProgram Manager30 9 * * 2 (Australia/Sydney)Tremor Tasks
Wednesday budget and runway reviewStudio operationsTremor Studio OpsSyd0 10 * * 3 (Australia/Sydney)Tremor Tasks
Thursday lab and device health checkStudio operationsTremor Studio OpsAdmin and Ops30 10 * * 4 (Australia/Sydney)Tremor Tasks
Friday QA regression smokeLaunch readinessTremor Studio OpsSDET Engineer0 11 * * 5 (Australia/Sydney)Tremor Tasks
Epoch 2 ledger reconciliationStudio operationsTremor Studio OpsAdmin and Ops0 * * * * (Australia/Sydney)Tremor Tasks

​
Operating Model

Issues and routines play different roles:
  • Issues push the roadmap forward.
  • Routines keep the company aligned, audited, and healthy.
  • Both are attached to branch goals so the task graph matches the company graph.
This makes Tremor useful as a reference example because it shows how one company keeps its delivery work and recurring operations in the same system without confusing them.

​
Source Set

SourceWhy It Matters
Tasks READMECanonical inventory and count summary
Issue task files/operating/tasks
Routine task files/operating/tasks

​
Reading Tip

If a task exists to land product work, treat it as an issue. If it exists to keep the company observable or healthy, treat it as a routine.