Trust
Morris does a lot on his own. He also asks a lot. The line between the two is the product.
This page is the charter every pilot starts from. It describes defaults, not promises: the starting position for what Morris may do without asking, and what he never does without a person.
WHAT MORRIS DOES ON HIS OWN
- Reading and understanding requests across email, Slack and your tracker
- Separating one message into its concrete asks
- Checking whether the work already exists before creating it
- Creating, updating and routing tickets
- Bounded engineering work, delivered as a pull request for review
- Following up on stalled work with the right person
- Verifying results before reporting them
- Drafting internal updates and client-facing status
WHAT MORRIS ALWAYS ASKS ABOUT
- Anything that leaves the company — every client email or message
- Anything that moves money — invoices, quotes, refunds, renewals
- Anything that changes production — deploys, data, config
- Anything irreversible, or that touches people decisions
Morris still does the thinking on these — the investigation, the recommendation, the draft. The difference is whether he is allowed to execute.
Default authority
What Morris may do, by default, in every pilot.
Morris asks when consequence is high. Authority is earned through evidence, not switched on: expanding any row below is a decision the owner makes, with a record of why.
- Read and understandYES
Across every connected tool, continuously.
- Internal draftYES
Messages, notes, summaries for the team.
- Create internal workYES
Tickets, updates, assignments in your tracker.
- Run bounded engineeringYES
Scoped changes, delivered as a PR for human review.
- External sendAPPROVAL
Any message to a client or third party.
- Financial actionAPPROVAL
Anything that moves or commits money.
- Production mutationAPPROVAL
Deploys, data changes, infrastructure.
| ACTION | DEFAULT | WHAT THAT COVERS |
|---|---|---|
| Read and understand | YES | Across every connected tool, continuously. |
| Internal draft | YES | Messages, notes, summaries for the team. |
| Create internal work | YES | Tickets, updates, assignments in your tracker. |
| Run bounded engineering | YES | Scoped changes, delivered as a PR for human review. |
| External send | APPROVAL | Any message to a client or third party. |
| Financial action | APPROVAL | Anything that moves or commits money. |
| Production mutation | APPROVAL | Deploys, data changes, infrastructure. |
Evidence over narration
Morris only says “done” when he can show the receipt: a merged pull request, a deployed URL, a passing check, a ticket in its final state. A claim without evidence isn't a status update; it's a story.
When he can't verify something, he says he can't verify it — and what he would need in order to. That applies to his own work as much as anyone else's.
Your tools stay yours
Morris doesn't replace the systems your company runs on. He becomes intelligent across them. The record of work lives where it already lives; if you turned Morris off tomorrow, nothing would be missing.
- Linear / Jira
- owns the tasks
- GitHub
- owns the code
- Slack / Gmail
- owns the conversations
- Morris
- owns the understanding across them
The charter is the same for every pilot.
It gets discussed, in writing, before Morris reads a single message of yours. Ask us anything about it.