gRPC contracts

Published copies under contracts/proto/ are synced from@yourorg/proto (orchestrator/v1, lms/v1). Services should consume generated stubs from that package — not these docs copies at runtime.

Package / file	RPCs	Consumers
orchestrator/payment.proto	InitiatePayment	CAP → OL (pricing stays in CAP; amounts in minor units / bigint)
orchestrator/identity.proto	VerifyIdentity	CAP → OL (client-facing entry is CAP POST /identity-verification)
lms/recommendations.proto	RecommendCourses	CAP → LMS (gap-training catalogue; replaces CAP mock client)

See Payment architecture for InitiatePayment semantics. Hub: Contracts.

// Shape from proto/orchestrator/v1/payment.proto
package orchestrator.v1;

service PaymentService {
  rpc InitiatePayment(InitiatePaymentRequest) returns (InitiatePaymentResponse);
}