This project is not covered by Drupal’s security advisory policy.
AI Decision Log stores editorial and technical decisions as persistent, queryable content entities — an ADR-style (Architecture Decision Record) trail for both human and AI-assisted changes. It answers not just what changed but why, and keeps that reasoning available for review, onboarding and audit.
The problem it solves
Decisions made during content and configuration work — especially AI-assisted ones — usually vanish into commit messages, chat logs or nobody's memory. AI Decision Log captures them as first-class, permissioned records you can query and report on.
What each decision records
- Title, summary and context — the situation and why a decision was needed.
- The decision and the alternatives that were considered.
- Related entities, configuration or modules.
- Source — whether the decision was human or AI-assisted, and by whom.
Features
- Content-entity trail — decisions are permissioned, queryable entities with an admin report at
/admin/reports/ai-decisions. - One-call writer service —
ai_decision_log.writerlets any module record a decision in a single call. - AI Policy Gateway integration — mirrors every AI policy decision into the log automatically, storing only sanitized, prompt-free data (a hash of the input, never the raw prompt).
Requirements
- Drupal 10.3+ or 11
Standalone — no other AI module is required.
Installation
composer require drupal/ai_decision_logEnable the module and review decisions under Reports.
Project information
- Created by cesarmsfelipe on , updated
This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.
