vh
ad2df89c0c
The incumbent Qwen3-Reranker-0.6B was measured actively harming 80/90 fleet queries on main+knowledge_base (and inverting the bare-name region behind Worldtree #389) — no-reranker beat it 89/90 vs 56/90. Brokkr's R43 bake-off selected BAAI/bge-reranker-v2-m3 (A3): 90/90 top-10, mean rank 0.19, multilingual (XLM-R), ~1.2 GB lighter than the incumbent. Control arm (A2 = same Qwen weights, seq-cls head) scored identical to the incumbent, proving the fault is a training prior, not the serving head — which cancelled the expensive Qwen3-4B arm before it cost a GPU seat. Cutover boundary 2026-08-06T17:37:48Z. The qwen3-reranker alias and the :8002 backend are retained for one-edit rollback. Adds the process audit trail at docs/pfi/reranker-selection-ledger.md.
docs/
Navigation map for the documentation tree. New session? Read
orientation.md first — it's the narrative overview
of the fleet, backup architecture, governing principles, and gotchas,
and it points at everything else.
Tree
docs/
├── orientation.md # start here — fleet overview + where-to-look guide
├── runbooks/ # ops runbooks (recovery, deployment phases)
│ ├── disaster-recovery.md
│ ├── nh3-prune-ritual.md
│ └── pbs-deployment.md
└── pfi/ # PFI-specific reference (services, models, VMs)
├── docker-stack.md
├── model-list.md
├── proxmox-vms.md
├── recommended-model-settings.md
├── vm-102-matrix-appservice.md
└── vm-102-matrix-synapse.md
What goes where
runbooks/— step-by-step ops procedures. Anything you'd reach for during an incident or while standing up new infrastructure. Examples: disaster recovery (blast-radius tiers + restoration steps), PBS deployment (9-phase rollout). New runbook → new file here.pfi/— PFI-specific reference material that's too narrow for the top-level CLAUDE.md but doesn't change incident response. AI model inventory, recommended inference settings, Matrix bridge config, Proxmox VM map. New stable reference → new file here.- Top-level (
docs/orientation.md,docs/README.md) — narrative guides about the workspace itself, not about specific infra.
Cross-references
- Fleet topology + servers table: top-level
CLAUDE.md. - Open work + recent milestones: top-level
STATUS.md. - Durable cross-session facts:
~/.claude/projects/-home-lkraven-development-eshpfi-management/memory/.
Conventions
- Markdown, GitHub-flavored. CommonMark renders fine in most viewers.
- File names are lowercase-kebab-case, descriptive. No dates in filenames — git history covers that.
- One topic per file. If a file grows past ~500 lines, look for a natural split before adding more.
- No checked-in binaries or checksums. Build/release artifacts belong
in a build pipeline or
tools/, notdocs/.