Authors: Mallesh Miryala
Abstract: Large organizations run on operational data that changes every hour: people join and leave, locations are renamed, incidents unfold, and responsibilities shift. In practice, the hardest part is not storing records; it is keeping the records consistent enough that policy decisions and workflows remain trustworthy. This paper proposes a practical design pattern called the policy- aware operational graph. The pattern treats people, organizational units, locations, requests, and tasks as a connected graph with explicit ownership and audit history. It combines three ideas that are often built separately: identity lifecycle management, rule-driven routing, and cross-system transaction safety. The design is informed by field experience maintaining a continuity platform at a large public university and building high-volume fulfillment workflows at a national telecom. The paper contributes a reference architecture, a repeatable identity hygiene loop for key contacts, and an efficient duplicate-detection method that routes only uncertain cases to human review. A small reference implementation is provided to demonstrate how blocking keys and union-find can scale to large datasets without excessive memory or quadratic comparisons.
