Cross API/web

A small contract drift can become a system failure.

The example starts with a user payload producer and a web consumer. The API emits email_address, the consumer expects email and the resulting KeyError represents the 500. The fix aligns the contract and adds a cross-project regression guard.

DEMO ASSET SOON Route status

Back to proof hub

api producer fixed

web contract guarded

mcp proof surface

review gate linked

Run shape

Hypothesis, plan, implementation, review.

The cross run first identifies the mismatch, then validates whether the plan covers the real boundary. Sub-runs apply scoped changes in api and web, then contract checks review the integrated result.

Guard

The regression test imports both sides.

The web test imports the real api.payload.build_user_payload and web.consumer.format_user_label, then asserts the rendered label and expected field coverage.

Limit

The fixture is intentionally small.

The example is not meant to prove every workflow. It proves that Orcho can preserve and inspect a cross-project delivery contract.