You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- An **OnTime User** may own zero or more **Schedules**.
131
+
- A **Schedule** has one **Place**.
132
+
- A **Schedule** may use one **Preparation**.
133
+
- A **Preparation** contains zero or more **Preparation Steps** in user-defined order.
134
+
- A **Preparation Step** belongs to exactly one **Preparation**.
135
+
- A **Schedule Notification** uses **Schedule** and **Preparation** timing, but is not itself a **Schedule** or **Preparation**.
110
136
- A **Product Usage Event** may describe a schedule, preparation, notification, alarm, onboarding, or account action without storing the user's raw schedule names, notes, place names, credentials, tokens, or free text.
111
137
- First-release **Product Usage Events** are **Workflow Milestone Events**, not every tap or raw navigation step.
> **Dev:** "Should the analytics event include the schedule note so we can understand why users are late?"
156
182
> **Domain expert:** "No. A **Product Usage Event** can say a schedule was finished late, but it must not include the user's raw note."
157
183
184
+
> **Dev:** "Can a **Schedule Notification** replace the **Schedule** if the user taps it?"
185
+
> **Domain expert:** "No. The **Schedule Notification** only prompts preparation for the **Schedule**; the **Schedule** remains the planned commitment."
186
+
158
187
## Flagged ambiguities
159
188
189
+
- "User" was overloaded as both the human actor and stored profile; resolved: use **OnTime User** for the account/profile concept and plain user only for the person performing an action.
190
+
- "Schedule" was used near notification and alarm flows; resolved: a **Schedule** is the planned commitment, while notifications and alarms are delivery experiences for preparation timing.
191
+
- "Preparation state" was ambiguous between step progress and display styling; resolved: **Preparation Step** progress belongs to preparation language, while visual labels should not redefine the domain.
160
192
- "User activities" was used broadly; resolved: the canonical term is **Product Usage Event**, and raw personal content is out of scope.
161
193
- "Analytics" was used to include all possible purposes; resolved: marketing and personalization are deferred, not first-release purposes.
162
194
- "User identity" for analytics was ambiguous; resolved: analytics uses a **Pseudonymous Analytics Subject**, not directly identifying user data.
0 commit comments