mirror of
https://github.com/hanzoai/minutes.git
synced 2026-10-30 18:27:58 +00:00
zeekayandHanzo Dev
ecd717c6fb
A fork of meetily (MIT, Zackriya Solutions) rebranded to Hanzo. The Python/FastAPI tier, its Docker files, its whisper-server scripts and the whisper.cpp submodule are deleted rather than rebranded. Upstream's own CLAUDE.md says that tier is archived and unsupported and tells you not to add endpoints to it; the shipping product is one Tauri binary that transcribes in-process with whisper-rs and Parakeet. Rebranding a corpse would have doubled the surface and taught the next reader that a dead service is a live one. Going with it: the vestigial localhost:5167 gate the sidebar checked before reading its own database. .github/workflows goes too. This repo lives on git.hanzo.ai, which reads .hanzo/workflows, and we do not use GitHub-hosted runners — six workflow files that cannot run read like CI that passes. Nothing replaces them yet, because a pipeline that has never run is worse than an honest absence. Summaries are written by api.hanzo.ai, our own stack, and it is the default. The other providers still compile and should go in a follow-up. The upstream MIT notice stays and the Hanzo copyright joins it. About and the README say plainly what this is a fork of. Left alone deliberately, and each is a decision someone must still make: the minisign updater key is upstream's and we cannot re-sign, so the updater points at a release path that does not exist yet; the ffmpeg binaries still come from upstream's GitHub; the Parakeet models still come from upstream's host. Co-authored-by: Hanzo Dev <[email protected]>
Meeting Summary Templates
This directory contains template definitions for meeting summary generation.
Available Templates
1. daily_standup.json
Time-boxed daily updates template designed for engineering/product teams.
Sections:
- Date
- Attendees
- Yesterday (completed work)
- Today (planned work)
- Blockers
- Notes
2. standard_meeting.json
General-purpose meeting notes template focusing on key outcomes and actions.
Sections:
- Summary
- Key Decisions
- Action Items
- Discussion Highlights
Template Structure
Each template JSON file follows this schema:
{
"name": "Template Name",
"description": "Brief description of the template's purpose",
"sections": [
{
"title": "Section Title",
"instruction": "Instructions for the LLM on what to extract/include",
"format": "paragraph|list|string",
"item_format": "Optional: Markdown table format for list items"
}
]
}
Custom Templates
Users can add custom templates to the application data directory:
- macOS:
~/Library/Application Support/Minutes/templates/ - Windows:
%APPDATA%\Minutes\templates\ - Linux:
~/.config/Minutes/templates/
Custom templates override built-in templates with the same filename.
Template Fields
Root Level
name(required): Display name for the templatedescription(required): Brief explanation of the template's use casesections(required): Array of section definitions
Section Object
title(required): Section heading textinstruction(required): LLM guidance for this sectionformat(required): One of"paragraph","list", or"string"item_format(optional): Markdown formatting hint for list items (e.g., table structure)example_item_format(optional): Alternative formatting hint
Usage in Code
Templates are loaded using the templates module:
use crate::summary::templates;
// Get a specific template
let template = templates::get_template("daily_standup")?;
// List available templates
let available = templates::list_templates();
// Validate custom template JSON
let custom_json = std::fs::read_to_string("custom.json")?;
let validated = templates::validate_template(&custom_json)?;