README.md

The README.md exists for one reader: you, three months from now, when you’ve forgotten how this folder works.

CLAUDE.md is for Claude. README.md is for the human. They serve different audiences and shouldn’t duplicate each other.

What to include

• Quick-start commands — how to actually use the folder
• A pointer to the maintenance cadence (monthly context updates, quarterly voice refresh)
• The current setup state of integrations that take time to land (Outlook, Python, brand templates)
• Shell aliases worth adding
• Troubleshooting notes for likely failure modes

What to exclude

• A full description of what each file does — that’s covered in this Playbook section, no need to repeat
• The folder structure diagram — already in CLAUDE.md and the Playbook
• Setup steps from scratch — those belong in the Playbook, not in the folder itself

Template

# Command Centre

Personal AI command centre. This folder is opened in Claude Code
(terminal) or Cowork (desktop) to drive inbox triage, reply
drafting, and document generation.

## Quick start

From terminal:

    cd ~/command-centre
    claude

Then ask Claude in plain English. Examples:

    "run the morning brief"
    "triage my inbox"
    "build a deck from outline.md, this is for an external client"
    "draft a reply to the latest email from [name]"

Claude reads workflows/[name].md to know what to do.

## Maintenance rules

These exist so the system doesn't degrade over time:

1. Update context/ files monthly. New people in people.md, project
   state changes in projects.md.
2. Add real sent emails to voice.md every quarter. Voice drifts.
3. Don't add new workflow files speculatively. Only add a workflow
   when I've done the same task three times manually and want it
   codified.
4. Keep CLAUDE.md under 80 lines. If it grows, the model starts
   ignoring it.
5. Review outputs/ quarterly. Delete old briefs and drafts so the
   folder doesn't become a junk drawer.

## Setup state

- Python: 3.11+, with python-pptx and msal installed
- Outlook integration path: [AppleScript / Graph API — fill in
  once chosen]
- Tenant app registration: [ticket number / status]

## Aliases (~/.zshrc)

    alias cc='cd ~/command-centre && claude'
    alias brief='cd ~/command-centre && claude "run the morning brief"'
    alias triage='cd ~/command-centre && claude "triage my inbox"'

## When something breaks

- Drafts looking generic → voice.md is stale, refresh examples
- Triage missing important emails → priorities.md needs new
  rules, probably a new sender tier
- Deck script failing → most likely template placeholder indices
  changed, run scripts/inspect_template.py
- Claude ignoring CLAUDE.md → it's grown too long, prune it

A note on the setup state section

The “Setup state” section deliberately has placeholders. Filling them in is part of the work — not because the file forces you to, but because future-you will need to know whether the Outlook integration is via AppleScript or Microsoft Graph, and whether the IT ticket landed.

Treat the README as a living document. Update it when something changes. The version that’s accurate today and stale in three months is worse than no README at all.