CloudWinks · Foundation apps

TaskMasterTechnical brief

TaskMaster organizes the work itself—tasks, work orders, projects and the checklists that go with them. It is the shared place for personal and company work, so other apps open TaskMaster rather than keeping a second task list.

Read the business brief · PDF

1. Architecture in brief

TaskMaster is a Foundation app with personal and company tenancy. It holds boards, projects, phases, tasks and work orders, dependencies, crews, assignments, templates, checklist items, recurrence rules, service-level policies and append-only task events. CloudWinks supplies the application runtime and Crux the shared identity. Other apps point at a task; they do not keep a second work engine.

2. Service boundary and intake

Work is created on a board or project, assigned, and advanced through status and checklist responses. Recurring templates are materialized when the shared clock says they are due. Another app can create or open a task through TaskMaster services rather than copy the work. Opening from the personal window uses a named control and repeats the authorization check. History is written as events; it is not edited in place.

3. Data handled

The model stores boards, projects and phases, tasks and work orders, dependencies, crews and assignments, templates and checklist snapshots, recurrence rules, service-level policies and append-only events. Cost codes belong to BeanCounter; tasks and time records reference them. TaskMaster owns the work record and its history. It does not own the time punch, the place, the evidence file or the message.

4. Integrations and ownership

BusyBody opens TaskMaster controls. TimeTracker may point at a task. Roady supplies places and zones. Conductor times recurring work. MediaMogul holds checklist evidence. Industry apps create work orders here. TheBoss TASK and APPROVAL steps create TaskMaster tasks and receive the result back. BeanCounter’s month-end close and LandMan maintenance requests are tasks here. Cost codes come from BeanCounter. TaskMaster owns the work record, not those other services.

5. Security and access

Access follows personal and company owner boundaries and platform grants. Opening a control from another window repeats the authorization check. A board view is not a grant to every task. Task history is append-only. Identity and access remain with Crux and KeyKook.

Competitive context

AlternativeIts focusCloudWinks product focus
AsanaTasks, projects, dependencies and multiple project views.One task and work-order record used across CloudWinks field, farm and company work, with checklist evidence in MediaMogul.
monday.comBoards, items and automations for team workflows.Operational tasks and work orders tied to CloudWinks places, crews and time records.

Read the business brief →

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