What ships
- Task — one unit of work: the source key that raised it, the deep link to the page where the work happens, the assignment (who, by whom, when), the due date, priority and stored status, and the endpoint sentence saying what closes it.
- Team Member — the roster as data: free-vocabulary specialties, rated skills per source kind, working weekdays and booked absences, and the track record the scorer weighs.
- Board — the desk: what is open (most urgent first, each row opening the raiser's own page), what has been closed, and who is available today with the load they carry. Derived live, stores nothing.
- Samples — a worked desk: five people and six items raised by four different sources against nodes in other modules.
How a task is raised
Any module raises work by writing a task node whose source key is <kind>:<subject> — the condition, then the node it is about. Nothing here takes a C# reference to the raising module: a subject is a path, a deep link is an href, and both keep working when the module they name is not installed.
| Kind | Raised when | Closed when |
|---|---|---|
dl |
a decision window is closing | the decision moves off Pending |
evt |
a severe event lands on the feed | the event is cleared from the feed |
impact |
an event is modelled onto the book | the impact is acknowledged |
drift |
the held book drifts off target | the drift is reconciled |
stale |
a feed stops refreshing | the feed is refreshed within 2 h |
review |
somebody asks for a review | the review is recorded |
manual |
a person raises it by hand | by hand |
How it is assigned
The scorer weighs four things and shows its arithmetic: 40 points for the rated skill at the item's kind, 25 for a specialty match, 20 for the track record, minus up to 15 for a full plate. Anyone not working that day scores zero — an exclusion, not a penalty — so an item never lands on someone who is on leave.
Why it is its own module
Employee task management is not an insurance capability, so it does not live inside one. It was carved out of the ILS decision process and made generic: any module raises a task by source key, the board assigns and tracks it, and the endpoint says what closes it. The types know nothing about cat bonds, books or perils — only about paths.