# Frequently Asked Questions

# For Git-based configuration items, how does Ketryx ensure bidirectional traceability between items?

In Ketryx, relationships between configuration items are inherently bidirectional but not symmetrical. This means that traceability is defined on a specific object. For instance, a child requirement has a field indicating its parent requirements. Once established, these relationships can be utilized to query data and enforce controls. In the given example, the parent requirement "has child" refers to the child requirement, while the child requirement "has parent" refers to the parent requirement.

See [MAN-09](https://docs.ketryx.com/manuals/man-09-git-based-configuration-items#id-6.-traceability-to-other-configuration-items) for more information on traceability to other configuration items.