Decision Log Recorder

WHAT IT DOES

Provides a structured decision log for recording and tracking decisions made during projects, incidents, or daily work. The script displays a comprehensive log with configurable fields including Decision Made, Context/Background, Alternatives Considered, Rationale, Impact, Decision Maker, Date Decided, and Status (Proposed/Approved/Implemented/Rejected/Deprecated). Each entry is automatically timestamped, and you can add custom tags for easy categorization. The log includes search and filter capabilities to quickly find decisions by text or tags. You can export the log as formatted text or JSON for documentation, audits, and retrospectives. Per-project or per-session logs are saved per decision identifier or project name.

WHERE IT RUNS

Works on all websites (match pattern *://*/*), making it perfect for project management platforms, incident response dashboards, product development tools, compliance portals, or any web-based workflow where decisions need to be tracked and referenced. Each project or session gets its own independent log, allowing you to manage multiple decision records simultaneously. The log state is saved per decision identifier, ensuring continuity across sessions and page reloads.

HOW TO USE

Install the script and the decision log appears in the panel. Enter a log identifier or project name to associate the log with a specific project or session. Fill in the decision details: the decision itself (required), select a status, optionally add decision maker, context, alternatives, rationale, impact, and tags. Click "Add Decision" to record it. Use the search field to filter entries by decision text, context, or tags. Use the export buttons to copy the log as text or JSON to your clipboard. Add custom statuses to match your workflow. The script saves your progress automatically as you work.

REAL MECHANISM: PROJECT-KEYED PERSISTENCE WITH MULTI-FIELD DECISION CAPTURE AND SEARCHABLE LOGGING

This script uses a project-based storage architecture where each decision log gets its own isolated state. The getDecisionLogId() function retrieves the current log identifier from GM_setValue or generates a new one. Data is stored using GM_setValue with a key format of "decision_log_" plus the log ID, ensuring data isolation between projects. The data structure includes an entries array where each entry has an id, decision, status, decisionMaker, context, alternatives, rationale, impact, tags (array), and timestamp. The statuses array stores user-customizable status names. The renderDecisionLog() function applies optional text filtering using includes() on decision, context, rationale, and tags arrays, then sorts entries chronologically (newest first) using sort((a,b) => b.timestamp - a.timestamp). Each entry is rendered as a flex row with a colored left border matching the status color (mapped via getStatusColor()), with decision text, status badge, timestamp, optional fields displayed conditionally, and tags rendered as chip-style spans. Timestamps are formatted using toLocaleString() for human-readable display. The export functions generate formatted text with a header, entry count, and each entry's fields in a structured format, or JSON with the full data structure including statuses. All operations are reactive, with automatic persistence and UI updates through saveDecisionLogData() and re-render.

THE PANEL

Drag the panel anywhere on screen by clicking and holding the header. It snaps to screen edges when released. Collapse it to a small bubble by clicking the minimize button, and expand it back by clicking the bubble. Resize the panel from any corner. Press Escape to close the configuration panel. Your position and size preferences are saved automatically per site.

PLEASE NOTE

This script requires the free BotGentz browser extension which provides the BGPanel framework and storage APIs. All data (entries, statuses, tags, and log identifiers) is stored locally in your browser using GM_setValue and never sent anywhere. No analytics, no tracking, no external calls. The script only reads the current log identifier to isolate decision records and never accesses user data, passwords, or sensitive information. Logs are saved per decision identifier, so ensure you enter a unique identifier for each project or session you track.