- Ya
- 3 Julai 2026, 04:40 UTC
- Mwandishi
- kamo
- Ahadi ya
- 63b0a04
The three write paths the consoles surfaced as coming-soon, live end-to-end: - StewardFeedbackComposer in the decision-trail drawer: CONFIRM/MODIFY/OVERRIDE segmented verdict (tone-coded), Reg-B reason select (required on OVERRIDE), MODIFY corrected-value JSON editor with client-side validation, WORM append-only note, in-flight guard (the chain has no idempotency key). - PullThroughPolicyComposer replaces the publish coming-soon box: two-step edit -> review-diff -> publish v(n+1); knob validation mirrors the service (probs 4dp, percentiles, doc-09 horizon vocabulary, platform floor hint); publishes via session-stamped proxy that ownership-verifies the grain. - RunPricingComposer behind a Run-pricing header action: scenario/product prefills from the selected run, SHOPPING/WHAT_IF only, optional facts (fico/ltv/dti/state), post-run counters incl. skipped products, view-run. Plumbing: mlos routes forward request.method + export POST; mlosPost (NO retry - non-idempotent WORM writes); write types/fns in governanceApi/pricingApi. i18n: all new text via next-intl; replaced hardcoded PRICING_PURPOSE_LABEL/ ELIGIBILITY_LABEL maps with t()-backed helpers; keys triple-written.