Memory and the Playbook
What Cruma keeps, what it asks about, and how it gets sharper.
Memory is not “everything in the workspace”. It is the small set of things worth carrying forward, and nothing enters it durably without provenance, and for learned rules, your review.
Three kinds of remembering
- Working context: what the crew assembles for the task at hand: the current guest count, the latest client email, today’s invoice status. Used, then let go. Never treated as durable truth.
- History: what happened, kept as the record: “Catering proposed an outdoor smoke station; the venue required indoor-only; Cruma requested a revision.” This lives in replay and informs future judgment.
- Standing memory: durable rules and facts worth reusing: “For Hall B events, all food preparation must stay indoors.” Created sparingly, kept with its source, and reviewable by you.
Personal versus business
Your personal preferences (“keep approval summaries under five lines”) follow your account and are visible only to you. Business memory belongs to the workspace. The wall between them is hard: a business fact can never slip into your personal memory and travel with you, and a private fact can never surface in a teammate’s answer. Summaries inherit the visibility of their sources, always.
The Playbook
The Playbook answers one question: how does Cruma run this business? It lives in your company root, next to your goals and brand, and it is made of readable skill files, not settings.
Coordinate an event change
Used by: Architect, Ops · Wakes on: guest count, venue, budget or schedule changes
Needs your ok: external messages, vendor commitments, invoice changes
Learned for your business: confirm venue access before Catering finalizes the menu; copy the account manager above $25,000
Sharpened 7 times · last changed from your edit on July 11
When you correct the crew, the correction becomes a proposal: “Cruma learned: confirm venue access before Catering finalizes menus. Keep, edit, or dismiss.” Keep it, and it becomes part of the skill, with a record of where it came from. Dismiss it, and it is gone. Nothing becomes standing procedure just because the model said it.
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.
What the Playbook is not
It is not a dump of your files, your email, or your chats. Raw threads, one-off research, and private conversations stay where they belong; the Playbook holds only the durable way of working.
Next: Teams, workspaces, and orgs, for when there is more than one of you, or more than one business.