API TENDER LEGACY ACTION 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 Action Status

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

Scope

This document classifies the tender legacy action routes in services/api and separates route ownership from legacy outbox/event behavior.

Legacy Action Inventory

| Route | Local action | Route classification | Event behavior | Verified in-repo caller status | | --- | --- | --- | --- | --- | | POST /api/v1/tenders/legacy/propose | proposeTenderFromKes | legacy local-engine action + compatibility bridge | may emit TENDER_CREATED via emitLegacyTenderOutbox | no verified direct in-repo caller | | POST /api/v1/tenders/legacy/:id/bids | submitLegacyBid | legacy local-engine action + compatibility bridge | may emit BID_SUBMITTED | no verified direct in-repo caller | | | | + | may emit | no verified direct in-repo caller | | | | + | may emit | no verified direct in-repo caller | | | | + | may emit | no verified direct in-repo caller |

Loading workspace

Loading module

Loading workspace

API TENDER LEGACY ACTION STATUS

API Tender Legacy Action Status

Scope

Legacy Action Inventory

Local-Engine vs Compatibility vs Gateway Event Emission

Legacy local-engine action

Compatibility bridge

Gateway-side legacy event emission path

Why These Routes Still Exist

What Is Still Operationally Needed

What Can Be Reduced Later

What Blocks Deeper Cleanup

Decision

What should remain now

What should be isolated next

What may be removable later

Ownership Verdict

Notes