Tremor Company Appendix

Tremor is a reference implementation and operating example, not the product itself. This appendix summarizes the company corpus so you can understand the operating model without reading every authored file first. Use this page when you need the shape of the company, the major workstreams, and the canonical entry points into the source corpus.

How To Read This Appendix

  1. Start with the boundary: Tremor describes how this specific company is organized and operated.
  2. Use the tables below to identify the relevant collection.
  3. Follow the linked authored files when you need the authoritative source.
  4. Treat this as an index plus operating guide, not a replacement for the underlying docs.

Corpus At A Glance

CollectionCountWhat It Represents
Company definition1The company-level operating model and work graph
Teams4The division and cell boundaries
Agents15The named roles that execute the work
Projects2The delivery and operations umbrellas
Tasks15Starter issues and recurring routines
Skills55The local capability library used by the company graph

Operating Model

Tremor is organized as a small company graph:
  • Leadership sets direction, budget, and escalation.
  • Platform and networking keep the state and transport model stable.
  • Sensory work owns the physical feel of the system.
  • Quality and product work protect the player experience and release confidence.
That is the point of the corpus: it documents a concrete operating pattern that can be read, audited, and replayed.

Primary Sources

SourcePurpose
Company definitionCanonical company record and work graph
Tremor READMEHigh-level overview and top-level counts
Operating wikiLive control-plane notes and policy pages
Projects indexDelivery and operations project map
Tasks indexIssue and routine inventory
Skills indexCompany-local capability catalog

What This Is For

  • Rapid orientation for people or agents new to the Tremor corpus.
  • A stable reference point when the underlying files are being extended.
  • A readable bridge between the company story and the authored source files.

What This Is Not For

  • It is not the product documentation for Paperclip.
  • It is not the place to define new company policy.
  • It is not the authoritative source for live operational facts if a source file disagrees.