My Day
/Review and plan today’s selected tasks.
Momentis is a personal task workspace for lists, daily planning, reminders, recurring work, smart views, templates, and lightweight collaboration. It keeps individual planning separate from team project delivery in Kinetis.
Organize personal work with lists, My Day, tasks, steps, reminders, recurrence, templates, sharing, and recovery.
Covers current beta task and list workflows. Momentis is intended for personal work and light shared lists; team project delivery belongs in Kinetis when that product is released.
| Role | Access | Responsibilities |
|---|---|---|
| Task user | Manage personal lists, My Day, tasks, reminders, templates, calendar, and search. |
|
| Shared-list participant | View or update shared work according to assigned permission. |
|
| Operator | Support tenant, scheduler, storage, or notification behavior outside normal use. |
|
Use clear outcomes, one accountable owner, and realistic dates rather than treating the task list as passive storage.
Place the task in the correct list and define the next executable action.
Search for existing work and open the list that owns the outcome.
Use an action-oriented title and add only the context needed to complete it.
Choose priority, due date, reminder, labels, and recurrence only when meaningful.
Break multi-action work into ordered, verifiable steps.
Confirm list, date, recurrence, reminder, and any assignment.
The task appears in the intended list with a clear next action and reliable planning metadata.
Select a realistic subset of tasks for focused daily execution.
Use Smart lists, Calendar, and assigned lists to understand obligations.
Choose work that can reasonably be completed or advanced today.
Place blocking or time-sensitive work before optional tasks.
Reschedule, delegate, or clarify tasks rather than carrying an impossible list.
Complete finished tasks and deliberately reschedule or remove unfinished work from My Day.
My Day is a current, bounded plan rather than an accumulation of all open tasks.
Create one durable schedule and test its next occurrence.
Confirm time zone and choose a reminder early enough to act.
Set interval, start, and end or count according to the real obligation.
Verify the displayed next due and reminder state.
Confirm the next task or schedule is produced as expected.
Snooze the notification without changing the underlying due date only when that distinction is intended.
The reminder and recurrence create one predictable sequence with a correct next occurrence.
Light collaboration adds visibility and notification risk; use least privilege and retain an owner for every task.
Share the smallest list scope with the least permission needed.
Remove personal notes, unrelated tasks, and prohibited attachments before sharing.
Use the list sharing action and verify identity and tenant.
Grant view or contribution rights according to the collaboration purpose.
Set one owner and due date and use comments for relevant context.
Confirm expected access and remove it when collaboration ends.
The intended participant can access only the shared list and assigned work with an accountable owner.
Preview bulk creation and use Trash as recovery, not records retention.
Use a template for repeatable work, import for reviewed external data, export for an approved portable copy, or Trash for recovery.
Check task count, target list, dates, assignments, labels, and attachments.
Avoid duplicate template application or import while processing.
Sample created or exported tasks and correct dates or ownership.
Confirm identity before restore; use permanent deletion only under policy.
Bulk or recovery work produces the intended tasks without duplicates, unintended sharing, or lost ownership.
These limits describe the source-pinned Momentis 0.1.0 beta scope and must be rechecked when the product changes.
Likely cause: The session expired, the identity is not assigned to the application, or the tenant claim is missing.
Likely cause: The current role, release, tenant configuration, or feature flag does not expose that operation.
Likely cause: Validation failed, processing is still running, or the current view is stale or filtered.
Likely cause: Time zone, schedule, completion state, worker, or notification delivery is incorrect.
Likely cause: The action was submitted more than once or the source already existed.