Expansion layer
These are not restaurants. They are subscription-linked community dining nodes for freshness, trust, and local density.
Core components are prepared two to three times daily. Final seasoning and assembly happen around confirmed arrival slots.
Physical joints become proof points: users can see creator skill, kitchen standards, ingredient quality, and neighborhood reliability in person.
| System | Operational Logic | Primary Metric |
|---|---|---|
| Batch Predictor | Uses subscription demand and reservations to plan prep cycles. | Waste percent and sell-through rate. |
| Kitchen Visibility | Routes real prep clips and creator identity into the customer menu. | Trust score and repeat visits. |
| Arrival Tracker | Coordinates table slot, kitchen finishing time, and customer ETA. | Average delay and seat turnover. |
| Membership Wallet | Converts neighborhood users into recurring dining credits. | Monthly recurring revenue. |