Many users run multi-entity or multi-department setups where the ideal context model is two layers — a company-wide Session Context (identity, entity structure, leadership, baseline industry framework) plus department-specific Topic Context (jargon, process, regulatory frame for that department). My setup is a Part 135 air carrier and Part 145 repair station with HR, Marketing, Sales, Operations, MX, Finance, and Compliance as topics — each with its own substantive jargon and framework above and beyond the general company context.

Current behavior: When a session is in a topic, the Topic Context completely replaces the Session Context. This forces full duplication of the company-wide baseline into every topic.

Problems with the current behavior:

• Doesn’t scale — baseline changes require editing every topic

• Burns through the 20K topicContext cap when departments need rich domain context

• Loses the clean general-to-specific separation that makes large context profiles maintainable

Proposed behavior: Stack the contexts. Apply the default Session Context first, then layer the topic’s Topic Context on top, with Topic Context taking precedence in any conflicts. This mirrors well-established inheritance patterns (CSS cascading, prototypal inheritance, scope chains).