Date: 2026-03-17 File: services/svc-tenders/src/repository.ts

Purpose

After Sprint 10, the root repository is no longer the live owner of every major persistence cluster.

This document records what still remains there on purpose.

VERIFIED remaining root-owned zones

1. Output allocation persistence

Methods:

• createOutputAllocation
• updateOutputAllocation
• findOutputAllocationById
• listOutputAllocations

State:

• VERIFIED
• REAL

Ownership:

• unresolved / deferred

Why still root-owned:

• still directly used by auction declaration admin flow
• final domain owner is not yet proven

2. Cross-domain auction settlement linkage

Method:

• settleAuction

State:

• VERIFIED
• REAL

Ownership:

• unresolved / cross-domain

Why still root-owned:

• current implementation updates auction settlement state and linked tender entitlement state together
• not honest to label it purely auction-owned yet

3. KES persistence block

Methods:

• countKesOrchestratorCases
• listKesOrchestratorCases
• getKesOrchestratorCaseDetail
• getKesOrchestratorCaseProjection
• getKesOrchestratorProcessMap
• upsertKesOrchestratorProcessMap
• createKesOrchestratorCase
• approveKesOrchestratorLandowner
• publishKesOrchestratorAuction
• confirmKesOrchestratorFunding
• assignKesOrchestratorTask
• submitKesOrchestratorInspection
• requestKesOrchestratorPayment
• approveKesOrchestratorPayment
• settleKesOrchestratorPayment
• closeKesOrchestratorCase
• listKesOrchestratorSuggestions

State:

• VERIFIED
• REAL

Ownership:

• unresolved between tender-hosted implementation and shared Kvary execution/backbone

Why still root-owned:

• event/runtime coupling is stronger here than for the Sprint 10 extraction targets

4. Legacy compatibility residue

Methods:

• vacancy compatibility readers
• accommodation compatibility readers

State:

• VERIFIED
• MIXED

Ownership:

• already marked as legacy compatibility residue

Why still root-owned:

• not part of Sprint 10
• removal would widen scope into runtime caller migration

VERIFIED remaining root-repository roles

The root repository still acts as:

• compatibility delegation surface
• shared type export location
• host for unresolved persistence ownership
• host for some older helper blocks not yet relocated

What is no longer a live root-owned persistence cluster

These are now child-owned with root delegation:

• tender core persistence
• auction core read/admin persistence
• declaration / evidence persistence
• ICPI persistence
• Butkhuzi persistence

Recommended next cleanup target

The safest next cleanup is not another ownership guess.

It is:

• map which private helpers in repository.ts are now only residual after delegation
• remove or relocate only those helper blocks that are clearly child-owned or dead
• keep KES / settlement / output-allocation ambiguity explicit