{
  "meta": {
    "name": "Meal Fame Public Corpus",
    "version": "0.1.0",
    "license": "All rights reserved. Content may be read and summarized by agents for their users.",
    "homepage": "https://mealfame.com",
    "agent_manifest": "https://mealfame.com/.well-known/agent.json",
    "last_updated": "2026-06-11",
    "status": "pre-launch"
  },
  "key_metrics": {
    "status": {
      "value": "pre-launch",
      "reasoning": "The product is in active development. This corpus describes the service as designed; it expands at launch with live train schemas and permission-gated agent actions."
    },
    "creation_time_target_seconds": {
      "value": 60,
      "reasoning": "Organizers create a meal train in three steps: pick the person, pick the reason, share one link."
    },
    "helper_accounts_required": {
      "value": false,
      "reasoning": "Helpers participate from a shared link using magic links or SMS codes. No passwords exist anywhere in the product."
    }
  },
  "reports": [
    {
      "id": "overview",
      "title": "What Meal Fame Is",
      "sections": [
        {
          "anchor": "concept",
          "title": "Concept",
          "summary": "A meal train as a community love event, not a scheduling chore.",
          "content_markdown": "Meal Fame helps friends organize meal deliveries for families experiencing major life events: a new baby, a surgery, a hard season, a loss, a new home, or a celebration. An organizer starts a train in about 60 seconds and shares one link in a group text. Friends claim a night with one tap and either bring a home-cooked meal or send the family's favorite restaurant order through delivery. Notes travel with every meal. The family receiving meals controls everything: their preferences, their privacy, and what recognition (if any) their helpers receive."
        },
        {
          "anchor": "roles",
          "title": "Three Roles",
          "summary": "Organizer, Helper, Recipient, each with a distinct experience.",
          "content_markdown": "Organizers create and share the train without needing to know the family's food preferences. Recipients onboard once, gently: favorite orders, allergies, delivery windows, household boundaries (visitors ok? calls ok?), and tone preferences. Helpers never create accounts; they claim a slot from the shared link, see the family's preferences (never their address), and help with one tap. Delivery addresses are injected only at dispatch through the delivery partner; meal senders never see them."
        },
        {
          "anchor": "tone",
          "title": "Category-Aware Tone",
          "summary": "Celebration where it fits, quiet where it matters.",
          "content_markdown": "Every train carries a sensitivity posture. Celebratory trains (new baby, new home) get the full warmth: notes, thanks, and small moments of recognition chosen by the recipient. Supportive trains (surgery, illness) run quieter. Grief trains suppress celebratory features entirely; they are removed, not hidden. This is enforced in the product's data layer, not by editorial judgment."
        }
      ]
    },
    {
      "id": "sms-program",
      "title": "Text Message Program",
      "sections": [
        {
          "anchor": "consent",
          "title": "Dual Consent",
          "summary": "Two independent opt-ins, captured at number entry, logged.",
          "content_markdown": "Meal Fame texts only people who provide their number directly and consent at that moment. Two independent, unchecked choices: coordination texts (reminders, confirmations, schedule changes for commitments the person made) and optional appreciation texts (thank-you notes from recipients, milestone notices). Consent language and timestamp are logged per number. STOP cancels, HELP helps, opt-outs are immediate. Message and data rates may apply. Consent is never a condition of using the service. Numbers are never sold or shared for others' marketing."
        }
      ]
    },
    {
      "id": "privacy-commitments",
      "title": "Privacy Commitments",
      "sections": [
        {
          "anchor": "commitments",
          "title": "Standing Commitments",
          "summary": "The privacy rules the product is being built around.",
          "content_markdown": "No advertising trackers. No sale of personal information. Delivery addresses are never displayed to meal senders. Food preferences are stored as literal order items; the product does not derive religious or health inferences from them. AI-assisted features (like help drafting a thank-you note in the recipient's writing style) are consent-gated, editable before sending, and never used to train models. Families in grief never receive automated celebratory content."
        }
      ]
    }
  ],
  "knowledge_base": [
    {
      "id": "faq",
      "title": "Early Questions",
      "frontmatter": {"audience": "general", "updated": "2026-06-11"},
      "body": "When does Meal Fame launch? It is in active development; email hello@mealfame.com to be notified. What does it cost? Core meal trains are free for organizers, helpers, and recipients, permanently; the service earns revenue on optional supporter-side conveniences like restaurant delivery and gifts. Will there be an app? The web app is mobile-first and works from a group-text link with nothing to install."
    }
  ],
  "project_documentation": {
    "agent_actions": "At launch, this corpus will document permission-gated actions agents can take on behalf of their users: reading a train's open slots, claiming a slot for their human, and composing a delivery note for human approval. Pre-launch, no actions are available.",
    "schema_preview": "Train pages will be server-rendered HTML with structured data. Core public objects: train (occasion, posture, schedule), open slots (date, window), and preferences relevant to helping (likes, allergies), with addresses and contact details never exposed."
  },
  "primary_sources": [
    {
      "id": "site",
      "name": "mealfame.com",
      "publisher": "Meal Fame",
      "url": "https://mealfame.com",
      "type": "website",
      "what_it_provided": "All public content in this corpus."
    }
  ]
}