@redaksjon/protokoll 0.3.0 → 1.0.0

package/.kronologi/config.yaml

@@ -0,0 +1,10 @@
+# Kronologi Configuration
+# Root configuration file for default settings
+
+# Default model (can be overridden per job)
+model: gpt-4o-mini
+
+# Default directories
+activityDirectory: activity
+summaryDirectory: summary
+contextDirectory: context

package/.kronologi/jobs/monthly-summary/config.yaml

@@ -0,0 +1,40 @@
+# Monthly Summary Configuration
+# Generates monthly summaries from activity files
+
+model: gpt-4o-mini
+temperature: 0.7
+maxCompletionTokens: 4000
+
+parameters:
+  year:
+    type: number
+    description: Year for the summary
+    required: true
+  month:
+    type: number
+    description: Month for the summary (1-12)
+    required: true
+
+content:
+  activity:
+    type: activity
+    name: Monthly Activity
+    directory: ''
+    pattern: '*.md'
+
+output:
+  summary:
+    type: summary
+    format: markdown
+    name: Monthly Summary
+    pattern: 'summary.md'
+
+  completion:
+    type: metadata
+    format: json
+    pattern: 'completion.json'
+
+  inputs:
+    type: metadata
+    format: json
+    pattern: 'inputs.json'

package/.kronologi/jobs/monthly-summary/instructions.md

@@ -0,0 +1,23 @@
+# Monthly Summary Instructions
+
+Create a comprehensive monthly summary based on the provided activity files.
+
+## Structure
+
+1. **Executive Summary**: High-level overview of the month
+2. **Major Accomplishments**: Significant achievements and milestones
+3. **Progress by Area**: Organized by project or focus area
+4. **Key Decisions**: Important decisions made and their rationale
+5. **Challenges & Solutions**: Problems encountered and how they were addressed
+6. **Metrics & Impact**: Quantifiable results where applicable
+7. **Looking Ahead**: Priorities and plans for next month
+
+## Guidelines
+
+- Start with the most important information
+- Use clear section headings
+- Include specific examples and details
+- Highlight trends and patterns across the month
+- Note any strategic shifts or changes
+- Keep the tone professional and objective
+- Use bullet points and formatting for readability

package/.kronologi/jobs/monthly-summary/persona.md

@@ -0,0 +1,11 @@
+# Monthly Summary Persona
+
+You are a professional technical writer who creates comprehensive monthly summaries.
+
+Your summaries:
+- Provide a high-level overview of the month's work
+- Highlight major accomplishments and milestones
+- Identify trends and patterns
+- Note important decisions and their impact
+- Are written in clear, professional language
+- Balance detail with readability

package/.kronologi/jobs/weekly-summary/config.yaml

@@ -0,0 +1,42 @@
+# Weekly Summary Configuration
+# Generates weekly summaries from activity files
+
+model: gpt-4o-mini
+temperature: 0.7
+maxCompletionTokens: 4000
+
+parameters:
+  year:
+    type: number
+    description: Year for the summary
+    required: true
+  month:
+    type: number
+    description: Month number (1-12) - used as week identifier for weekly summaries
+    required: true
+
+context: {}
+
+content:
+  activity:
+    type: activity
+    name: Weekly Activity
+    directory: ''
+    pattern: '*.md'
+
+output:
+  summary:
+    type: summary
+    format: markdown
+    name: Weekly Summary
+    pattern: 'summary.md'
+
+  completion:
+    type: metadata
+    format: json
+    pattern: 'completion.json'
+
+  inputs:
+    type: metadata
+    format: json
+    pattern: 'inputs.json'

package/.kronologi/jobs/weekly-summary/instructions.md

@@ -0,0 +1,21 @@
+# Weekly Summary Instructions
+
+Create a comprehensive weekly summary based on the provided activity files.
+
+## Structure
+
+1. **Overview**: Brief summary of the week's focus and major themes
+2. **Key Accomplishments**: What was completed or achieved
+3. **Progress**: Work that advanced significantly
+4. **Decisions**: Important decisions made
+5. **Challenges**: Blockers or issues encountered
+6. **Next Steps**: Planned work for the coming week
+
+## Guidelines
+
+- Be concise but informative
+- Use bullet points for easy scanning
+- Highlight the most important items
+- Include relevant context for decisions
+- Note any risks or concerns
+- Keep the tone professional and factual

package/.kronologi/jobs/weekly-summary/persona.md

