Memory Gateway and Model Types
A new architectural layer gives the agent richer organizational context, plus a clearer vocabulary around model types, instances, and template molecules.
The agent now reasons about your organization through a dedicated Memory Gateway, a layer that builds an ontology of artifacts, relationships, and the working set the agent has touched. The result: more coherent reasoning across long conversations and larger Dimensions.
Ontology in System Context
Every turn, the Memory Gateway enriches the agent's context with each interacted-with artifact's folder, model type, ad-hoc relationships, and a relationship ledger, capped at 10 entries per artifact for budget reasons. Instead of a flat list of artifacts, the agent sees how things connect and what type each artifact represents.
Model Types and Instances
Templates are now framed explicitly as model types: schemas that produce model instances. Any artifact (a PDF, a Canvas, a document) can be assigned to a model type after the fact, so you can introduce structure to a workspace as patterns emerge instead of having to design everything up front.
Template Molecule Awareness
When the agent creates from a template, the response now includes the template's expected relationships, the connected artifacts that form the template's molecule. The agent uses this to wire up the new instance correctly instead of leaving it isolated.
Active-Set Folder Overview
Folder overviews now auto-expand to show the artifacts the agent is actively working with. Active folders display titled entries (sorted), while non-active siblings stay compact with a "… and N more subfolders" truncation. The folder view becomes a navigation menu, not a statistic.
Relationship Type Cascade
Archiving a relationship type now soft-archives every relationship instance using it. Unarchiving restores them. No more orphaned edges or manual cleanup.