decision-clock

You can track open decisions by creating records with assigned owners, deadlines, and statuses. The system monitors these entries and sends notifications for overdue or soon-to-be-overdue deadlines to ensure compliance.

Managing decision workflow deadlines in a fleet system is best handled by centralizing decision storage in a Cosmos database and using a fleet-dispatch system for notifications. This ensures that all open decisions, owners, and statuses are tracked and acknowledged on time.

Yes, you need access to a Cosmos database for decision storage. The system requires this dependency to persistently track decision categories, owner assignments, status updates, and deadline compliance.

To open a new decision record with a specific owner and expected date, use the command: `node skills/decision-clock/decision.mjs open --category <category> --owner <owner> --expected-by <date>`. This initiates the decision tracking process.

Yes, you can receive notifications for overdue or soon-to-be-overdue decisions. The system integrates with a fleet-dispatch notification mechanism to alert assigned owners when decision deadlines are approaching or have passed.

You should not use a script-based decision tracking workflow if your environment lacks a Cosmos database or a fleet-dispatch system. Without these dependencies, the system cannot store decision records or send overdue deadline notifications.