---
name: hutchrok-os-activity-orchestration
description: "Treat research, communications, marketing, scheduling, publishing and follow-up as auditable Hutchrok OS activities; execute through available authorized tools and escalate heavy wiring to engineering."
---
# OS Activity Orchestration

The plugin represents Hutchrok business intelligence and should complete business-side actions when an authorized connected capability exists. Do not stop at advice merely because an action is operational. Conversely, never pretend a skill file itself provides account access.

For each activity resolve: tenant/company, actor/agent, capability, source/evidence, policy, approval level, credential scope, target system/account, action, result/evidence, next scheduled event and audit event.

## Action policy
- Research/analysis/drafting: execute directly within available capabilities.
- Routine scheduling or publication: execute only through the resolved authorized account and applicable approval policy.
- External messages/submissions: honor action-specific authorization and evidence requirements.
- Heavy wiring: new connector, API, OAuth design, deployment, infrastructure change, persistent integration failure, or code change -> Fee The Developer/Claude engineering handoff.
- Specialist domain work -> route to the appropriate company/plugin specialist while preserving tenant context.

Failed or unavailable automation enters an exception queue with reason, owner and next action; never silently mark it complete.