​

System Reference

Use this page as the fast lookup for terminology, ownership, and doc boundaries. It is a reference page, not a narrative page.

​

Authority Map

​

Key Terms

​

Paperclip

The platform that provides the control plane for autonomous AI companies. Paperclip owns the UI, server, data model, adapters, and CLI surfaces that govern work.

​

Tremor

The company currently operating on Paperclip. Tremor owns the company-specific wiki, operating artifacts, repo strategy, and live audit surfaces.

​

Control plane

The part of the system that decides, coordinates, validates, and records work. In practice, this means the UI, server, database, adapters, and CLI that make the company governable.

​

Operating corpus

The current, dated, and company-specific documentation set that records how Tremor is being run. This includes the wiki, current snapshots, recovery notes, and related artifacts.

​

Baseline

A current verified state that should be treated as operationally meaningful until a new baseline is promoted. Examples include a runtime target, database target, or repo strategy baseline.

​

Reference Rules

• If a term is stable and reusable, define it in product docs.
• If a term is current-instance specific, define it in operating docs.
• If a page uses a term that can mean two different things, define the local meaning on first use.
• If a live fact is being referenced, include the date, audit basis, or verification context.
• If a page compares both layers, state the comparison boundary near the top.

​

Where To Look

​

Boundary Summary

In one sentence:

• Paperclip docs explain the platform.
• Tremor operating docs explain the current company running on that platform.

That separation keeps the manual reusable while still preserving the live operating record.