Project Homey: The Household Ecosystem

Product model for equal household access and planning-oriented versus execution-oriented intent.

1. The Human Dynamics

Homey is built on the principle of Equality of Access but Differentiation of Intent. While every household member is an equal partner, their interaction with the home varies based on their current activity.

2. Defined Functional Roles

To simplify the user interface, the app recognizes two distinct modes of operation.

Role	Primary Intent	Key Actions
The Owner (Architect)	High-level planning and financial management.	Scanning bills, managing "Almarah" locations, setting the weekly menu, and reviewing stock levels.
The Chef (Executor)	Daily operational management.	Viewing the day’s menu, checking ingredients, marking items as "used/completed," and flagging shortages.

Role

Primary Intent

Key Actions

The Owner (Architect)

High-level planning and financial management.

Scanning bills, managing "Almarah" locations, setting the weekly menu, and reviewing stock levels.

The Chef (Executor)

Daily operational management.

Viewing the day’s menu, checking ingredients, marking items as "used/completed," and flagging shortages.

3. The Synchronization Bridge (The Code System)

To maintain the "Local-First" simplicity while allowing multi-device support, Homey uses a Temporary Access Token system.

Master Device: The "Owner" phone holds the master database.
The Token: The Owner generates a unique alphanumeric code.
The Hand-off: The "Chef" enters this code to sync the current house state.
Validity: The code is permanent for 30 days. After 30 days, the Chef must renew the token to ensure the household data remains secure and up-to-date.

4. The Feedback Loop: How the House "Talks Back"

The inventory is only as good as the Chef’s feedback. 1. The Recipe Trigger: When the Chef selects "Cook Now," the app displays the required ingredients. 2. The "Empty" Signal: Once cooking is done, the Chef marks the item as "Finished." 3. Inventory Update: The app automatically subtracts those items from the master list. 4. The Owner’s Review: The Owner sees these updates reflected in the weekend "Nudge" list.

5. Notification Ownership & Hierarchy

Homey follows a "Need to Know" basis for notifications to avoid digital clutter.

The Weekend Nudge (Owner): Only the Owner receives the proactive shopping list reminder. This aligns with the "Architect" role of ensuring the house is ready for the coming week.
The Ingredient Shortage (Chef): The only scenario where a Chef receives an alert is if a planned meal is missing an ingredient at the moment of cooking.
Vacation Mode: A global toggle that pauses all "Live" house alerts, switching the app to "Deep Freeze" mode (monitoring only long-term maintenance or pre-return audits).

6. Exploration Summary (Decision Log)

Topic	Outcome & Rationale
Role Partitioning	Architect vs. Executor. Rejected a "Admin vs. User" hierarchy to maintain the feel of a shared home while keeping the UX focused.
Sync Strategy	30-Day Renewable Tokens. Provides a middle ground between "no sync" and a complex "user account/password" system.
Device Logic	Single App Model. One app for all users. The "Chef" login is simply a view-filter on the same core product logic.
Chef Notifications	Minimalist. Chef avoids the "Weekend Nudge" to prevent redundant alerts, as the Owner is the designated shopper/planner.

Topic

Outcome & Rationale

Role Partitioning

Architect vs. Executor. Rejected a "Admin vs. User" hierarchy to maintain the feel of a shared home while keeping the UX focused.

Sync Strategy

30-Day Renewable Tokens. Provides a middle ground between "no sync" and a complex "user account/password" system.

Device Logic

Single App Model. One app for all users. The "Chef" login is simply a view-filter on the same core product logic.

Chef Notifications

Minimalist. Chef avoids the "Weekend Nudge" to prevent redundant alerts, as the Owner is the designated shopper/planner.