Typed Relationships and Richer Context

Relationship modeling got more explicit. Templates can now carry schema-bound relationship types, and the agent sees those structures in a cleaner context view instead of a partial or repetitive graph.

Relationship Types on Templates

You can now define relationship types against templates, not just ad-hoc instances. That gives the platform a stable schema for how model types connect, so new instances can inherit a clearer structure instead of relying on one-off edges.

Cleaner Ontology Output

Ontology context is now rendered as grouped edge lists instead of repeating the same schema detail in multiple places. System-only edges stay out of the way, template schema edges stop cluttering the active artifact list, and explicit collaborator links no longer disappear just because they sit outside a narrow visibility filter.

Peer and Partner Neighborhoods

When the agent reasons about a collaborator or partner, it now sees a two-hop neighborhood instead of a flat dump. Related instances are grouped under their template, nearby context stays connected, and the response can say when there is more beyond the visible neighborhood instead of pretending the graph ends there.

Fresh Graphs After Type Changes

Defining or updating a relationship type now refreshes the affected graph views, so context tools and relationship-aware prompts pick up the new structure right away. You do not have to wait for a stale graph cache to age out before the model sees the corrected shape.

Try It

Ask the agent to explain how two model types relate, or to summarize a collaborator's working context. The answer should now reflect the typed graph instead of a thinner, flatter snapshot.