The Cedric manual.

The difference between a request that comes back perfect and one that comes back close is usually four words. A practical guide to asking well, with before and after examples.

How Cedric reaches the systems that hold your work: what scoped access means, what to connect first, how to revoke, and what he can and cannot see once connected.

Cedric asks before he sends, changes, or spends. What that means exactly, which actions are gated, what happens when you say no, and why the gate is not a setting you can quietly remove.

Invite Cedric to a call by link or calendar invite. He takes notes, answers when addressed by name, queues actions for approval, and posts the summary when the call ends.

Move the weekly report, the daily check, and the monthly reconciliation onto a schedule. How to set one up, what stays gated, and how to avoid automating something wrong.

Some work spans days and people: collect from five, then book; send the form, then act on the answers. Cedric runs it as a workflow that waits, nudges, and finishes.

Cedric keeps one shared memory for your team: corrections stick, documents can be taught, everything he knows is listed on one page, and delete means delete.

Teach Cedric how your team works once, and it sticks: house style, report formats, and per-tool playbooks, saved from chat in a sentence and removable in a click.

If a tool speaks MCP, the open standard for connecting tools to assistants, Cedric can use it: registered in a minute from chat, gated by the same approvals as everything else.