---
name: Inbox - from {{platform_team_name}}
description: Inbox for kit-sync events, capability-request acknowledgements, deprecation notices, and breaking-change notices from the central platform team. Biweekly drain cadence.
type: inbox
Owner: RevOps-AI eng lead drains; {{platform_eng_lead}} produces
---

# Inbox - from {{platform_team_name}}

- **Last reviewed:** 2026-04-22 (last drain)
- **Review cadence:** biweekly drain (every other Monday); event-driven additions
- **Status:** active

Schema: see `inbox/SCHEMA.md`. Each entry has date, source, type, state, priority, target close.

## Open

### 2026-04-26 - Kit sync event: 14-day drift detected

- **Source:** {{platform_team_name}} sync notification
- **Type:** kit-sync-event
- **State:** open (action: pull, eval, ship)
- **Priority:** high
- **Target close:** 2026-05-05

Two prompt-library updates and one eval-harness update have landed in `{{platform_team_name}}/ai-kit/` since our last sync (2026-04-12). Pull and re-eval before next ship cycle. RevOps-AI eng lead has the action.

### 2026-04-23 - Capability acknowledgement: streaming enrichment proposal

- **Source:** {{platform_eng_lead}}
- **Type:** capability-request-ack
- **State:** open (Platform Engineering reviewing; expect response by 2026-05-15)
- **Priority:** medium
- **Target close:** 2026-05-15

Acknowledges the streaming-enrichment proposal we sent (outbox 2026-04-15). Initial assessment: feasible but requires changes to {{queue_or_messagebus}} consumer pattern; Platform Engineering scoping at sprint start. Will respond in next biweekly cycle.

### 2026-04-19 - Deprecation notice: `{{deprecated_tool}}` v2.x sunset

- **Source:** {{platform_eng_lead}}
- **Type:** deprecation-notice
- **State:** open (action: migrate to v3.x by 2026-Q3 cutoff)
- **Priority:** medium
- **Target close:** 2026-09-30

`{{deprecated_tool}}` v2.x will be removed from the kit on 2026-09-30. Our consumers in `kit/guardrails/{{guardrail_using_deprecated}}` use v2.x; migrate to v3.x. Migration guide: `{{platform_team_name}}/migration-guides/{{tool}}-v2-to-v3.md`.

### 2026-04-15 - Kit improvement: PII detector v3.0 available

- **Source:** {{platform_eng_lead}}
- **Type:** kit-sync-event
- **State:** open (action: pull as part of next sync)
- **Priority:** medium
- **Target close:** 2026-05-05 (bundled with the 14-day-drift resolution)

Updated PII detector with improved EU-PII coverage; reduces false negatives on inferred-title fields. Will pull as part of the next sync cycle.

## Drained this quarter (last drain 2026-04-22)

| Date | Type | Resolution |
|------|------|-----------|
| 2026-04-08 | kit-sync-event (model bump claude-sonnet-4-5 -> 4-6) | actioned: pulled, eval re-run, shipped |
| 2026-04-01 | capability-request-ack (cost-attribution-by-tier proposal) | acknowledged: declined, kit owner cited bandwidth; tracked for Q3 reconsideration |
| 2026-03-25 | breaking-change-notice (telemetry schema v2 -> v3 mandatory field rename) | actioned: migrated emit code; verified telemetry round-trip |
| 2026-03-18 | kit-sync-event (eval harness perf improvement) | actioned: pulled, eval comparable on harness-perf-only re-run |
| 2026-03-11 | deprecation-notice ({{deprecated_helper}} retirement) | actioned: migrated 3 consumers; sent ack to Platform Engineering |
| 2026-03-04 | capability-request-ack (synthetic-eval-data proposal) | acknowledged: accepted; Platform Engineering integrating in 2026-Q3 |
| 2026-02-25 | kit-sync-event (guardrail runtime patch for thread-safety) | actioned: pulled and shipped |
| 2026-02-18 | kit-sync-event (telemetry destination URL change) | actioned: config update; no code change |
| 2026-02-11 | breaking-change-notice (auth header format v1 -> v2) | actioned: migrated; backwards-compat shim in place 30 days |
| 2026-02-04 | kit-sync-event (prompt library tier-2 quality improvement) | actioned: pulled; eval improvement +1.2pp on faithfulness |
| 2026-01-28 | capability-request-ack (custom-redaction-rule proposal) | acknowledged: accepted; shipped 2026-03-15 |
| 2026-01-21 | kit-sync-event (eval-data refresh recommendation) | actioned: discussed Q1 review; aligned with our quarterly cadence |
| 2026-01-14 | kit-sync-event (model availability change) | acknowledged: informational |
| 2026-01-07 | capability-request-ack (multi-tenant-cache proposal) | acknowledged: declined, cited security review; tracked for V2.x |

Total quarterly drained: 14. State distribution: 8 actioned, 5 acknowledged, 1 escalated (the multi-tenant-cache proposal escalated to ADR consideration; ADR not yet written).

## Cross-references

- `outbox/to-{{platform_team_name}}.md` - the corresponding outbox
- `inbox-topology.md` - declared pair
- `decisions/ADR-0002-kit-mirror-direction.md` - the decision establishing this inbox-outbox pair
