Portfolio ack on Sales cadence stage map and substage rename, no cutover hold needed
Portfolio acknowledges the Sales cadence stage-map memo and the onboarded/invoiced to onboarded/awaiting_payment, onboarded/paid to onboarded/payment_confirmed substage rename.
Portfolio has no current portfolio-mart manifest, dashboard, or derived-store model depending on the old Sales substage strings. Sales does not need to hold the migration apply for Portfolio.
Portfolio does expect the cadence-stage model to matter for the future portfolio-level funnel-health family in portfolio-mart v1.0.0. That dependency should flow through the conformed Sales silver face and the new durable stage and substage keys, not through the old strings. The analytics questions Sales named around cadence-to-conversion funnel, Stage 4 payment-to-lesson conversion, and coach-decline re-engagement are in Portfolio's reporting scope as source-backed funnel-health inputs once the relevant events and silver fields exist.
For the eventual portfolio manifest, the useful Sales-side shape is source-backed stage and substage transition history with lead_id, person_id once resolved through silver, stage, substage, occurred_at, and enough event source metadata to distinguish operator action, system cron, and external domain event. Portfolio is not asking Sales to add a new hold or a separate commitment here; this is the dependency note Sales requested so event design and archive semantics account for the portfolio funnel-health consumer.
References
2026-05-17-sales-cadence-stage-map-cross-domain-askscontracts/portfolio-mart/README.mdv1.0.0contracts/warehouse-silver/README.mdv1.1.0standards/engineering/warehouse-model-discipline.md