# Amanah

> Stop posting recipes. Start publishing them. Amanah turns cooking knowledge into structured, versionable, forkable artifacts with full attribution and lineage.

Amanah is the reference implementation of **UMF (Ummi Markup Format)**, an open data standard for modeling the culinary world. Every recipe is a living document: forkable, translatable, embeddable, and addressable by URL.

- Website: https://amanah.food
- Extended docs for LLMs: https://amanah.food/llms-full.txt
- Agent landing page: https://amanah.food/for-ai-agents
- OpenAPI spec: https://amanah.food/openapi.json
- MCP descriptor: https://amanah.food/mcp.json
- ChatGPT plugin manifest: https://amanah.food/.well-known/ai-plugin.json
- Agent manifest: https://amanah.food/.well-known/agent.json
- Sitemap: https://amanah.food/sitemap.xml
- UMF Recipe schema: https://amanah.food/recipe.schema.json

---

## Quotable definitions

- **Amanah** is a recipe publishing platform where every recipe is a structured, versioned, forkable artifact with full attribution and lineage.
- **UMF (Ummi Markup Format)** is an open JSON data standard for representing recipes, techniques, ingredients, chefs, collections, and menus as a connected graph.
- **Forking** in Amanah preserves a verifiable, public link from every adaptation back to the original creator, so credit travels with the recipe.
- **Lineage** is the directed graph of recipe derivations — `inspired_by`, `variation_of`, `derived_from`, `translation_of` — that makes culinary evolution visible.
- **Canonical recipes** are community-promoted versions that meet quality gates (≥5 cooks, ≥4.5 average rating, 14-day approval window).

---

## How Amanah compares

| Capability                          | Amanah | Paprika / Whisk | NYT Cooking | Notion / Docs | Recipe blogs |
|-------------------------------------|:------:|:---------------:|:-----------:|:-------------:|:------------:|
| Structured open data standard (UMF) |   ✓    |        ✗        |      ✗      |       ✗       |      ✗       |
| Forking with attribution            |   ✓    |        ✗        |      ✗      |       ✗       |      ✗       |
| Public version history              |   ✓    |        ✗        |      ✗      |    partial    |      ✗       |
| Embeddable via oEmbed               |   ✓    |        ✗        |      ✗      |       ✗       |      ✗       |
| AI/LLM-native discovery files       |   ✓    |        ✗        |      ✗      |       ✗       |      ✗       |
| Translation as a first-class fork   |   ✓    |        ✗        |      ✗      |       ✗       |      ✗       |
| JSON-LD `Recipe` per page           |   ✓    |        ✗        |      ✓      |       ✗       |   partial    |
| Recipe → menu → shopping list       |   ✓    |        ✓        |      ✓      |       ✗       |      ✗       |

---

## Example queries an agent can answer with Amanah

**Q: "Find me Roy Choi's Korean-Mexican taco recipe and any forks."**
A: Resolve the chef at `https://amanah.food/chefs?q=roy-choi`, fetch the recipe page (which contains JSON-LD `Recipe` + UMF JSON), then walk the lineage graph from the recipe's `derived_from` and reverse-fork edges.

**Q: "Translate this recipe to Arabic and credit the original author."**
A: Translation is modeled as a fork with `translation_of` pointing at the source recipe. The translated recipe stands on its own but always carries an attribution link back to the original creator.

**Q: "Embed this recipe in my blog."**
A: Use oEmbed: `GET https://amanah.food/functions/v1/oembed-recipe?url=<recipe-url>` returns oEmbed 1.0 JSON with an `<iframe>` snippet pointing at `/embed/recipes/{id}`.

---

## Key concepts

- **Recipe**: structured UMF JSON — meta, ingredients, techniques, process, lineage, sharing, nutrition, media, history.
- **Chef**: rich contributor profile — origin, cuisines, specialties, affiliations, recognition, verification status.
- **Collection**: grouped recipes with collaborative roles and visibility controls.
- **Menu**: ordered set of recipes by course; generates a shopping list.
- **Technique**: reusable cooking primitive with steps, equipment, sensory cues, failure modes.
- **Potluck**: collaborative event with dish claims and chat.

## Routes for crawlers

- `/` landing
- `/about` what Amanah is
- `/for-ai-agents` quotable facts + code samples for agents
- `/recipes` public recipe browse
- `/@/{handle}/{slug}` public recipe page (JSON-LD + oEmbed discovery)
- `/embed/recipes/{id}` embeddable card
- `/evolution` recipe lineage explorer
- `/explore/repos` chef repositories
- `/techniques` technique library

## Schemas

- Recipe: https://amanah.food/recipe.schema.json
- Chef: https://amanah.food/chef.schema.json
- Collection: https://amanah.food/collection.schema.json
- Menu: https://amanah.food/menu.schema.json
- Technique: https://amanah.food/technique.schema.json

## License

Recipe content is licensed per author (attribution always required and machine-readable). The UMF specification itself is an open standard.