CitadelAcme Test Company
Acme already knows what changed this week.
A pricing decision landed Tuesday. Operations found the risk Wednesday. Leadership needs the state, not a recap.
Company
Acme Industrial Systems
Role
Chief Operating Officer
This week
Pricing change Tuesday. Fulfillment risk Wednesday. Executive review today.
What Citadel holds
The decision, the rationale, the affected accounts, the blocker, and the next action.
Session start. Loaded Acme context: pricing decision approved Tuesday, fulfillment risk attached Wednesday, executive review in 47 minutes.
What matters before the review?
The 12% price increase is approved, but two enterprise accounts still have onboarding packets at the old rate. Fulfillment is waiting on the revised bundle table before they can convert them.
Who owns the revised table?
Maya Patel in revenue operations. The table exists, but the record shows it was never attached to the fulfillment task.
Attach it and mark the blocker resolved.
Done. The fulfillment blocker is resolved, the affected accounts are linked, and the executive review now shows pricing green and delivery amber.
What Survives
continuity after the session ends
Session memory
fresh chat, old context gone
reset
Docs and email
facts exist, but the chain is broken
fragmented
Citadel record
decision → risk → owner → action, intact
preserved
The problem
Without a durable record, the pricing rationale, the owner, and the blocker live in separate chats and separate heads. Every new conversation starts with recovery work.
The difference
With Citadel, the decision, rationale, owner, risk, and next action stay attached. A new session loads the state instead of asking for a recap.