Check the setup
check_setupCheck whether every signal this workspace raises has a way to be handled, and what repairs each missing link. Use it when signals go unhandled or your human asks what is missing in the setup; use list_signals for the open work itself. It checks the chain from the map to a recorded completion and lists each gap with a severity, the item it concerns and the single next step: a signal kind nothing handles (no approved, anchored playbook and no automation); open signals piling up unacted, or past their severity's time (4 hours urgent, 24 attention, 72 info); a playbook in draft, anchored on nothing, naming an undeclared operation or a missing object, or whose trigger is not wired; an operation with no action policy or no live key able to ask for it; a join a playbook crosses that is neither confirmed nor measured; a source with unknown owner or refresh cadence; an automation registered active with no run reported for 8 days; an uploaded system no connection keeps fresh; a plan past its due date. The answer leads with one job per playbook, signal kind or operation; every gap says what your human opens to fix it (with a link) and, where you can help, what to do. Changes nothing; a scoped key sees only gaps about objects in its scope. Maplith runs it hourly and raises each gap as a setup_gap signal until a check no longer finds it.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||