Stefan Ianta · Ianta Labs

Tools for AI professionals

A 4k agentic desk, the shared surface it posts to, and the server underneath — all built and in daily use.

AI product & platformbuilding in the open, running in private

Software for building virtual AI Nations — communities, families and businesses where pros and their agents share and distribute projects, skills and workloads.

The bet is that the unit of AI work stops being one person at one chat window. It becomes a desk a professional actually lives in, a shared surface where their agents post and hand work to each other, and a substrate that keeps both running. Everything below is evidence for that sentence — built for my own use first, which is why most of it is private and in daily operation rather than packaged.

01The work

The desk · current main product

3AI Desk

A 4k agentic workspace for AI pros — a board of live cells where text, spreadsheets, terminals and agent chats sit side by side on one screen, instead of behind tabs.

  • Built for a 4k display. The point of the resolution is parallelism — a POS loop of cells you supervise at once, not a single conversation you scroll.
  • Mixed cell types on one board — text and spreadsheet cells, terminal cells, agent chat, and board views.
  • Terminals are first-class. Shell cells run through the editor server's own bridge, with no external terminal daemon to install or keep alive.
  • Runs on the LAN, so the Desk on the 4k monitor and a second device can address the same workspace.
  • The layout is an argument. Five overlays redraw the same grid as the SellOpsPay engine, as life's power loop, and as the raw subagent steps — the analogy the desk was designed around, not a diagram added afterwards.
iantalabs/3aidesk · private, in active useHugo · Node · agent cells
The SOP overlay on the Desk — i.SOW, x.Project, y.Agent, z.Bank with Sell, Ops, Pay and Loop bands
The SOP overlay — Sell › Ops › Pay › Loop across the four containers.
The engine loop in full — Dev steps a to j paired with Ops steps k to t, each pair gated to GO or NO-GO
The same grid in full — Dev `a–j` paired with Ops `k–t`, each pair gated.
The shared surface

ncol

Element Web modules turning a Matrix homeserver into a multi-column room wall for large displays — the surface where pros and their agents post, and hand work to each other.

  • A multi-column wall, built for the same wide display the Desk targets. Each column header cycles Room → Split → Thread, so one screen can hold a room, its threads, or both.
  • Not a fork of Element. Each module builds to a single JS file that a stock Element loads from one line of config — the upstream release is a pinned dependency, never a base to rebase onto.
  • An upgrade gate, not a hope: a smoke suite of 15 checks runs the modules against a stock release before any version bump lands.
  • Inline SVG posts and a composer height cap, so agent output arrives as something readable in the room rather than an attachment to download.
  • Agents post here directly. The repo's Matrix poster sends a coding agent's response straight into that project's room — the notes on this site's own build arrive that way.
iantalabs/ncol · private, in active useElement Web modules · TypeScript · Matrix
The ncol wall running three Matrix rooms side by side across a wide display, each column a full room view
Three project rooms in parallel on one wide display — each column a live Matrix room.
The substrate

famops

Operations for the machine underneath — a Matrix homeserver, Element Call and the family's websites, run on a 2012 Mac mini, with the runbook and the live status dashboard treated as part of the system.

  • A real homeserver, not a toy. Matrix, video calling and public sites run behind a tunnel, with the media store and the database deliberately on different disks.
  • A live operations dashboard, admin-gated: current status of the server and the sites it serves, denied on the public listener and reachable only over the private network.
  • Decisions are written down. A standing rule to read the decision log before changing anything non-trivial — several choices look wrong until you know what was ruled out.
  • Nine corruption incidents traced to one root cause — a database living on the wrong filesystem — and migrated off it. The incident record is part of the repo, not separate from it.
  • This site deploys through it. One script builds and ships each site, then verifies the result at every URL it is meant to answer on.
iantalabs/family-server-ops · private, in active useMatrix/Synapse · Docker · nginx · Cloudflare Tunnel
The famops runbook index — cards linking to server procedures, decisions and the maintenance log
The runbook front-end. Every card is rendered from the ops repo's own checkout, never copied.

02Also in the labs

ai-pro-career

A six-month pilot testing whether three agent-run repos, each owning one stage of a career pipeline, work as a system — reporting only, never commanding.

iantalabs/ai-pro-career · private, in active use

ai-bio-energetics

A catalogue of the cell's energy reactions, supplying the mechanistic layer a purely statistical VO₂max forecast is missing.

iantalabs/ai-bio-energetics · private, in active use

clock

A clock and stopwatch with large digits, built for reading across a room mid-session. React and Vite, building to a single HTML file.

github.com/iantalabs/clock

DNA › RNA › ATP and Sell › Ops › Pay

A coming site putting the two loops side by side — where life's power loop and the SellOpsPay delivery engine match, where they differ, and what the differences say to build next.

coming
Interested in any of this?

The tools are in private use while they are built. If something here is worth a conversation — the Desk, the shared surface, or how the pieces fit into an AI Nation — the way in is a message on LinkedIn.

Connect on LinkedIn For recruiters