Obligations (shared calendar, alerts, rule registry)

2 entities and 5 agent-callable operations in obligations. Each operation is addressed as {mega_tool}/obligations/{entity}/{operation} and carries the same permission check over MCP and REST.

`business_day_calendar`

Operation	Mega-tool	What it does
`get`	`report_query`	Resolve ONE calendar key the way a date roll resolves it: your organization's own list for that key, else the platform SYSTEM list, else nothing.
`list`	`report_query`	Every business-day (holiday) calendar your organization can see: its OWN calendars plus the platform-wide SYSTEM calendars.
`upsert`	`smart_action`	Load or replace YOUR organization's business-day (holiday) calendar for one key.

`construct`

Operation	Mega-tool	What it does
`get`	`report_query`	One typed construct schema, whole.
`list`	`report_query`	The catalogue of typed contract-construct schemas an extraction runner emits against: obl:schedule@v1, obl:deadline@v1, obl:test@v1, obl:ordering@v1.

Parameter schemas and permission codenames are in the full reference — sign in — or call prism_introspect(dimension="capability_search", query="…") with your key.

In the full reference this application appears under report_query, smart_action.