svc-tenders Extraction Order

This document proposes a practical extraction sequence based on current code reality.

It does not assume immediate service splitting. The default strategy is:

1. code boundary first where possible
2. package/API boundary next
3. service or database split only when contracts are stable

Extraction decision rules

• Extract first when:
  • the capability already has a distinct table set
  • the gateway already supports a service URL override
  • Kafka/outbox coupling is low
  • UI and API ownership are already product-distinct
• Delay extraction when:
  • the public truth model is still mixed or UI-first
  • the data model is still legacy/new dual-path
  • the capability is deeply tied into KES/tender declarations
  • the current service is still the only stable canonical owner