CloudWinks · Foundation apps

BusyBodyTechnical brief

BusyBody is the personal window onto a person’s calendar, goals, meetings and other commitments. It brings those activities together and opens the app that owns the work, rather than copying that work into a second list.

Read the business brief · PDF

1. Architecture in brief

BusyBody is a Foundation app with personal tenancy. It holds appointments, events, meetings, goals, milestones, activities, reflections and related reminder records. TaskMaster remains the authority for personal and company tasks and projects. CloudWinks supplies the application runtime and Crux the shared identity and time-zone references.

2. Service boundary and intake

Personal calendar and activity entries are created in BusyBody. When the item is a task owned elsewhere, BusyBody opens that app’s named control rather than promoting the work by copying it. Contact import writes the person’s Rolodex address book: Crux find-or-create when a phone or email is present, otherwise a name-only Rolodex draft.

3. Data handled

The model stores appointments, events, meetings, goals, milestones, activities, reflections and personal reminder context. BusyBody owns the personal calendar and activity window, not the TaskMaster task, the TimeTracker entry or the Rolodex address-book entry.

4. Integrations and ownership

BusyBody subscribes to other apps and sources, including TaskMaster, Google Calendar and Microsoft To Do, and combines their items in calendar, Gantt, list and other views; each item opens in its owning app. TaskMaster owns tasks and projects; BusyBody presents a personal view and opens TaskMaster controls. Outside sources such as Google Calendar connect through CosmosCall and the person’s own KeyKook connected account. TimeTracker records time independently. Rolodex is the address book for imported contacts, linked to Crux records. TjingTjing “My payslips” and BeanCounter personal books open as owning-app controls. Conductor can time a reminder. BusyBody owns the personal window, not those other records.

5. Security and access

The personal window respects the source app’s permissions; aggregating a view does not grant extra access. Opening an owning-app control repeats the authorization check. Company task data is not stored as a second copy in the personal window. Identity and access remain with Crux and KeyKook.

Competitive context

AlternativeIts focusCloudWinks product focus
Google CalendarEvents, invitations, reminders and shared calendars.A personal activity window that opens the CloudWinks app that owns the work.
Microsoft OutlookAppointments, meetings, reminders and scheduling tools.Personal calendar and goals alongside, not instead of, the shared task service.

Read the business brief →

← More Foundation apps apps · All application briefs · How the framework works