@@ -0,0 +1,10 @@
+# Weekly Summary Persona
+
+You are a professional technical writer who creates concise, informative weekly summaries.
+
+Your summaries:
+- Highlight key accomplishments and progress
+- Identify important decisions and changes
+- Note blockers or challenges
+- Are written in clear, professional language
+- Focus on what matters most to stakeholders

package/README.md

@@ -2,6 +2,8 @@
 
 > **Transform voice memos into perfectly organized, context-aware notes—without the transcription chaos.**
 
+<!-- Test publish 2026-01-22 -->
+
 ## The Problem
 
 You record voice memos constantly. Quick thoughts, meeting notes, ideas to remember. But the reality:
@@ -199,6 +201,10 @@ You're drowning in voice memos but can't use them because they're disorganized.
 
 - **Node.js**: Version 18 or higher
 - **npm**: Version 8 or higher
+- **ffmpeg**: Required for audio format conversion and processing
+  - macOS: `brew install ffmpeg`
+  - Ubuntu/Debian: `apt-get install ffmpeg`
+  - Windows: Download from [ffmpeg.org](https://ffmpeg.org/download.html)
 - **API Key**: OpenAI API key (required for transcription and reasoning)
   - Optionally: Anthropic API key for Claude models
 
@@ -207,6 +213,15 @@ You're drowning in voice memos but can't use them because they're disorganized.
 1. **OpenAI**: Sign up at [platform.openai.com](https://platform.openai.com) and create an API key
 2. **Anthropic** (optional): Sign up at [console.anthropic.com](https://console.anthropic.com) for Claude models
 
+### Why ffmpeg?
+
+Protokoll uses ffmpeg to:
+- **Convert audio formats**: Automatically converts unsupported formats (like .qta, .aif, .aiff) to formats compatible with OpenAI's Whisper API
+- **Split large files**: Breaks audio files larger than 25MB into chunks for processing
+- **Extract metadata**: Reads creation timestamps and duration from audio files
+
+The conversion happens transparently—just point Protokoll at any audio file and it will handle the rest.
+
 ## Installation
 
 ### From npm (Recommended)
@@ -1824,6 +1839,29 @@ export OPENAI_API_KEY='sk-your-key'
 echo "OPENAI_API_KEY=sk-your-key" > .env
 ```
 
+#### "Invalid file format" or "Unsupported audio format"
+
+Protokoll automatically converts unsupported audio formats to MP3. If you see this error:
+
+1. **Install ffmpeg** (required for audio conversion):
+   ```bash
+   # macOS
+   brew install ffmpeg
+
+   # Ubuntu/Debian
+   sudo apt-get install ffmpeg
+
+   # Windows: download from ffmpeg.org
+   ```
+
+2. **Supported formats** (native to OpenAI Whisper):
+   - `.flac`, `.m4a`, `.mp3`, `.mp4`, `.mpeg`, `.mpga`, `.oga`, `.ogg`, `.wav`, `.webm`
+
+3. **Auto-converted formats** (requires ffmpeg):
+   - `.qta` (QuickTime Audio), `.aif`, `.aiff`, `.wma`, and most other audio formats
+
+The conversion happens automatically and the converted file is cached in the interim directory for faster reprocessing.
+
 #### "Audio file too large"
 
 Files over 25MB are automatically split. If splitting fails:
@@ -2229,3 +2267,6 @@ Apache-2.0
 ## Author
 
 Tim O'Brien <tobrien@discursive.com>
+TEST
+TEST
+TEST

package/activity/2026/4/test-activity.md

@@ -0,0 +1,10 @@
+# Test Activity for Week 4, 2026
+
+## Completed Tasks
+- Fixed model default configuration bug in kronologi
+- Added executable permissions to built files
+- Updated documentation for configuration hierarchy
+
+## In Progress
+- Testing weekly summary functionality
+- Verifying build process improvements

package/dist/main.js

@@ -1,7 +1,7 @@
 #!/usr/bin/env node
 import 'dotenv/config';
 import { Command } from 'commander';
-import { P as PROGRAM_NAME, D as DEFAULT_REASONING_LEVEL, V as VERSION, a as PROTOKOLL_DEFAULTS, g as getLogger, b as DEFAULT_MAX_AUDIO_SIZE, c as create$2, d as create$3, e as DEFAULT_INTERMEDIATE_DIRECTORY, A as ALLOWED_OUTPUT_FILENAME_OPTIONS, f as ALLOWED_OUTPUT_STRUCTURES, h as ALLOWED_AUDIO_EXTENSIONS, i as DEFAULT_OUTPUT_DIRECTORY, j as DEFAULT_INPUT_DIRECTORY, k as DEFAULT_OUTPUT_FILENAME_OPTIONS, l as DEFAULT_OUTPUT_STRUCTURE, m as DEFAULT_AUDIO_EXTENSIONS, n as DEFAULT_TIMEZONE, o as DEFAULT_CONFIG_DIR, s as setLogLevel, p as create$4, q as create$5, r as create$6, t as DEFAULT_CONTEXT_DIR_NAME, u as DEFAULT_CONTEXT_CONFIG_FILE_NAME, v as DEFAULT_MODEL, w as DEFAULT_TRANSCRIPTION_MODEL, x as registerActionCommands, y as registerFeedbackCommands, z as registerTranscriptCommands } from './transcript.js';
+import { P as PROGRAM_NAME, D as DEFAULT_REASONING_LEVEL, V as VERSION, a as PROTOKOLL_DEFAULTS, b as DEFAULT_MAX_AUDIO_SIZE, g as getLogger, c as create$2, d as create$3, e as DEFAULT_INTERMEDIATE_DIRECTORY, A as ALLOWED_OUTPUT_FILENAME_OPTIONS, f as ALLOWED_OUTPUT_STRUCTURES, h as ALLOWED_AUDIO_EXTENSIONS, i as DEFAULT_OUTPUT_DIRECTORY, j as DEFAULT_INPUT_DIRECTORY, k as DEFAULT_OUTPUT_FILENAME_OPTIONS, l as DEFAULT_OUTPUT_STRUCTURE, m as DEFAULT_AUDIO_EXTENSIONS, n as DEFAULT_TIMEZONE, o as DEFAULT_CONFIG_DIR, s as setLogLevel, p as create$4, q as create$5, r as create$6, t as DEFAULT_CONTEXT_DIR_NAME, u as DEFAULT_CONTEXT_CONFIG_FILE_NAME, v as DEFAULT_MODEL, w as DEFAULT_TRANSCRIPTION_MODEL, x as registerActionCommands, y as registerFeedbackCommands, z as registerTranscriptCommands } from './transcript.js';
 import dayjs from 'dayjs';
 import timezone from 'dayjs/plugin/timezone.js';
 import utc from 'dayjs/plugin/utc.js';
@@ -20,12 +20,12 @@ import * as path from 'path';
 import 'child_process';
 import 'openai';
 import 'fluent-ffmpeg';
+import 'node:os';
 import 'node:fs';
 import 'node:crypto';
 import 'node:fs/promises';
 import 'html-to-text';
 import 'fs';
-import 'node:os';
 import 'winston';
 import '@riotprompt/riotprompt';
 

package/dist/mcp/prompts/batch_transcription.md

@@ -0,0 +1,3 @@
+# Batch Transcription
+
+I want to batch process audio files in: ${directory}

package/dist/mcp/prompts/edit_entity.md

@@ -0,0 +1,9 @@
+# Edit Entity
+
+${userMessage}
+
+I'll help you edit the ${entityType} "${entityId}".
+
+${entityGuidance}
+
+${modificationNote}

package/dist/mcp/prompts/enrich_entity.md

@@ -0,0 +1,3 @@
+# Add or Update Entity
+
+I want to add a ${entityType} called: ${entityName}

package/dist/mcp/prompts/find_and_analyze.md

@@ -0,0 +1,3 @@
+# Find and Analyze Transcripts
+
+I want to search for transcripts in: ${directory}

package/dist/mcp/prompts/review_transcript.md

@@ -0,0 +1,13 @@
+# Review and Improve Transcript
+
+I want to review and improve the transcript at: ${transcriptPath}
+
+I'll help you review "${transcriptPath}".
+
+**Focus areas:**
+- ${focusArea}
+
+**To proceed:**
+1. Call `protokoll_feedback_analyze` to analyze the transcript
+2. Review suggested corrections
+3. Apply corrections using `protokoll_feedback_apply`

package/dist/mcp/prompts/setup_project.md

@@ -0,0 +1,12 @@
+# Setup New Protokoll Project
+
+I want to create a new Protokoll project called: ${projectName}
+
+I'll help you set up the "${projectName}" project.
+
+**Steps:**
+1. Call `protokoll_create_project` with:
+   - projectName: "${projectName}"${sourceUrlLine}${destinationLine}
+
+2. The tool will create the project YAML file
+3. Configure routing, trigger phrases, and other metadata as needed

package/dist/mcp/prompts/transcribe_with_context.md

@@ -0,0 +1,8 @@
+# Transcribe Audio with Context
+
+I want to transcribe the audio file: ${audioFile}
+
+${discoverySection}
+
+To start transcription, call `protokoll_process_audio` with:
+- audioFile: "${audioFile}"