API TENDER LEGACY BRIDGE STATUS

Current scope: Gest

Category: 10_normative | Version: v1.0.0

Owner: DOCUMENT_CUSTODIAN | Review cycle: 90 days

Approval Authority: GOVERNANCE_ADMIN

Read-only Documentation Portal. Editing and mutation endpoints are disabled.

METADATA INCOMPLETE: Document ID, Version, Status, Owner Role, Last Review Date, Next Review Date, Change Log

API Tender Legacy Bridge Status

Date: 2026-03-19 Sprint: Platform Cleanup Sprint 104

Scope

This document isolates the tender legacy compatibility route shell from the gateway-side legacy outbox bridge that still lives in the same services/api module.

It is not removal planning. It is a boundary-clarification step before later removal planning.

Route / Action Inventory

| Route | Local action | Route classification | Bridge classification | Operational need today | Separable? | Looks isolatable next? | | --- | --- | --- | --- | --- | --- | --- | | POST /api/v1/tenders/legacy/propose | proposeTenderFromKes | legacy compatibility route that also triggers gateway-side bridge behavior | emits TENDER_CREATED through the bridge helper | yes | yes | yes | | POST /api/v1/tenders/legacy/:id/bids | submitLegacyBid | legacy compatibility route that also triggers gateway-side bridge behavior | emits through the bridge helper | yes | yes | yes | | | | | emits through the bridge helper | yes | yes | yes | | | | | emits through the bridge helper | yes | yes | yes | | | | | emits through the bridge helper | yes | yes | yes |

Loading workspace

Loading module

Loading workspace

API TENDER LEGACY BRIDGE STATUS

API Tender Legacy Bridge Status

Scope

Route / Action Inventory

What The Route Shell Still Does

Actual Bridge Ownership Inventory

Bridge helper

What the bridge does

What calls the bridge

Why the bridge still exists

Which Parts Are Route Compatibility Only

Which Parts Are Bridge Behavior

What Remains Operationally Needed

What Looks Isolatable Next

Notes