Outcome Notes / Description
Should I incorporate Drupal's native:
"Revision information (No revision)"
"Revision log message"
"Briefly describe the changes you have made."
**Absolutely not.** You should brutally purge the native Drupal "Revision information", "Revision log message", and "Briefly describe the changes you have made" fields from your `GTD Item` edit forms.
Leaving these fields visible would be a critical violation of your "Intelligent Dumbing Down" architecture and introduces unnecessary cognitive friction. Here is how the enterprise and productivity frameworks in your library decisively validate stripping this feature away from your Tier 3 GTD Exocortex:
### 1. It is Pure Administrative Waste (ITIL 4 & GTD)
Applying the ITIL 4 guiding principle to **"Keep it simple and practical,"** you must eliminate any process, service, or action that fails to provide value or produce a useful outcome [1, 2]. ITIL strictly advises that "record-keeping should be simplified and automated where possible to maximize value and reduce non-value-adding work" [3].
In the Getting Things Done (GTD) methodology, your system **"must save a lot more time and effort than are needed to maintain it"** [4]. Forcing yourself to type a manual justification (e.g., *"Updated context from @HomeOffice to @Calls"*) for a transient daily task is the ultimate example of non-value-adding work. If your system is too bureaucratic, "your mind will go numb to the whole business" and you will instinctively resist using it [5].
### 2. Disproportionate to Risk (GAMP 5)
GAMP 5 emphasizes using "critical thinking" to scale life cycle and control activities based on the actual risk, complexity, and novelty of a system [6]. It explicitly warns that **"too much paperwork can confuse and make it harder to maintain and inspect computerized systems"** and that compliance is not "directly proportionate to the amount of paperwork produced" [7].
Because your `gtd_item` bundle represents low-risk, personal momentum drivers (Tier 3) rather than a high-risk enterprise manufacturing system, imposing heavy change-control documentation on your daily Next Actions is entirely disproportionate. "Significant efficiency improvements can be achieved by focusing on what is essential in individual situations and avoiding unnecessary work" [8].
### 3. Unnecessary for a Single-Tenant Perimeter (ISO 27001)
While ISO 27001 dictates that audit trails are essential for investigating what has gone wrong in a corporate environment [9], it also recognizes that "extensive and detailed logs... may provide more (or less) information than is required" [9]. Because your GTD Exocortex is a highly secure, single-tenant environment, you do not need version-controlled compliance auditing to track your own task updates. You are the sole actor; you do not need to justify changing a task's status to an external auditor.
### The Execution Strategy
To align perfectly with Praxis deployment principles:
1. **Disable Revisions by Default:** In the Drupal `gtd_item` content type settings, uncheck "Create new revision" so the database does not bloat with thousands of transient task states.
2. **Hide the UI Cryptographically:** Use your existing `hook_form_alter` to completely strip the revision UI element from the form array:
`$form['revision_information']['#access'] = FALSE;`
This keeps your interface completely silent, streamlined, and relentlessly focused on execution.
