Do We want to support per Doc Auditing in Vulcan?

Currently we provide the following memcached audit events:

"id": 20488,
"name": "document read",
"description": "The named document was read",

"id": 20489,
"name": "document locked",
"description": "The named document was locked",

"id": 20490,
"name": "document modify",
"description": "The named document was modified",

"id": 20491,
"name": "document delete",
"description": "The named document was deleted"

By "named" it means the document name including in the contents of the audit event.
For clarification in Vulcan we do NOT provide the ability to specify a "name" (or wildcard / regular expression) for which documents to audit. All documents will be audited.
(The only filtering provided is on user_id).

There is some confusion as to whether we want to provide the above "per doc" auditing events in Vulcan - Perry Krug was under the impression that they were not to be provided in Vulcan.

We need to confirm with PM whether we want to keep the existing memcached per doc audit events - or whether they should be deferred?

thanks