Get the derivation graph around an attribute.
Return the part of the derivation graph reachable from the given attribute: the attributes it can be derived from, the attributes that can be derived from it, the rules connecting them, and the routes out of the attribute with their total cost and fidelity. Only active rules the caller may use are followed, and an attribute the caller cannot view is left out along with the rules touching it.
Authentication is optional. Anonymous callers see rules shared with every company and attributes shared with every company. A token that is present but invalid is rejected rather than falling back to the anonymous view.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Either an attribute name or an attribute id Unique identifier
Query Parameters
Which way to walk from the attribute. descendants follows rules from source to target and reaches what can
be derived from the attribute; ancestors follows them from target to source and reaches what the attribute
can be derived from. The default walks both ways.
descendants, ancestors, both Response
OK
The part of the derivation graph reachable from one attribute through active rules the caller may use, over
attributes the caller can view. nodes and edges are flat lists rather than a nested tree because the graph can
contain cycles (a rule from birthdate to age and one from age to birthdate are both legitimate). A program walks
the adjacency through edges; a person reads paths.
The walk goes as far as query resolution can chain rules, which is one rule today, so every path listed is one a query can use. At most 50 paths are returned, descendants before ancestors.
An short identifier for the attribute to be used when it is referenced in validations.
Attribute names must consist of only alphanumeric characters or underscores and be < 255 characters long.
The direction the walk followed, as requested.
descendants, ancestors, both Every rule connecting two of the nodes, in rule id order.
The requested attribute first, then the rest by distance and then by id.

