Tools, half-finished

Behind the bevel.
The studio floor.

Side of the site where experiments live. A command palette I actually use, synthetic host pings, the occasional hex dump, and a ticker that re-samples what the month felt like. Nothing here is a portfolio piece — everything here is working material.

01 · command

Command palette

K
↑ ↓ to move
inert · demo5 matches

Same shell I use locally to route between builds, scans, and drafts. This one’s wired to nothing — you can type, it won’t bite.

02 · telemetry

Host pings

  • gw.lanedge router
    4ms
  • omniapx.lanmodel host
    11ms
  • kuba-hdx.devvercel · prod
    38ms
  • mcp.localtool bridge
    7ms
  • vault.lansecrets
    6ms
  • ci.runnerbuilds
    52ms

Synthetic — drift-sampled from a nominal baseline. Real deploy telemetry never lands on the public site.

03 · inspect

Hex dump

recon.ts · 64 B
00002f2f207265636f6e2e74730a696d706f// recon.ts.impo
00107274207b207a207d2066726f6d20227art { z } from "z
00206f64223b0a6578706f727420636f6e73od";.export cons
003074207363616e203d20746f6f6c280000t scan = tool(..

Static fixture — but the spotlight is real. Good reminder that everything compiles down to bytes, and bytes don’t lie.

04 · telemetry band

What the month looked like

Honest-ish numbers. Some measured, some felt. Re-rendered manually when the month flips.

Direct line · dev

Different inbox. Same reply window.

Messages from this page feed a separate admin tab — useful for keeping studio-floor questions out of the main inbox. Pick which widget you were exploring and I’ll know what to open first.

  • Rate-limited to 5/min per IP
  • Stored locally; no third-party relay
  • Shows up under /admin → Dev inbox