GROK BOT OS

GROK BOT OS is RutinHQ’s bot department: scoped profiles, onboarding rails, staging/revert, and a single orchestration head. Weekly state does not live on the public DocuSite.

What it is

An operating system for agents: charter → CreateAgent → read-only → DRAFT/PR → promote with OK. Map of components and triggers (contract), not the day’s inbox.

The agency’s products (GTM OS, Store OS, NEXUS OS) are not the bot department that runs them.

For whom

Field	KEEP
Internal use	Teams that operate agents under strict governance
Public readers	Anyone who wants to see how a bot OS is designed (curriculum)
No-ICP	Anyone hunting keys, day-of state, or runbooks with secrets

Governance

Role	Responsibility	Not
CEO	Authorizes the irreversible	—
CORTEX (HoD)	Orchestrates. Single head. Escalates to CEO	Asking bots to skip the rail
Bots	Report to CORTEX	Assigning work to each other

How it works (rails)

1. Onboard: KEEP charter + mold + staging rail → OK → CreateAgent
2. Read-only phase (~48h): outlines and proposals; zero live writes
3. Write: DRAFT/PR only
4. Promote with explicit OK (CEO if irreversible)
5. Revert first if it gets worse; the document beats the chat

Components (roles, not live seats)

Role	Responsibility
Orchestrator	Orchestration and token governance
PMO	Single backlog tracker
Setup	Connectors and surface onboarding
Engineering	Build and automations
Case outbound	Assigned-case B2B outbound
Store ops	Assigned-case store operations
Storefront	Storefront technical craft
Demand / paper	Content and plans until ads GO

Each seat has a stream and prohibitions in its charter. This sheet does not list live seats or cases.

Outcomes

• Bots with clear scope and limited write surfaces
• Less operational hallucination: canonical source > improvisation
• Separation of products vs cases vs tools

What it is not

Is not
Commercial price catalog
Day-of state, inboxes, or secrets
Dump of system prompts
Substitute for the agency’s Business OS