You said it, once
YouJuly 11
Confirm venue access before Catering finalizes the menu. And copy the account manager on anything above $25,000.
Cruma learned this. Keep, edit, or dismiss.
The correction Plain words, taken as fact.
Memory and the Playbook
Your best way of working, kept.
Corrections you make once become rules the crew runs by. The Playbook holds them as skill files you can read, each with its date, source, and teacher.
Three laws hold the whole memory system up.
Reviewed, then rememberedNothing becomes standing procedure just because the software suggested it. You keep, edit, or dismiss every proposed rule.
Personal stays personalYour preferences travel with your account, visible to no one else. Business memory belongs to the workspace, and the wall does not bend.
Not a data dumpRaw threads and one-off research stay where they live. The Playbook keeps only the durable way of working, each rule with its source.
Correct it once. It stays corrected.
How the Playbook worksA correction is not a chat message that scrolls away; it becomes a proposal you keep, edit, or dismiss, and the kept rule joins the skill with its source.
The next run knows
Cascadia · Playbook · sharpened from your correction
Coordinate an event change
Who runs it
Architect plans, Ops executes.
When it wakes
Guest counts, venues, budgets or schedules change.
Learned for Cascadia
· Confirm venue access before Catering finalizes a menu.
· Never send a revised budget before the client's timeline is updated.
· Copy the account manager on anything above $25,000.
Last sharpened from Sean's edit on July 11 · every version is kept
The skill, after Sharpened seven times, and it shows.
Ask it how it runs your business. The answer is a page you can read, not a settings tree.
Memory, in detail, in HelpIt should not leave when someone does.
Institutional knowledge usually walks out the door. Here it stays written down, sourced, and working.
Request an invite We onboard a few businesses at a time.