doordash-order-ledger

Topics in the source

• DoorDash Order Ledger
• Line schema (v1)
• Query recipes (jq)
• Honest semantics
• Maintenance

Every dd-cli command the agent runs is recorded by the doordash-audit-log hook in /.claude/dd-guard/audit.jsonl — one versioned JSON line per event. This skill teaches you to answer questions from that log instead of guessing. Install the bundle: hook doordash/doordash-audit-log (the recorder), command /doordash-report (reconciled summaries), this skill (querying). Composes with doordash-spend-guard (shares the /.claude/dd-guard/ state directory) but runs standalone. Commands are secret-stripped before persisting and truncated to 500 chars. The v field guards future schema changes — check it before assuming fields. Answer from data, not memory: When the user asks a money question ("how much this week?"), prefer /doordash-report — it reconciles against real dd-cli order history and labels intent-only numbers honestly. Raw checkouturl counts are intents: the human may have abandoned the payment page. checkouturl ≠ purchase. It records that a link was issued. Only reconciliation against order history confirms money moved. Subtotals (when present via doordash-spend-guard's ledger) are pre-fee. The log records what went through Claude Code's Bash tool — orders placed by the human direct

This is an excerpt. Refer to the complete source and its current requirements.