• Sources: primary
  • Summary: PrivacyLib runs inside client libraries and at RPC boundaries for hundreds of Meta data and processing systems, mapping each access to read, write, RPC and similar operations so enforcing and observing modules such as Policy Zones can plug in without new integration work. Requirements are compiled at build time and answered mostly from in-process caches, and enforcement ships with each owning service rather than through a fleet-wide config push. An Agent Observability module links internal AI agent tool calls to their session context so disallowed operations can be blocked.
  • Why it matters: It shows a concrete pattern for putting data access controls, including for agents, at the client boundary without per-system reimplementation.