live visual scratchpad · pick a lane / roast freely

Four directions that are not more Vercel cosplay.

These are deliberately divergent mood prototypes for the next dkta.dev pass. They are not final copy or layout; they are taste probes. Tell me which one has a pulse.

reply: “A/B/C/D” or: “B but warmer” or: “none, make it stranger”

A · Agent field notes

Editorial / zine / technical notebook. Personal, smart, less startup-polish.

Infrastructure as field work.

A site that feels like Dakota is publishing from inside the systems: notes, artifacts, failures, recovered context, shipped loops.

B · Control room

Ops cockpit / mission control. More infra-native, urgent, active.

Agent systems require operators.

Make the landing page feel like the surface of a running autonomous stack: live signals, workers, triggers, memory, deploys.

memdurable context

evallong horizon

shipprod loops

C · Personal mainframe

Retro-future terminal. Weird, compact, agent-built, not generic SaaS.

DKTA/OS boots agents into useful work.

Less landing page, more strange personal operating system: logs, commands, services, subdomains, autonomous workers.

load memory surface

open retrieval port

spawn eval environment

ship via autonomous deploy loop

D · Artifact gallery

Museum / portfolio without portfolio clichés. Calm, memorable, high taste.

Shipped systems as exhibits.

The site becomes a gallery of agent infrastructure artifacts: Engram, Extract, TavernBench, and the invisible deployment machinery.

Engrammemory

Extractretrieval

TavernBenchevals

Fast loop: you reply from Telegram, I mutate this scratch page, redeploy, and send the refreshed URL.

scratch.dkta.dev · noindex · disposable