edictIn development

Meal planning and recipes

An example app for recipe data, weekly meal schedules, shopping lists, AI-generated plans, and reminders.

Example app Built from planned modules. Not a customer. Not a supported app today.

Illustrative rule: AI meal plans for premium, one per week

AgentEdit edict.yaml+11illustrative
1modules:
2+ subscriptions:
3+ plans: [free, premium]
4+ ai_meal_planner:
5+ requires_plan: premium
6+ quota:
7+ per: week
8+ limit: 1
9+ notifications:
10+ triggers:
11+ - on: schedule.sunday_evening
12+ send: plan_next_week

Placeholder values and unfinished syntax. Not a released feature.

What is the Meal planning and recipes example app?

A user saves recipes, drops them onto a weekly calendar, and gets a shopping list built from the week. Free users plan by hand. A premium feature drafts a week of meals from their tastes and constraints. A reminder on Sunday evening invites them to plan the next week.

This category is a design target. It is not a claim that Edict already supports a complete meal planning app.

What backend does the Meal planning and recipes example need?

  • Recipe data.
  • Meal schedules.
  • Shopping lists.
  • AI-generated plans.
  • Subscriptions.
  • Reminders.

How do the planned modules compose in the Meal planning and recipes example?

The database is designed to store recipes, ingredients, scheduled meals, and shopping items, all owned by the user. A shopping list would be derived from the meals in a chosen week, which the planned query support is meant to cover.

For the generated plan, Authentication, Subscriptions, and the AI gateway are designed to form the usual chain: identity, plan, then a quota. In this example the quota allows one plan per week. Background jobs are planned to run the generation without holding the client connection open, and Push notifications would tell the user when it is ready or when it is time to plan.

What would an illustrative rule look like in the Meal planning and recipes example?

The configuration above gates the planner behind a premium plan, limits it to one use per week, and sets a Sunday reminder. The limit is a placeholder, and the key names and syntax are not final.

What is example and what is planned in the Meal planning and recipes example?

All modules named here are planned and in development. Your app owns the recipe content, the nutritional or dietary logic, and the safety of its suggestions. Edict does not give dietary or medical advice, and a generated plan may be wrong, so your app should make that clear. Any recipe or grocery data service would be an outside integration and none is listed as active.

See the Subscriptions and AI gateway module pages for the planned design. Join the beta waitlist to follow progress.

These share the most modules with this one.

See all example apps

Get an invitation when the beta opens.

Joining gets you email updates while Edict is built, and an invitation to the hosted beta when it opens.

Building now. No launch date yet.