vh
70f7c0e4a2
The base-viability pre-flight had three checks (fits / MoE expert mapping / LoRA support) and would have passed Qwen3.5-0.8B-Base clean while it trained 2.6x slower than a dense model 2.3x its size. Check 4 closes that: read `layer_types` for a linear_attention majority AND probe for mamba_ssm / causal_conv1d / fla / kernels. It is the intersection that is slow -- a hybrid shape with the kernel present is fine, a dense shape does not care. Carries the measured table (gx10 GB10, n=10/arm, spreads 0.6-2.6%), plus the two things a hybrid Base checkpoint brings that a dense one does not: a vision tower and MTP head that target_modules="all-linear" would train on text, and the module rename that AutoModelForCausalLM introduces relative to the vLLM serving class; and unsafe cross-document packing, since SSM state ignores the attention mask. Section heading corrected from "three greps" to "four checks". The example was made runnable and verified on the box rather than shipped untested.
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/.