Tremor Teams Appendix
Tremor is a reference implementation and operating example, not the product itself. This page explains how the team structure works and where the division boundaries live in the authored corpus. Read this page when you need the organizational model, the reporting lines, or the source files that define each team.How To Read This Page
- Read the division names as operating lanes, not abstract departments.
- Use the manager and scope columns to understand ownership.
- Follow the linked team files for the full authored definition.
- Use the team boundaries to decide who should own a question before you route it.
Team Map
| Team | Manager | Scope | Source |
|---|---|---|---|
| Leadership Cell | Founder | Strategy, roadmap control, budget, and studio support | Tremor Teams |
| Nervous System Division | Co-Engineering Lead A | Platform architecture, networking, and release safety | Tremor Teams |
| Sensory Engine Division | Co-Engineering Lead B | Simulation, perception, audio, visual assets, and synthesis | Tremor Teams |
| Fidelity and Quality Division | Lead Product Designer | Experience design, regression coverage, and confidence engineering | Tremor Teams |
Operating Shape
The team model is intentionally small:- Leadership Cell coordinates the whole system and carries escalation.
- Nervous System Division owns the control-path and transport layer.
- Sensory Engine Division owns the product feel and the perceptual stack.
- Fidelity and Quality Division keeps the experience shippable and testable.
Source Links
| Source | What It Adds |
|---|---|
| Tremor COMPANY.md | The company-level explanation of why these divisions exist |
| Leadership Cell | Governance and support boundary |
| Nervous System Division | Platform and networking boundary |
| Sensory Engine Division | Simulation and perception boundary |
| Fidelity and Quality Division | Design and QA boundary |