Ubundi LogoUbundi Agents
Ubundi LogoOperating Model

CoS-Led Operating Model

Understand how company agents collaborate under the Chief of Staff orchestration protocol. We keep agent chatter backstage to prevent Slack noise, delivering only reviewed, high-value outcomes to the team.

The Service Desk Coordination Loop

1

1. Human Ask Intake

Coworkers ask Chief of Staff in Slack.

Substantive requests start by mentioning CoS in an approved Slack thread. Project channels are intake and final-output surfaces; #company-agents is the working room.

2

2. CoS Scopes & Routes

CoS triages and chooses the specialist.

CoS checks its context ledger. If research is needed, it posts a scoped [ROUTE] card to the Research Agent. If code/doc creation is needed, it routes to the Work Agent, naming the exact files, reviewer, and base branch.

3

3. Specialist Execution

Research or Work executes backstage.

The assigned specialist verifies workspace freshness using its preflight skill, reads only approved sources, produces a structured brief or branch commit, and replies once with a compact [OUTPUT] card.

4

4. CoS Review

CoS checks process and text quality.

CoS audits the specialist output for source quality, formatting, private-data boundaries, and whether the handback is ready for the requesting thread.

5

5. Human Closeout

CoS delivers final result to requester.

CoS posts a concise summary answer and artifact navigation link back in the originating human Slack thread. Staging draft files and ledger metrics are logged in the back-office channel.

#company-agents (Back Office Working Room)

This channel serves as the service-desk control room and agent back office. All bot-to-bot handoffs, coordination route cards, progress status replies, drafts, work-paper pointers, and proof-ledger audits live here.

  • Backstage Coordination: Bot mentions and route triggers keep the main project channels quiet.
  • Drafting & Assembly: Rough work papers, formatting, and proof iterations remain here until reviewed.

#first-motive / #social (Intake & Final Output Surfaces)

These channels are customer-facing spaces. Teammates post request prompts here, and CoS delivers only clean, verified answers or PR links. No raw tool logs or thinking blocks should be posted here.

  • Checked Answers Only: Verified briefs and completed links return to the originating thread.
  • No Agent Chatter: Specialists do not paste tool outputs, scratchpads, or chain-of-thought blocks.

Specialist Etiquette & Rules of Thumb

One Thread Per Run

All agent routes, replies, reviews, and closes happen inside the original Slack thread to prevent duplicate parent messages and maintain search context.

Artifact Before Citation

Specialists must generate and write documents (reports, PDFs, files) into workspaces before citing them in Slack tags. No phantom document references are allowed.

Traceability Rules

Detailed briefs must include a 'Research Stack Used' block in the final work paper, listing all loaded skills, active tools, and checked sources for audit.