AXJNS.DEV — OPERATIONAL▸▸▸PRINCIPAL ENGINEER @ AWS▸▸▸FOUNDER — K8SGPT.AI▸▸▸OPEN SOURCE: ACTIVE▸▸▸LOCATION: LONDON, UK▸▸▸DISTRIBUTED SYSTEMS / KUBERNETES / AI▸▸▸RUST + GO + PYTHON▸▸▸FIELD TESTED / STATUS — NOMINAL▸▸▸AXJNS.DEV — OPERATIONAL▸▸▸PRINCIPAL ENGINEER @ AWS▸▸▸FOUNDER — K8SGPT.AI▸▸▸OPEN SOURCE: ACTIVE▸▸▸LOCATION: LONDON, UK▸▸▸DISTRIBUTED SYSTEMS / KUBERNETES / AI▸▸▸RUST + GO + PYTHON▸▸▸FIELD TESTED / STATUS — NOMINAL▸▸▸
[ 006 / field status ]

Now building.

A short, dated view of the work in motion.

Celln

Building an execution plane for agents: isolated cells that borrow verified tools rather than assembling mutable environments. The immediate work is making the real KVM path easy to install, inspect and prove.

Sympozium

Exploring a clean split between coordination and execution. Sympozium should own workflow, policy and shared state; Celln may become the smaller execution primitive beneath an AgentRun.

Questions I am following

  • What does a useful persistent agent API require beyond one-shot jobs?
  • Which capabilities should an agent request explicitly: tools, files, egress, time, memory?
  • How do we make revocation and provenance operational rather than aspirational?

Updated August 2026 · read the Celln notes →