Implementation Approach

Strategy Selection

Use this sequence when a design or task needs an implementation approach:

1. Current evidence: Inspect the relevant responsibility, data or control path, representative repository pattern, and constraints that can change the choice.
2. Direct implementation: Describe the simplest end-to-end change that delivers the confirmed outcome through the existing architecture and dependencies.
3. Failure check: Test the direct implementation against current requirements, verified constraints, observed problems, and evidence-backed material risks within scope.
4. Targeted expansion: Add only what resolves a failed item. Compare the smaller design with and without the addition.
5. Value and subtraction check: Retain an addition only when evidence shows that its outcome benefit justifies its implementation, testing, documentation, runtime, and maintenance cost.

Possible future reuse, generic best practice, speculative edge cases, and optional hardening are not failed items. File count is supporting evidence, not a strategy rule.

Keep unselected candidates in the active execution context. Create a durable artifact only for a named downstream consumer.

Slicing Choice

Choose the smallest structure that preserves real dependency order and yields observable progress: