Task Aging
Unfinished task age and time in the current column, with owner and due-date context; excludes archived and cancelled tasks from active workload.
Collaborate and follow up
Share the right context and keep time-sensitive work visible.
3 stages · 0 approvals
Roles and responsibilities
Process steps
Follow the process from start to finish. Select a step to see who acts and what changes.
Discuss task
Members post TaskComments and protected TaskAttachments with the intended audience. Guests can read only Shared content on their explicitly shared tasks, and can comment only with a Comment grant. Parent comments must belong to the same task. Mentions notify only currently authorized participants. Withdrawn files and deactivated memberships lose effective download access even through an old link.
Follow up on dates
The reminder service evaluates DueDate in the board timezone and schedules a unique NotificationDeliveries occurrence for the intended current owner or reviewer. Recheck the task, audience and date immediately before sending. Completed, cancelled, archived or rescheduled work suppresses an obsolete reminder. Provider acceptance and observed delivery remain separate, and an unknown result keeps its original operation key for reconciliation.
Review flow
Board Owner reads BoardSnapshots and event-based reports with their time window, timezone and DefinitionVersion. Distinguish completed cycles from reopened work and unfinished aging. An empty result has no measured cycle time. Compare owners’ workload in context; task counts alone do not establish productivity. Viewer receives only the permitted board reports, and Guest has no board-wide analytics or export.
Approvals and controls
0 approvals required in this process
- Recheck copied attachment links and queued notifications.
- Suppress obsolete remindersMessages to deactivated guests.
- Keep uncertain provider outcomes tied to their original operation.
Records and postings
| Stage | Records | Effect |
|---|---|---|
| 1 Discuss task | TaskCommentsTaskAttachmentsTaskParticipants | Preserve conversation audience |
| 2 Follow up on dates | TasksNotificationDeliveries | Send one relevant authorized reminder |
| 3 Review flow | BoardSnapshotsTaskEvents | Explain observed outcomes in context |
Process reports
All reportsCycle Time
Observed elapsed start-to-completion hours by task cycle, including explicit rework cycles and null where an observation is incomplete.
Ownership and Workload
Active task count by accountable owner and priority within board scope; task count is not a productivity ranking.
Board Flow Summary
Dated snapshots by board and reporting window: active work, overdue work, completed cycles and reopened cycles with the definition version.
Due-Date Performance
Compare retained completion events with the due date applicable at that event; later due-date edits cannot rewrite earlier on-time results.
Run by an agent
Agent support
This system owns daily boards, checklists, dependencies, controlled handoffs and scoped collaboration. Customer invoicing, payroll, formal sprint commitments and resource-cost planning are outside its scope. Proto prepares work and explains blocked transitions; it cannot supply independent approval.
# Example after configuration
$ curl -fsSL https://www.erp.ai/skill.md | paste into your agent
› collaborate and follow up · discuss task on TaskComments, TaskAttachments, TaskParticipants
✓ Members post TaskComments and protected TaskAttachments with the intended audience.
› collaborate and follow up · follow up on dates on Tasks, NotificationDeliveries
✓ The reminder service evaluates DueDate in the board timezone and schedules a unique NotificationDeliveries occurrence for the intended current owner or reviewer.
› collaborate and follow up · review flow on BoardSnapshots, TaskEvents
✓ Board Owner reads BoardSnapshots and event-based reports with their time window, timezone and DefinitionVersion.
Other processes
3 moreSet up and capture work
Create the board boundary and bring useful work into it.
3 stages · 0 approvals
Complete and revisit work
Preserve a finished outcome when work needs another cycle.
3 stages · 0 approvals