ICPI CODE BOUNDARY HARDENING

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, Owner Role, Last Review Date, Next Review Date, Change Log

ICPI Code Boundary Hardening

Status: ACTIVE
Sprint: Extraction Prep Sprint 45

Purpose

This document records the first real ICPI code-boundary hardening pass.

The goal of this sprint was not to extract ICPI out of svc-tenders. The goal was to reduce ICPI dependence on mixed root files by moving clearly ICPI-owned contracts and validation into ICPI-owned modules first.

What Moved Into ICPI-Owned Files

Contracts

New file:

services/svc-tenders/src/icpi/contracts.ts

Moved here:

ICPI domain-facing value shapes
ICPI request/input shapes
ICPI response shapes
ICPI repository-port contract
ICPI route-support contract

Most important effect:

ICPI types are no longer primarily defined inside the mixed root

Loading workspace

Loading module

Loading workspace

ICPI CODE BOUNDARY HARDENING

ICPI Code Boundary Hardening

Purpose

What Moved Into ICPI-Owned Files

Contracts

Validation

What Dependency Edges Were Reduced

Route module

Support module

ICPI repository

Root repository

What Still Depends On Root Or Shell Files

Root compatibility still remains

Shell dependencies still remain

What Gateway/API Behavior Stayed The Same

What Is Still Blocking Actual Extraction

Remaining blockers

What is no longer the primary blocker

Practical Outcome