vh
95ab344990
Reported by draupnir after the Booth v0.2.0 consumer note, and it is the higher-impact half of what it found: this file is autoloaded by every agent family on this box through the shared FLEETTOOLS bootstrap pointer, so it is the first thing a cold session reads about the Booth. Draupnir was a live specimen — it read this page earlier in the same session to post a booth, before the announcement landed, and only luck of scope kept it off the broken surfaces. Stale and now corrected: `booth asks` presented as the listing verb (it is a deprecated alias and emits JSON now, not the old table); `<stem>.ask.json` / `<stem>.answer.json` presented as the storage (one `.marks.json` per booth replaced them, and the answer sidecar 404s forever, so a remote session polling it is polling nothing); the `#ask-<stem>` anchor convention. Not stale, and left alone deliberately: the `data-booth-ask=` placeholder conventions. The inline placement engine survives v0.2 and is removed in a later unit, so those still work exactly as documented. Added: `booth marks` and `booth marks-import`, the marks.json HTTP read path, the partially-answered-counts-as-open change, and the 409-on-damaged-file behaviour.
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/.