TFD-0014: Digital Talent Component Taxonomy

TFD-0014: Digital Talent Component Taxonomy

Status: Accepted Date: 2026-03-29 Decision makers: CEO (Oscar), Ada (Agentic Pattern Designer), CTO (Clara)

Context

The factory has strong individual catalogs (Ada's 21 agentic patterns, Francois's framework library, Pablo's assembly process) but no unified view of what makes up a digital talent. Production workers assemble knowledge from 4+ sources during Stage 3 and Stage 4. No single document maps the complete set of building blocks, their relationships, selection criteria, and ownership.

Additionally, Anthropic's harness design evolution (Agent SDK, multi-agent orchestration) represents the next product tier, but we have no systematic way to track and integrate new harness capabilities.

Decision

Create an 8-category component taxonomy owned by Ada (Agentic Pattern Designer), with a harness capability matrix documenting Claude Code as our runtime:

Component Categories

  1. Agentic Patterns — How the talent works (Ada)
  2. Frameworks — What the talent knows (Francois)
  3. Models & Routing — Which LLM for which task (Ada + Riley) [new]
  4. Harness Configuration — Runtime setup (Ada + Ivan) [new]
  5. Skills & Commands — Executable capabilities (Pablo)
  6. Templates & Deliverables — Output formats (Francois)
  7. Integrations — External connections (Ivan) [new]
  8. Knowledge Base — Reference materials (Kai)

Harness Capability Matrix

Documents what Claude Code can do as a runtime, maturity levels, and design principles drawn from Anthropic's harness design article.

Ownership

  • Ada owns the overall taxonomy and harness capability documentation
  • Riley feeds new discoveries via the R&D pipeline (TFD-0012)
  • Category owners maintain their individual catalogs
  • Clara approves changes to selection criteria (affects production quality)
  • Monthly review cycle, plus trigger-based updates

Scope Expansion for Ada

Ada's role expands from "Agentic Pattern Designer" to include:

  • Full component taxonomy ownership
  • Harness capability documentation
  • Model & routing catalog (with Riley)
  • Cross-department coordination for taxonomy updates

Sub-Decisions

ID Decision Status
D1 Category-level taxonomy (not instance-level) — map the 8 types with selection criteria Approved
D2 Harness capability matrix as a first-class section (not separate R&D track) Approved
D3 Agent SDK evaluated through R&D pipeline as next product tier Approved
D4 Interactive HTML diagrams on intranet (LeanIX-style component map) Approved

Consequences

Positive:

  • Unified view of all building blocks for production workers
  • Selection criteria prevent ad-hoc, inconsistent component choices
  • Riley and engineering have a clear target for where new capabilities land
  • Harness mastery documented as competitive differentiator
  • Foundation for client-facing explanations of "why these components"

Negative:

  • Ada's scope increases — may need to delegate pattern catalog maintenance
  • Monthly review adds process overhead

Risks:

  • Taxonomy becomes stale if update triggers are not followed — mitigated by monthly review + R&D pipeline integration

References

  • Design spec: docs/superpowers/specs/2026-03-29-component-taxonomy-design.md
  • Anthropic harness article: https://www.anthropic.com/engineering/harness-design-long-running-apps
  • Existing pattern catalog: departments/it-architecture/agentic-pattern-designer-ada/patterns/catalog-index.md
  • Framework library: production-lines/digital-talent/frameworks/
  • Assembly guide: production-lines/digital-talent/assembly.md