← All projects

Project notes / Internal platform · case study

Imperion

The studio’s internal platform for agent-assisted work.

Previously called Zero; Zero remains an internal alias. Imperion integrates multiple agent harnesses, including Hermes Agent from Nous Research, alongside Codex, Claude Code, and MCP tools.

Imperion / system overview
Starts withHuman direction & scoped work
Workflow coordinationImperionTask scope · context · model routing
ExecuteRuntimes & tools

Hermes Agent · Codex
Claude Code · MCPs

RetainContext & evidence

Memory · retrieval
Execution records

Recorded results. Human review.
Approval where required.

Conceptual overview, not an execution sequence. Human approval gates actions where required. Hermes Agent is developed by Nous Research; Imperion integrates it with other tools and operating controls.

What it does

Imperion integrates multiple agent harnesses with scoped workflows, retained context, tools, automation, and human review inside Zendren. It is internal infrastructure, not a customer SaaS product.

The problem

Long-running agent work needs more than a prompt. Tasks cross sessions and tools, context needs to survive, and consequential actions need a human decision.

How it works

Imperion integrates Hermes Agent (Nous Research), Codex, Claude Code, MCP services, memory, and host bridges. Work is organized into scoped tasks with recorded results and review boundaries. Some steps are automated; others are interactive or require approval. The platform combines these tools with Zendren’s operating controls.

Integration engineering

Zendren connects agent harnesses, MCP tools, retained memory, and host environments through scoped workflows. The work includes model and provider compatibility, failure-path tests, and recovery procedures rather than treating each session as an isolated prompt.

Authority and verification

Tasks carry scope and approval boundaries. Execution records and review steps distinguish a proposed action from a verified result; financial, public, and other consequential actions remain subject to their applicable human-approval rules.

Technical notes

  • Scoped work, scheduled workflows, and model routing
  • Retained context, memory, and retrieval across sessions
  • MCP integrations and bridges between tools and host environments
  • Recorded results, human review, and approval boundaries