Admin #332 — Transcript rendered in the shape RDS actually stores

Plus an explanation of why a voice-agent list can legitimately be empty. **Test (Tier 3):** compare a rendered transcript against the stored record for the same session.

Admin #338 — Market Experience v2: Global is content every market receives, not a market of its own

The foundation the rest of the market work sits on. Treating Global as a third bucket alongside NA and EU was the single cause of the empty market view, the header disagreeing with the market count, and curators being unable to find posts associates could plainly see. **Test (Tier 3, indirect):** verified through #340, #344, #350, #354 and #356. A market view should return All Markets content plus that market, never that market alone.

Consumer #700 / Admin #348 — nginx header buffers sized for the ALB cookie

ALB identity 400s. The header buffers were too small for the ALB session cookie and OIDC headers, and a 400 now names its own cause instead of being opaque. Consumer half is #700, admin half is #348. **Test (Tier 3):** only reproducible under whatever condition was producing the 400s, typically a large session cookie.

Admin #342 — Probe parses date types the way the pool does

The probe was parsing dates differently from the connection pool, so it reported a state that did not match reality. **Test (Tier 3):** compare probe output against a real query returning date columns.

Consumer #704 / Admin #358 — Recombee made dormant behind RECOMBEE_ENABLED

A master switch, off by default. Publish-time item sync on admin is dormant unless `RECOMBEE_ENABLED=true`. Consumer half is #704, admin half is #358. **Test (Tier 3):** verified by absence. Publish an item with the switch off and confirm no sync fires.

Consumer #676 — Store-group hierarchy resolved by district, then area, then country

The consumer half of the EU hierarchy fix. Recovers the 19 European stores that carried no district and were appearing nowhere. **Test (Tier 2):** confirm the consumer hierarchy shows seven EU groups totalling 72 stores, matching admin and analytics exactly.

Consumer #694 — Sentry issue titles carry the failing query name

Previously a failing query produced a title that did not identify which query failed. **Test (Tier 3):** in Sentry. Trigger a query failure and confirm the issue title names it.

Consumer #706 / Admin #360 — Week boundary moves Monday to Tuesday, cutover 2026-09-01

A week now runs Tuesday through the following Monday. Going forward only, no historical recompute. Consumer half is #706, admin half is #360. **Test (Tier 2):** the picker snapping to Tuesday rather than Monday is checkable now. Full behaviour only observable across the 1 September cutover. **Still open:** whether the changeover week runs short or long, and whoever publishes needs to know before scheduling a required set into it.

Consumer #686 — Audio device refusal gets its own retry budget

COACH-PULSE-4T. A refused microphone was consuming the general retry budget. **Test (Tier 2):** deny microphone permission and confirm a readable error rather than a dead end, and that other retries are unaffected.

Consumer #690 — Identity memo keyed on the identity, not the token

COACH-PULSE-4H, the 100% cache miss. The memo was keyed on a value that changed every request, so it never hit. **Test (Tier 3):** watch cache hit rates. Not observable from the interface.

Train: reference audio library per scoring area

Field asked what good, better and best actually sound like for cultural fluency and reading the moment. Generated reference examples per scoring category avoid the consent question entirely. Decision needed on whether we build a reference library. Source: pilot production testing, Aug 11 2026.

Train: named coach that speaks the feedback

Strongest idea of the session. Rather than reading post-session feedback, the associate hears it from a persistent named coach with a chosen voice, building familiarity across sessions. Overlaps with short-form feedback item and should be built together. Source: pilot production testing, Aug 11 2026.

Train: press to speak control (F12)

Store noise is captured during sessions and personas respond to speech the associate did not make. Requested directly by store leaders. Add a press to speak mode in the Train voice UI as an alternative to open mic, with per-user preference persisted. Interim: headset guidance in launch training plus voice partner tuning. Source: pilot production testing, Aug 11 2026.

Train: session playback consent capture and opt-out (F8)

Playback of another associate audio is removed from the Aug 22 build. Returning it requires a consent system: capture consent at first Train session, record scope of consent, per-associate opt-out honored at retrieval time, and admin visibility into consent state. Defined with Coach Legal and HR. Source: pilot production testing, Aug 11 2026.

Rewards for Launch

Coach Pulse has a badge system. It does not have a rewards program. This post scopes what a rewards layer requires and what we commit to for launch. What exists 15 achievement badges, score badges unlocking at 80/90/100%, badge progress on Profile, and an "Earn More" section on Today. All of this is recognition — no cost, no fulfillment, no budget. What a rewards program adds Something of value that an associate receives. That means a funding source, a finite catalog, a redemption path, a fulfillment owner, and per-market HR, payroll and tax review. It is a net-new layer, not an extension of badges. Core decision — earn model Do badges convert into rewards, or do rewards run in parallel on their own criteria? Conversion — badges unlock rewards at a threshold. Reuses the shipped earn logic; cheapest path. Risk: badge design now has money attached, so anything gameable becomes a liability. Parallel — rewards run on separate criteria, likely sales or performance rather than training completion. More defensible, but a new earn engine, and it depends on associate sales data in the C360 feed. Most other decisions follow from this one. Open decisions and owners Earn model — FutureProof recommends, Tapestry approves Reward catalog and funding — Tapestry Redemption and fulfillment path — joint; drives build scope Market eligibility — Tapestry HR/Legal Day-to-day fulfillment owner — Tapestry Proposed launch position Recognition-only. Badges ship as-is; rewards land once catalog, funding and eligibility are settled. Immediate issue, independent of the above"Earn More" is live in nine languages telling associates they can earn additional rewards. No rewards exist. This copy needs correcting regardless of what we decide here.

Work with China team to deploy Train module on their environment

Tapestry AI Summit Training Module Gameplay

Create new version of Train module gameplay where users sign up with email and complete 1 of 3 available personas. Scores are logged and full scoring reports emailed top user. Leaderboard accessible from admins who name winners./

Localization for NA/EU

Localization for NA/EU

Settings: Punjabi and Hindi support for Canada (F20)

Roughly eighty percent of staff and four in five walk-ins at the reporting Canada location speak Punjabi or Hindi. Neither was in the original language set. Feasibility answer required first, then validation through the Canada testers who volunteered. Not in Aug 22 build. Source: pilot production testing, Aug 11 2026.