A career assistant does not need your whole chat history every time you ask for help. It needs the facts that still matter.
CareerSwitch keeps five separate kinds of context. Strategy holds the target role and plan. Evidence holds wins, skills, and facts that can back up a resume or interview answer. Logic holds hard limits and decisions. Pipeline tracks live applications and next steps. Identity holds the user’s professional voice and the story behind a career change.
That means a resume request can load evidence and identity. A follow-up email can load pipeline and strategy. The model does not need to reread months of unrelated chat.
The separation matters when something changes. A user correction needs to beat an old model guess. A current application status needs to beat an abandoned plan. Deleting a fact needs to remove it from future context, not hide it in a database row while the assistant keeps repeating it.
Structured state lives in the database. Private files live in object storage. Resume versions, interviews, job status, and chat can share an account boundary without becoming one giant document.
Memory gets useful when someone can correct it and see the correction stick.