Relationship discovery
Give business reasoning a meaningful path through connected objects.
Objects become useful together
Knowing that a Supplier and an Order exist is not enough to determine the effect of a supplier change. The context model needs the intervening material, product and order relationships.
- Supplier — supplies
- Material — used by
- Product — appears on
- Order — belongs to
- Customer
Where relationships can come from
- Foreign keys and shared source IDs.
- API relationships and document references.
- SOP language describing dependencies or governance.
- Business descriptions and repeated patterns that still need validation.
Relationships need meaning
“Contains”, “supplies” and “governed by” are different relationships. Direction, source and business meaning matter. The aim is to supply usable reasoning paths, rather than drawing connections for their own sake.
Current boundary
Canvas curves are illustrative, based on the selected task. Invoice checks match po_id values in supplied records. There is no general relationship discovery or graph traversal engine in this release.