Single-owner principle

Single-owner principle

One role owns the full lifecycle of an artifact category. Forking ownership across layers creates structural debt.

Concrete instances

  • Framework library — Francois (Framework Specialist) is the single owner of frameworks per TFD-0010 (refined by TFD-0022). TFD-0022 explicitly extends his ownership to the rendering layer of frameworks, not just the content layer, because forking the rendering ownership to Remy would have created TFD-0010 debt. TFD-0022 Decision

  • Toolkit-catalog bundle — Diego (Deployment Specialist) leads the unified packaging + release pipeline. Pablo owns the bundle convention upstream so production-line Stage 5 emits it natively. Two roles, two clear surfaces. TFD-0021 Actions §1

  • agent-ea output contract — the EA Catalog Storage decision moves agent-ea's output to a validated-upload step. The pipeline and leanix-catalog-extract toolkit own the change end-to-end (no fork). TFD-0019 Consequences

Distinction: owner vs operator vs consumer

TFD-0022 §5 makes this explicit for frameworks:

  • Francois owns what is a valid gabarit (standard, content + rendering, skill).
  • Remy operates the publication of the final deliverable at the client (JCT, intranet, SharePoint).
  • Elena consumes by filling content for a given mandate.

The single-owner rule applies to ownership, not to operation/consumption — those can be distributed.

Linked