TFD-0010: Framework Library Ownership — Internal with Interface Design

TFD-0010: Framework Library Ownership — Internal with Interface Design

Status: Accepted Date: 2026-03-23 Decision makers: CEO (Oscar) Consulted: CTO (Clara), Enterprise Architect (Elena), Production Line Architect (Pablo), Framework Specialist (Francois), Client Intake Manager (Camille)

Context

The factory is accumulating framework documentation work across 6 capability areas (enterprise-architecture, it-governance, project-management, coding-standards, data-governance, solution-architecture) with active requests for LeanIX schemas and Macroscope. Each new client engagement could require additional frameworks (TOGAF, COBIT, ISO 27001, PMBOK, SAFe, etc.). The question arose whether this growing library should be offloaded to a subsidiary, outsourced partner, or kept internal.

Decision

Keep framework documentation internal to Talent Factory, but design the framework package format as a defined interface contract so it could be fulfilled externally in the future.

Options Considered

Option Verdict
A — Keep internal (no interface design) Too short-sighted — doesn't prepare for scale
B — Spin off subsidiary Premature — insufficient volume, undefined integration contracts, legal/operational overhead
C — Outsource to partner Quality control risk, format misalignment, external dependency
D — Internal now, design for future separation Accepted — fast iteration today, optionality tomorrow

Rationale

  • Framework knowledge is tightly coupled to the production pipeline (Francois → Pablo → digital talent output)
  • Current volume (6 capability areas, 1 specialist) doesn't justify organizational separation
  • Client intake depends on fast framework turnaround — adding an external entity slows the loop
  • The framework package standard is still being defined (MET-0004) — premature to outsource what isn't standardized yet

Actions

  1. Standardize the framework package format (Francois + Marcel, already in progress via MET-0004)
  2. Treat the framework library as a defined interface — documented inputs, outputs, and quality criteria
  3. Revisit this decision at 15+ frameworks or when a second production line needs different framework packaging

Consequences

  • Francois remains the single owner of framework documentation
  • Framework packages must conform to a standard interface (to be defined)
  • No organizational change today — scaling trigger is explicit (15+ frameworks or multi-line demand)