outcome-owned-agent-patternlisted

# Outcome-owned agent pattern (steal from Grok Bot) Canonical product docs: [Grok Bot overview](https://docs.x.ai/grok-bot/overview), [skills & routines](https://docs.x.ai/grok-bot/skills-routines-and-automations), [approvals](https://docs.x.ai/grok-bot/approvals-security-and-privacy), [use cases](https://docs.x.ai/grok-bot/use-cases). This skill maps those ideas onto **our** fleet (Hermes, Grok Build, Cursor, Grok Bot desktop, LaunchAgents) — not a reimplementation of their cloud VM. ## Steal matrix (high ROI only) | Grok Bot idea | Do this here | Do not | |---------------|--------------|--------| | Bot owns a **repeatable outcome** | One charter per role (job + systems + format + stop rules) | Vague “help with coding” agents | | **Draft / prepare first** | Every outbound, publish, spend, prod change stops at draft | Auto-send “to be helpful” | | **Task → skill → test → routine** | One live success, save method, second input test, then schedule | Schedule on first try | | **Narrow event triggers** | Phrase + ticket link / label match | “Every Slack message” | | **Missing/stale data = fail loud** | Report source failure; refetch; never invent | Silent empty or yesterday’s cache as truth | | **Prefer connectors/API** | `gh`, Gmail API, Linear, Stripe CLI | Hijack Igor’s Chrome (ban) | | **Shared computer ≠ security boundary** | Assume shared sessions across fleet bots | Separate bots as isolation | | **Human for secrets/2FA** | Secure handoff / Keychain / take-over | Passw