A useful assistant.
Clear rules around every tool.
A rehearsal for the CPC office pilot: Microsoft identity, a bounded harness, a deterministic tool broker, and explicit approval before a write.
The boundary is in code
Personal Teams chat verified.
Private context, bounded requests.
Rules, approvals and audit outside the model.
MCP connector
Real MCP client/server exchange between separate containers over Streamable HTTP. Approved knowledge fixture.
New tools also need a typed adapter and access rule.CLI adapter
A fixed executable with typed operations. No shell or arbitrary command input.
Connector credentials stay server-side.Durable state
SQLite stores jobs, approvals and audit metadata. Replays cannot repeat a dry-run publication.
Production requires backup and restore acceptance.Try a complete workflow
The draft uses the local MLX model on Octopus with context from the approved MCP guide. The model is Qwen3.8-Flash-Next-Abliterated-MLX-Serve-mixed-4-8bit. Inference errors stop the request; there is no template fallback. No live campaign, mailbox or HR system is connected.
Marketing draft
Approval before publication
This writes only to the lab’s synthetic publication record. The exact text, owner and policy version are bound to the request.
Where the access matrix lives
Versioned config/policy.json is the source of truth in this lab. IT and the business owner review changes; the model cannot grant access.
| Role | Tool | Resource | Boundary |
|---|---|---|---|
| Pilot | Read knowledge | Approved brand guide | Read only |
| Marketing | Create draft | Lab campaign | Draft only |
| Marketing | Publish | Lab campaign | Exact human approval; dry run |
| Reporting / operator | Read summary | Synthetic sales | No employee or salary data |
| Operator | Inspect CLI runtime | Lab runtime | Fixed command; no shell |
| Every role | Change salary / create employee | Any | Always denied |
Capacity Entra identities use object IDs, not email suffixes. Demo identities use a separate synthetic tenant.
Your Microsoft files, with your own login
CPC Microsoft files panel — requires separately configured CPC connectors; disabled by default.
Obot Microsoft demo: Excel uses a reviewed tool selection for reading worksheets and adding rows or columns. Each user authenticates separately through Microsoft. Open the Microsoft vMCP.
These connectors run at Obot.ai for this demo. We must replace them before CPC production. Their direct file tools use Obot profiles and Microsoft rights. They do not inherit this page’s campaign approval workflow.
Personal Excel and OneDrive OAuth completed. OneDrive drive listing and Excel workbook listing succeeded. Excel MCP worksheet creation, six-row write and read-back succeeded. Teams file creation and two-user isolation remain open.
What we can settle in the call
Presentation PDF · Editable presentation · CPC how-to PDF · Mike’s permission and delegation memo
First useful workflow
Pick a marketing task the office team can repeat. Agree the material and who reviews the output.
Identity & hosting
CPC tenant account, Teams availability, bot registration, and a CPC-owned runtime with named IT owners.
Rules & milestone
Choose pilot users, resource boundaries, approval rules, and acceptance evidence before adding capabilities.
Still to validate: CPC tenant setup, two-user Microsoft file isolation, production model approval, HR isolation and production operations.