A view, not a fence

Admin or server operator

Dependencies, operational truth, privacy boundaries, failure modes, and recovery paths.

Your question: What runs, what does it cost, and how do I operate or recover it? Start here, then cross the lane whenever something catches your eye.

Choose another lens

Start in your lane

live

ComfyStewardView

Reads a Valheim world file and answers the questions that stop being walkable once a server gets big: where is everyone building, and who owns this.

local-only

Live Community Telemetry

An aggregates-only telemetry API with privacy tests that fail if a player ID, name, or position ever shows up — plus the whole stack, runnable on your machine.

portal

Baseline

The public hub for the repository map, durable decisions, evidence, corpus, and discovery surfaces of the Valheim project fleet.

live

Quest Picker + Absorption Engine

Turns a guild's real quest tracker into a single offline page where a player checks the quests they care about — and the game mod reads the result.

local-only

Quest Submission → Review Bridge

The back half of quest capture: package what a player did in-game, land it in a review inbox, and turn it into a record a GM can read.

local-only

Steam Self-Service Join

An invite link, a Steam sign-in, and a mod-pack zip with your credentials already in it — no config file to hand-edit.

Recent work touching this lane

Transferred Lumberjacks platform ownership to its sovereign repository

Gateway, Companion, P7 infrastructure, live FieldLab harnesses, and the roadmap journal now live in djcdevelopment/lumberjacks-platform. The roadmap command and pre-commit ceremony move with that implementation authority; baseline remains the evidence archive and fleet index rather than a source fallback.

Decouple the repo seams in place ahead of the sovereign split

Quest glue and transport contracts now travel as source packages (Comfy.Quest.Contracts, Comfy.Transport.Contracts); the fused test project split along the quest seam with count conservation (166+185=351); Quest Studio carved behind IQuestStudioHost with route parity 10/10; cross-seam scripts parameterized behavior-preserving. Extraction of networksense, lumberjacks-platform, and comfy-quest can now proceed from one green tag.

Publish the audience-aware Workbench from committed source inputs

The generated Workbench now carries a production provenance stamp for the committed audience vocabulary, catalog, and renderer instead of a preview stamp. The companion corpus projections were rebuilt after the deployment record, keeping the public index and roadmap adapter byte-current with their authoritative journal.

The Quest Lab is live: tome, download and all, and the last blocker was a Caddy allowlist nobody had written down

Cut m31-questlab-20260808-r1, shipped it to AM4 with the new isolate deploy lane, recreated lj-workbench on it, and published. The download streams 74949 bytes at d49a20db and /questlab serves the real tome from the mount with X-QuestLab-Sha256 equal to the committed file. THE ACTUAL BLOCKER was neither the image nor the publish: Tailscale Funnel sends / to Caddy on 8190, and Caddy forwards a deliberate allowlist of paths to the Gateway, answering an honest 404 for everything else so that /ops/* is never funneled. The container answered /questlab correctly for twelve minutes while the origin still 404d. Adding /questlab to the @public matcher and reloading was the fix; the boundary was re-checked afterwards and still holds, /ops/* 403 and unmatched 404. That Caddyfile is host-only config carrying bcrypt credentials, so only the mechanism is documented, in START-HERE, in the publish script header, and in the deploy lane README where somebody adding a route will actually look. Also learned: questlab.html and workbench.html are not baked into the image at all -- both have always been served from the mount, and the fallback page is what /questlab served in the gap.

Explore everything, including work outside this lens →