Skip to content

docs: centralize Mimir documentation #19

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jb-thery merged 1 commit into from
Jun 28, 2026
Merged

docs: centralize Mimir documentation #19

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,9 @@
- Keep public positioning focused on sovereign local RAG for confidential datasets and AI agents.
Avoid claiming universal binary-file support; unsupported proprietary formats need extraction or
dedicated parsers.
- Keep product documentation canonical in the root `README.md`. Package README files under
`packages/*/README.md` are intentionally minimal npm entrypoints and must link clearly to the
GitHub root README because npm displays package README files separately.
- Keep optional audio summaries separate from core ingestion/query behavior. The
`mimir-audio-summary` skill must prefer `kb audio` / `@jcode.labs/mimir-tts`, default to the
Transformers.js WAV path for offline/confidential rendering, use the Edge MP3 path for global
Expand Down
Loading
Loading