Decision log

• scan-participants — 2026-04-24T13:48:34.637212+00:00

  unknown

  decisions/2026-04-24-scan-participants.md

  Show content

  # scan-participants — 2026-04-24T13:48:34.637212+00:00
  Repos discovered: 2
  
  - atlas (/repos/marome-atlas)
  - payments (/repos/my-investments-payments)
  # scan-participants — 2026-04-24T14:02:27.633432+00:00
  Repos discovered: 11
  
  - agents-config (/repos/agents-config)
  - finance-dashboard (/repos/finance-dashboard)
  - gatekeeper (/repos/license-gatekeeper)
  - atlas (/repos/marome-atlas)
  - admin (/repos/my-investments-admin)
  - android (/repos/my-investments-android)
  - ios (/repos/my-investments-ios)
  - payments (/repos/my-investments-payments)
  - rn (/repos/my-investments-react-native)
  - marketing (/repos/my-marketing)
  - music (/repos/my-music-production)
  

• Broadcast Decision — product_slug → product_key rename

  unknown

  decisions/2026-04-24-product-slug-to-product-key.md

  Show content

  # Broadcast Decision — product_slug → product_key rename
  
  **Broadcast ID:** `msg_a8f3c210`
  **Date:** 2026-04-24T14:05Z
  **Source Repo:** payments
  **Tags:** `["user-request", "api-change", "breaking", "product_slug", "product_key"]`
  **SLA Window:** 48h (expires 2026-04-26T14:05Z)
  
  ## Summary
  
  `product_slug` field is being renamed to `product_key` in the **payments** API (`payments:openapi` contract) and related event payloads (`payments:events`).
  
  ## Classification
  
  | Contract | Breaking? | Justification |
  |----------|-----------|---------------|
  | `payments:openapi` | **Yes** — field name change in request/response schemas |
  | `payments:events` | **Yes** — event payload field rename affects consumers parsing events |
  
  ## Affected Repos
  
  | Repo | Role | Contract(s) Consumed | Impact |
  |------|------|---------------------|--------|
  | admin | web | `payments:openapi`, `payments:events` | Direct — UI + webhook handling |
  | finance-dashboard | service | `payments:openapi`, `payments:events` | Direct — API integration + event consumers |
  | gatekeeper | infra | `payments:events` | Indirect — event parsing only |
  | music | service | `payments:openapi`, `payments:events` | Direct — subscription + purchase flows |
  | android | mobile | `payments:openapi` | Direct — in-app purchase flows |
  | ios | mobile | `payments:openapi` | Direct — in-app purchase flows |
  | rn | mobile | `payments:openapi` | Direct — in-app purchase flows |
  
  ## Responses
  
  *(Asynchronous fan-out initiated. No architect responses yet within the synchronous window.)*
  
  | Repo | Status | Response Time | Verdict |
  |------|--------|---------------|---------|
  | admin | no-response | — | Pending |
  | finance-dashboard | no-response | — | Pending |
  | gatekeeper | no-response | — | Pending |
  | music | no-response | — | Pending |
  | android | no-response | — | Pending |
  | ios | no-response | — | Pending |
  | rn | no-response | — | Pending |
  
  ## Decision
  
  **Fan-out required:** Yes — 7 repos affected.
  
  **Next steps:**
  1. Source repo (payments) should publish migration timeline
  2. Each affected repo's architect to assess breakage + migration effort
  3. Coordinate rollout to avoid multi-version drift in mobile app stores
  
  ## Logged By
  
  Atlas PM (auto-classified, user-initiated broadcast)