Concepts & principles / design-pattern

Strategy pattern

Encapsulate interchangeable algorithms behind a shared behavioral contract when variation is a real requirement.

Canonical graph nodestrategy-pattern

Variation with a reason

A system may need different ranking or generation strategies. If callers can rely on the same contract, selecting an algorithm need not change their behavior. One simple algorithm does not require a strategy framework in anticipation of others.

AI-first interpretation

Model providers or retrieval methods can be candidates for strategies only when their guarantees are sufficiently compatible. Latency, privacy, tool support, output limits, and failure modes are part of the contract, not incidental details.

Ask an assistant to define substitutability tests before implementing a provider switch. A shared method name alone does not make two models interchangeable.

Part of a connected world

Follow the meaning.

View the graph →

Outgoing connections

extendsGang of Four design patterns
applies-toFrontier models

Connected from

explainsOld principles. New leverage.

Node data identity, meaning & relationships

The complete semantic record, rendered from root node: front matter.

semantic_node:
  description: Encapsulate interchangeable algorithms behind a shared behavioral contract when variation is a real requirement.
  id: strategy-pattern
  kind: design-pattern
  name: Strategy pattern
  relationships:
  - predicate: extends
    target: gang-of-four-patterns
  - predicate: applies-to
    target: frontier-models
  type: concept

Publishing metadata

description: Encapsulate interchangeable algorithms behind a shared behavioral contract when variation is a real requirement.
draft: false
title: Strategy pattern
url: /graph/concepts/strategy-pattern/