jake/Lumotia
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: rebrand from Kon/Corbie to Magnotia

Browse Source 
Replace all instances of the legacy product names "Kon" and "Corbie" with
"Magnotia" across user-facing copy, code identifiers, package names, bundle
ids, file paths, and documentation. Preserves the unrelated "konsole" (KDE
terminal) reference and the parent CORBEL company name.

- Renames 10 Rust crates (kon-* → magnotia-*) and the tauri binary
- Updates package.json, tauri.conf.json (productName + identifier)
- Renames CSS classes (kon-rh-* → magnotia-rh-*) and animations
- Renames brand and roadmap docs
- Regenerates Cargo.lock and package-lock.json

Verified: svelte-check passes; pure-rust crates compile under new names.
This commit is contained in:
Claude
2026-04-30 13:06:55 +00:00
parent 749403697a
commit 89c63891fa
186 changed files with 1297 additions and 1297 deletions
Download Patch File Download Diff File Expand all files Collapse all files

72
docs/gpu-tuning/plan.md
View File

@@ -1,4 +1,4 @@
# Kon — GPU Tuning & Community Config Plan
# Magnotia — GPU Tuning & Community Config Plan
*Implementation spec for the first three phases of the GPU kernel tuning roadmap. The full five-phase roadmap is pinned in memory; this document scopes the MVP subset that ships real value without pulling in `ggml`-dedup or agentic-search prerequisites.*
@@ -7,8 +7,8 @@
**IN** (this document):
- Phase 1 — Advanced GPU tuning settings panel (exposing GGML env vars)
- Phase 2 — `kon-bench` local autotuning CLI
- Phase 3-lite — `kon-configs` community repo with manual-PR workflow (no CI replay)
- Phase 2 — `magnotia-bench` local autotuning CLI
- Phase 3-lite — `magnotia-configs` community repo with manual-PR workflow (no CI replay)
**OUT** (pinned to memory for later):
@@ -36,13 +36,13 @@ This subset captures roughly 85% of the perceived value for ~20% of the total ef
| Disable integer dot product | `GGML_VK_DISABLE_INTEGER_DOT_PRODUCT` | off | "Random NaN" on RDNA2 with certain drivers |
| Enable Vulkan validation | `GGML_VK_VALIDATE` | off | Diagnostic only; impacts performance |
Metal / CUDA counterparts slot in when those backends grow in Kon. Today Kon is Vulkan-only.
Metal / CUDA counterparts slot in when those backends grow in Magnotia. Today Magnotia is Vulkan-only.
### Design
- New `SettingsState.gpuTuning: { disableCoopmat: boolean, forceFp32: boolean, disableF16: boolean, disableIntegerDotProduct: boolean, enableValidation: boolean }` in [src/lib/types/app.ts](../../src/lib/types/app.ts)
- All defaults `false` in [src/lib/stores/page.svelte.ts](../../src/lib/stores/page.svelte.ts)
- Persistence uses the existing `save_preferences` → SQLite `kon_preferences` path
- Persistence uses the existing `save_preferences` → SQLite `magnotia_preferences` path
- Backend reads preferences at the **very top** of `run()` in [src-tauri/src/lib.rs](../../src-tauri/src/lib.rs) — before `tauri::Builder::default()` spawns threads — and writes via `unsafe { std::env::set_var(...) }`. Matches the existing `ensure_x11_on_wayland` pattern
- Settings UI shows a sticky "Restart required for changes to take effect" banner when any toggle has drifted from its launch-time value
- A "Reset to defaults" button zeroes all toggles
@@ -55,18 +55,18 @@ Metal / CUDA counterparts slot in when those backends grow in Kon. Today Kon is
---
## Phase 2 — `kon-bench` local autotuning CLI
## Phase 2 — `magnotia-bench` local autotuning CLI
**Effort**: 3–5 days.
**What ships**: New workspace binary `crates/bench/` producing a `kon-bench` executable. User runs it once post-install; output lands at `~/.kon/gpu-profile.toml` with the best-scoring config for their hardware. Settings page gets an "Apply auto-tuned profile" button that consumes the TOML and updates the Phase 1 toggles.
**What ships**: New workspace binary `crates/bench/` producing a `magnotia-bench` executable. User runs it once post-install; output lands at `~/.magnotia/gpu-profile.toml` with the best-scoring config for their hardware. Settings page gets an "Apply auto-tuned profile" button that consumes the TOML and updates the Phase 1 toggles.
### CLI surface
```
kon-bench --quick # bundled 20s sample + reference transcript
kon-bench --model <path> --audio <wav> --transcript <txt>
kon-bench --compare <profile.toml> # benchmark a specific profile vs default
magnotia-bench --quick # bundled 20s sample + reference transcript
magnotia-bench --model <path> --audio <wav> --transcript <txt>
magnotia-bench --compare <profile.toml> # benchmark a specific profile vs default
```
### Execution model
@@ -102,7 +102,7 @@ A 20-second public-domain speech clip with a known-good reference transcript, co
```toml
[benchmarked_at]
timestamp = "2026-04-21T14:32:00Z"
kon_version = "0.1.0"
magnotia_version = "0.1.0"
model = "whisper-distil-large-v3"
[hardware]
@@ -137,37 +137,37 @@ crates/bench/
│ └── librivox-sample.txt
└── src/
├── main.rs # CLI + parent process
├── runner.rs # subprocess harness (child entry gate: KON_BENCH_RUN=1)
├── runner.rs # subprocess harness (child entry gate: MAGNOTIA_BENCH_RUN=1)
├── matrix.rs # grid-search + top-k logic
├── metrics.rs # RTF + WER + optional VRAM sampling
└── profile.rs # TOML serialise
```
Depends on `kon-transcription` + `kon-llm` + `kon-audio` as path deps so it reuses the existing model-loading code.
Depends on `magnotia-transcription` + `magnotia-llm` + `magnotia-audio` as path deps so it reuses the existing model-loading code.
### Acceptance
- `kon-bench --quick` runs unattended to completion on a fresh install
- `magnotia-bench --quick` runs unattended to completion on a fresh install
- Produces a valid `gpu-profile.toml`
- "Apply auto-tuned" button in Settings consumes the TOML and updates Phase 1 toggles (restart banner fires as expected)
- Re-running with `--compare <profile>` produces reproducible-enough numbers (RTF within 5% run-to-run)
---
## Phase 3-lite — `kon-configs` community repo
## Phase 3-lite — `magnotia-configs` community repo
**Effort**: 3 days (1 for repo + seeds, 2 for Kon-side fetch + apply UI).
**Effort**: 3 days (1 for repo + seeds, 2 for Magnotia-side fetch + apply UI).
**What ships**: A separate public GitHub repo `kon-configs` (not part of the kon main repo) seeded with 2–3 curated configs. Kon's Settings page gets a "Browse community configs" button that fetches matching configs for the user's detected hardware.
**What ships**: A separate public GitHub repo `magnotia-configs` (not part of the magnotia main repo) seeded with 2–3 curated configs. Magnotia's Settings page gets a "Browse community configs" button that fetches matching configs for the user's detected hardware.
### Repo structure
```
kon-configs/
magnotia-configs/
├── README.md # pitch + how to benefit
├── CONTRIBUTING.md # required fields, benchmark protocol, fork/PR flow
├── SCHEMA.md # TOML schema documentation
├── index.json # manifest for Kon to discover configs
├── index.json # manifest for Magnotia to discover configs
└── configs/
├── nvidia/
│ ├── rtx-3060-12gb-linux.toml
@@ -190,15 +190,15 @@ notes = "Tested with 1-hour continuous dictation session, no crashes."
### Contribution flow (manual, honour-system MVP)
1. User runs `kon-bench` on their hardware.
2. User runs `kon-bench --compare` against baseline to confirm improvement isn't noise.
3. User forks `kon-configs`, commits their TOML under `configs/<vendor>/`, opens PR.
1. User runs `magnotia-bench` on their hardware.
2. User runs `magnotia-bench --compare` against baseline to confirm improvement isn't noise.
3. User forks `magnotia-configs`, commits their TOML under `configs/<vendor>/`, opens PR.
4. Maintainer reviews format + plausibility, merges.
5. No CI replay — revisit if spam becomes a problem.
### Kon integration
### Magnotia integration
- New Tauri command `fetch_community_configs(gpu_fingerprint)` — HTTPS GET `https://raw.githubusercontent.com/<org>/kon-configs/main/index.json` for the manifest, then fetches matching TOMLs
- New Tauri command `fetch_community_configs(gpu_fingerprint)` — HTTPS GET `https://raw.githubusercontent.com/<org>/magnotia-configs/main/index.json` for the manifest, then fetches matching TOMLs
- Fingerprint match: GPU name substring + VRAM tier (e.g., `"RTX 3060"` + `"12gb"`)
- Settings "Browse community configs" button lists matches with submitter, claimed RTF improvement, and a preview of the toggle deltas
- Applying a config updates Phase 1 toggles AND stores provenance (source = `"community"`, submitter, fetch date)
@@ -206,13 +206,13 @@ notes = "Tested with 1-hour continuous dictation session, no crashes."
### What we explicitly skip at MVP
- **No CI replay**. Maintainer eyeballs + honour system. Revisit past ~50 configs or on abuse.
- **No automated upload from `kon-bench`**. User always commits + PRs manually. Zero privacy concerns, zero spam surface.
- **No automated upload from `magnotia-bench`**. User always commits + PRs manually. Zero privacy concerns, zero spam surface.
- **No sophisticated fingerprint normalisation**. Substring matching is sufficient.
### Acceptance
- Repo exists with README + CONTRIBUTING + 2–3 seed configs
- Kon Settings fetches + lists + applies a community config end-to-end
- Magnotia Settings fetches + lists + applies a community config end-to-end
- "Revert to default" path works (Phase 1's reset)
---
@@ -223,7 +223,7 @@ This is the UX the three phases together enable. All three are prerequisites; Ph
### First-launch onboarding nudge
After the existing first-run model download, Kon surfaces a non-modal card:
After the existing first-run model download, Magnotia surfaces a non-modal card:
```
🎛 GPU Optimisation
@@ -241,7 +241,7 @@ Two steps, in this order:
**Step 1 — Community config check (instant, ~2 s)**
Kon fingerprints the GPU and queries the `kon-configs` manifest for matches. If a match exists, a preview card appears:
Magnotia fingerprints the GPU and queries the `magnotia-configs` manifest for matches. If a match exists, a preview card appears:
```
┌─────────────────────────────────────────────┐
@@ -271,13 +271,13 @@ If no community match, or the user prefers their own measurement:
│ │
│ We can benchmark your machine to find the │
│ best settings. Takes ~8 minutes; runs in │
│ the background while you keep using Kon. │
│ the background while you keep using Magnotia. │
│ │
│ [ Benchmark my GPU ] [ Skip ] │
└─────────────────────────────────────────────┘
```
Kicks off `kon-bench` as a background process. Kon keeps working during the run.
Kicks off `magnotia-bench` as a background process. Magnotia keeps working during the run.
### Progress UI during benchmark
@@ -307,7 +307,7 @@ Plus a "Revert to previous config" button, active for 7 days after any change, i
### Optional — sharing back to the community
After a successful local benchmark that shows meaningful gains, Kon prompts:
After a successful local benchmark that shows meaningful gains, Magnotia prompts:
```
┌─────────────────────────────────────────────┐
@@ -325,7 +325,7 @@ After a successful local benchmark that shows meaningful gains, Kon prompts:
└─────────────────────────────────────────────┘
```
"Create PR" opens the user's browser to `github.com/…/kon-configs/new/main` with the TOML prefilled in the PR body. User finishes the submission on GitHub (still honour-system; no automated uploads, no telemetry).
"Create PR" opens the user's browser to `github.com/…/magnotia-configs/new/main` with the TOML prefilled in the PR body. User finishes the submission on GitHub (still honour-system; no automated uploads, no telemetry).
### Non-GPU / integrated-only fallback
@@ -333,7 +333,7 @@ If `sysinfo` reports no dedicated GPU or Vulkan isn't available, the card replac
```
🎛 GPU Optimisation
No dedicated GPU detected — Kon is using CPU inference.
No dedicated GPU detected — Magnotia is using CPU inference.
GPU tuning doesn't apply to this setup.
```
@@ -345,7 +345,7 @@ For users whose GPU has a community-contributed config, the experience is **lite
For users without a community match, the experience is **two clicks** (trigger bench → apply results on completion), with a passive ~8-minute background wait in between.
For users on integrated graphics / no GPU, the experience is **zero clicks** — Kon tells them GPU tuning doesn't apply and moves on.
For users on integrated graphics / no GPU, the experience is **zero clicks** — Magnotia tells them GPU tuning doesn't apply and moves on.
---
@@ -353,7 +353,7 @@ For users on integrated graphics / no GPU, the experience is **zero clicks** —
Strict linear: Phase 1 → Phase 2 → Phase 3-lite. Each phase merges to `main` and gets dogfooded before the next starts.
- Phase 1 is a prereq for Phase 2 — `kon-bench`'s output needs the Phase 1 settings schema to be its consumption target.
- Phase 1 is a prereq for Phase 2 — `magnotia-bench`'s output needs the Phase 1 settings schema to be its consumption target.
- Phase 2 is a prereq for Phase 3-lite — the community repo's config TOML schema **is** Phase 2's output schema (with an added `[attribution]` section).
## Shelved with rationale
@@ -361,4 +361,4 @@ Strict linear: Phase 1 → Phase 2 → Phase 3-lite. Each phase merges to `main`
- **Phase 4 — custom SPIR-V shader drops.** Blocked on `ggml`-dedup workstream. Pinned in memory.
- **Phase 5 — agentic (Karpathy-style) autotune.** Phase 2's grid search produces schema-compatible results, so Phase 5 can drop in later without a schema break. Pinned.
- **Phase 3's CI replay.** Defer until spam / bad-config abuse is a real problem rather than a hypothetical one. Honour-system PR review is sufficient for the MVP community.
- **`kon-bench` automated upload.** Deliberately manual for MVP — removes all privacy / spam / rate-limiting concerns. Revisit when the community volume justifies the infrastructure.
- **`magnotia-bench` automated upload.** Deliberately manual for MVP — removes all privacy / spam / rate-limiting concerns. Revisit when the community volume justifies the infrastructure.