ZENSEN SYSTEMS / Hub
DocsPublish node
ZENSEN/SYSTEMS HUB/FEATURED NODE
NODE PREVIEW // 0x004
⟦⎊⟧ :: ENDER-En0
featured node // Zensen Systems

ENDER-En0

A persistent agent runtime for supervised execution, durable identity, and receipts for every run. Choose a node, wire the contract, and let the system carry the state.

stagedagentotpmesh-ready
Configure node  ↗Read contract  →
Release
0x004 / preview
Owner
3OX / X lane
State
● staged
Endpoint
ender.3ox.me
registry // choose your system

More from Zensen Systems

⌁
preview

ENDER-En0

Persistent agent runtime

A durable identity and supervised execution seat for agents that need to outlive one prompt.

runtime · 0x004
Ω
staged

ORION OTP

One-time passcode protocol

A small, legible boundary for authorization, handoff, and receipts across the living chain.

protocol · Z lane
Y
building

ENKEY / SYSGEN

Identity emission bus

Emit names, runtime pointers, and installable system shape from one small command surface.

runtime · Y lane
Z
map

ZENOS

Operating surface for the suite

A quiet environment where the suite, its tools, and its operators can find one another.

surface · suite
M
lab

MARDUK

Heavy execution seat

A high-energy work surface for the jobs that need more metal, more memory, and a clear return path.

runtime · lab
✦
draft

3OX STUDIO

Build surface for new agents

Compose an agent surface, attach its contract, and send it into the registry when it is ready.

surface · authoring

ENDER-En0 / contract

public preview
The first thing a node should make clear is what it owns. ENDER-En0 owns the identity, supervised runs, and the receipt that explains what happened. The deployment surface remains intentionally small while the system is in staging.