Implement Permanent $CreatedBy Field in Person Documents for IT Audit Compliance

During IT Audits, we are required to identify the exact Administrator (e.g., System Admin/TEST, Mail Admin/TEST, Account Operator/TEST) who initially registered a new user or re-created a user's email account.

Currently, we rely on the native $UpdatedBy field to track administrative actions. However, $UpdatedBy is a dynamic, multi-value field that appends or modifies names every time a document is edited or replicated. Because it changes continuously throughout the user lifecycle, it is unreliable for pinpointing the original creator of the Person document, creating a gap in our IT Audit trail. Introduce a permanent, immutable field named $CreatedBy (or OriginalCreator) into the Person document schema.

• Behavior: This field must be "tattooed" (computed when composed/registered) with the canonical name of the Administrator session performing the registration.

• Restriction: Once populated at document creation, the field must become strictly Read-Only and must not be altered by subsequent edits, agents, or replication processes. For existing documents where $CreatedBy is blank, a one-time agent could optionally populate the field using the oldest entry in the current $UpdatedBy array, though the primary focus is ensuring accuracy for all new and re-registered users moving forward.