Files

T

vh 099e1d7418 catalog: promote chatterbox-fast to ready; vibevoice->down; resolve voxtral 8197 collision

- chatterbox-fast experimental -> ready: browser audition verified end-to-end
  (operator confirmed progressive playback "excellent" 2026-06-02).
- vibevoice ready -> down: no container running on irv-ml1 (connection refused);
  catalog status was stale.
- voxtral: NOT a stale typo — its stack genuinely claimed :8197, the port now held
  by the live chatterbox-fast. voxtral is down, so moved IT to :8201 (catalog
  endpoint + source_url, stacks/voxtral/.env.example + README, host .env) rather
  than disturb the live service. No live clash existed (voxtral down) but it was a
  latent deploy-time collision I introduced by placing chatterbox-fast on 8197.

No catalog_version bump (status changes + endpoint correction, additive). Validates
against the schema.

2026-06-02 09:10:57 -07:00

archive/asset-engine

docs: archive asset-engine design-brief.md

2026-05-14 15:33:15 -07:00

asset-engine

catalog: promote chatterbox-fast to ready; vibevoice->down; resolve voxtral 8197 collision

2026-06-02 09:10:57 -07:00

design

feat(chatterbox-fast): Phase 1 streaming server — adaptive-chunk scheduler

2026-06-01 22:42:28 -07:00

pfi

2026-04-29 17:03:41 -07:00

runbooks

vllm: rename stack from vllm-qwen3 → vllm + add Skywork reward classifier

2026-05-13 22:00:26 -07:00

orientation.md

docs/runbooks/nh3-prune-ritual: write up the quarterly NH3 prune ceremony

2026-04-27 20:54:08 -07:00

README.md

docs/runbooks/nh3-prune-ritual: write up the quarterly NH3 prune ceremony

2026-04-27 20:54:08 -07:00

README.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/, not docs/.