Doordash — Delivery Changelog
Owner: Brylle Girang
Updated by: Cursor automation (Thursday) or Brylle manually
Related: Doordash Workflow Plan · SLA
Purpose
This changelog is the single source of truth for all Doordash deliveries. Every update that gets packaged and shipped gets a row here. It serves three functions:
- Accountability: Confirms that the weekly cadence (≥1 update/week, OKR M3.3) is being met
- Refire pairing: The changelog is the baseline for absorption tracking — compare Refire signal volume before and after each entry to gauge behavioral adoption
- Audit trail: Allows the team to look up when a specific workflow changed and when the team was notified
Log
| Date | Week | PR # | Update title | Tier | Format | Channel | Delivered | Absorption status |
|---|---|---|---|---|---|---|---|---|
| — | — | — | — | — | — | — | — | — |
Column definitions
| Column | Definition |
|---|---|
| Date | Date the delivery was posted (YYYY-MM-DD) |
| Week | ISO week number (e.g. W15) for easy scan-to-delivery grouping |
| PR # | GitHub PR number that sourced the update |
| Update title | Short title used in the delivery (matches Slack post or digest entry) |
| Tier | 1 / 2 / 3 |
| Format | digest / slack-post / forge+clip |
| Channel | Slack channel or Forge page URL where delivery was posted |
| Delivered | yes / pending / skipped (with reason in notes) |
| Absorption status | tracking / no-signal / refire-spike / refire-drop / n/a — updated as Refire data becomes available |
Absorption status guide
The absorption column is populated after delivery, not at time of posting. It reflects activity signals, not self-report.
| Status | Meaning |
|---|---|
tracking | Delivery posted; monitoring Refire signals for this skill/workflow — no data yet |
no-signal | No Refire signals observed for this skill before or after delivery; behavior change not yet measurable |
refire-drop | Refire signals for this skill decreased after delivery — strongest absorption indicator |
refire-spike | Refire signals increased after delivery — packaging likely didn’t land; flag for re-delivery |
n/a | Tier 1 quick tip — absorption tracking not applied at this tier |
Absorption tracking is a WIP system. See Stage 5 in the plan for the design direction. Update this column as the Refire system matures.
Scan log
Each Thursday scan also gets a one-line entry here to confirm the scan ran, even if no deliveries were produced that week.
| Scan date | PRs scanned | T1 found | T2 found | T3 found | Notes |
|---|---|---|---|---|---|
| — | — | — | — | — | — |