​

ADR-0002: Platform/Tenant Repo Target State

​

Status

Accepted target state

​

Context

Paperclip is the platform/runtime. Tremor is a tenant/company/project operating on that platform. The current single-repo arrangement obscures that distinction, especially around ownership, release boundaries, and IP separation.

​

Decision

Use a two-repo target model:

• embr-labs/paperclip for the platform/runtime
• embr-labs/tremor for the Tremor tenant/company layer

Do not execute that split yet. Treat it as the target state and migrate only after the operating preconditions are satisfied.

​

Preconditions

• environment matrix is stable
• canonical schema authority is documented
• handoff protocol is active
• CI gates are stable
• platform vs tenant boundaries are explicit
• import/export or packaging boundaries are defined
• regression suite is adequate for split validation

​

Consequences

​

Positive

• cleaner ownership model
• stronger platform vs tenant separation
• clearer IP and release boundaries

​

Negative

• migration cost is nontrivial
• regression testing burden will be high
• requires packaging and import/export discipline that does not yet fully exist

​

Review Trigger

Revisit when the preconditions are met and the integration baseline is stable enough to survive a split.