Reading a monthly fund report.

The monthly fund reports live at /impact/reports. Every month has a document. These are LADLE-issued reports on the meal fund (they are not partner receipts — our future hunger-relief partner is the partner we select, not yet an active integration). Here's how to read the fields.

**Month + reference number.** Until the partnership with the hunger-relief charity we select activates, the reference number column reads "pending — will populate once the $50,000/year partnership threshold clears." Post-threshold, the reference number is issued by our future partner (The partner's per-meal platform) with a format like "4471-A", and you can cross-verify it against their transparency reports.

**Total meals reserved.** The count of meals this month's earmark translates to at the $0.80/meal working peg. Today this is meals reserved in the fund, not meals served. Post-threshold, the same column becomes "meals funded" and reflects our future partner-delivered donations. The floor is (subscriber count × 10 meals × months paid), which annual subscribers pull forward into their invoice month.

**Total USD earmarked.** Raw dollar amount added to the meal fund this month. It's total meals reserved × $0.80. Once the partnership activates, this becomes the transfer amount to the partner we select.

**Fund balance + threshold progress.** The cumulative balance held in the meal fund, and the percentage progress toward the $50,000/year partnership with the hunger-relief charity we select commitment. Every $8 accrued moves the needle.

**Per-plan breakdown.** How many reserved meals came from Base subscribers, Max 5x, Max 20x, and gift subscriptions. Verifies the plan mix and per-plan meal count (10 / 50 / 100 monthly, 100 / 500 / 1000 annual). No per-user detail — that'd be a privacy violation.

**How to verify.** Today: cross-check the math against active subscriber counts (subscribers × $8 should reconcile against "added this month," within refund/mid-cycle variance). Post-partnership: look up the reference number with the partner via the verification path published at announcement. If the counts don't reconcile, something is wrong on our end and we owe you an explanation. The escape hatch is documented in /impact/methodology.

If we can't publish a fund report on time in a given month, we say so in the changelog with the reason.