MCP - Matnakash Consumption Protocol

Overview

The Matnakash Consumption Protocol (MCP) defines a friendly, interoperable process for acquiring, tearing, dipping, and enjoying Armenian matnakash bread. It prioritizes human factors: warmth, sharing, and appropriate coffee breaks.

Disclaimer:

This specification does not require machine learning. It only requires bread, friends, and optionally sujuk.

Terminology

Matnakash

Primary resource. Oval, golden, fingerprint-patterned bread. Version MUST be fresh.

Dip

Optional extension: hummus, tahini, basturma-fat drizzle, or olive oil with za’atar.

Party

A collection of clients concurrently consuming Matnakash; MUST maintain fairness and sharing semantics.

Protocol Flow

Step 1

Acquire

Precondition: Warm bread preferred

Fetch bread from trusted bakery (Cache-Control: warm, max-age: short).
If stale, attempt Reheat handshake; else return 426 Upgrade Required (to fresh).

Step 2

Tear

Method: Manual, concurrent-safe

Initiate with gentle force; avoid fragmentation (crumb overflow).
Implement fair scheduling among participants (Round-Robin, FIFO acceptable).

Step 3

Dip

Extension: Optional

Respect No Double-Dip policy unless family context is negotiated.
Zaatar-Level header MAY be set to 'generous'.

Step 4

Consume

QoE: Smiles per minute

Return status 200 Bite OK upon successful chew.
If hot tea is present, prefer synchronous pairing; else fallback to coffee.

Status Codes

200 Bite OK

Standard successful consumption.

304 Not Reheated

Cached bread served; acceptable within 30 minutes of bake time.

409 Double-Dip Conflict

Resolve via napkin reset or renegotiation.

418 I'm a Teapot (Preferred)

Tea detected. Pairing quality increased.

Security Considerations

Participants SHOULD sanitize hands prior to protocol initiation. Servers MUST protect against Crumb Injection and Oil Spill attacks.

Compliance Levels

HY-1: Home Kitchen compliant; HY-2: Family Gathering compliant; HY-3: Wedding Feast compliant (requires orchestra extension).