Tremor

Tremor is a local-first Apple ecosystem game studio building tactile board-game experiences. This page is the curated narrative surface for the company: it explains the shape of the work, then points into the source corpus and operating docs when you need the underlying detail.

Read this site in two modes

SurfaceUse it forStart here
LandingOrientation, thesis, and the company storyTremor landing
Knowledge baseStable product and platform reference for PaperclipKnowledge base overview
Operating corpusLive Tremor baseline, wiki pages, and recovery disciplineOperating corpus overview
The point of the split is simple: this page should stay short and legible. The manual and the live operating record each have their own surface.

The short version

Tremor exists to make a board-game system feel physically grounded before it feels expansive. The product is designed around a hub-and-client model: deterministic state lives on the hub, iPhone and iPad provide tactile input and feedback, and the shared screen carries the board and spectator view.

What makes it distinct

The company is not trying to be a generic multiplayer app. Its differentiators are specific:
  • Wired-first connectivity, with AirPlay-fallback later.
  • Authoritative state on the hub, not dispersed across clients.
  • A shared-screen presentation model that keeps the board legible.
  • Tactile feedback as a first-class part of the experience, not a cosmetic layer.
  • A local-first operating posture that treats fidelity and latency as product facts, not implementation details.

Why it exists

Tremor is built around the premise that board-game software should preserve the physical feel of play instead of flattening it into a conventional mobile app. The company structure exists to support that outcome: platform and networking keep the runtime stable, sensory systems shape the tactile layer, and quality work protects the experience before it ships.

What backs it

SystemWhat it contributes
Paperclip knowledge baseStable manual for the control plane, workflows, architecture, deploy, and API surfaces
Tremor operating corpusLive operating boundary, current baseline, and control-plane reference set
Tremor company recordCanonical company definition, goals, divisions, and operating shape
Tremor operating wikiCurrent status, environments, recovery, and operational safety pages
Tremor projectsDelivery and operations project structure
Tremor skillsLocal capability catalog for the company graph
The knowledge base explains the system. The operating corpus captures the live baseline. The source corpus carries the underlying authored company record. This landing page stays above all three and keeps the entry path short.

Where to go next

Knowledge base

Read the manual for Paperclip concepts, guides, deploy, API, and system boundaries.

Operating corpus

Read the live Tremor baseline, operating wiki, and recovery-oriented appendices.

Company appendix

Read the compact company summary, counts, and canonical source links.

Architecture

Read the current control-plane and data-flow architecture in manual form.