Gig
$6/hour
20
Mar 28, 2026
1. What You Are Building
An autonomous development agent system running on a dedicated VPS. The system consists of two components: EVA (the conversational interface) and ZION (the orchestration layer that directs Claude Code workers to execute development tasks).
I interact with EVA via
SCOPE
You are building EVA and ZION only. Claude Code is an existing tool you will install and wire up. You are not building any downstream applications — ZION will build those after handoff.
2. How It Works
Component
Role
EVA
Conversational AI interface. Listens on
ZION
Orchestrator. Receives briefs from EVA. Manages task queue. Assigns tasks to Claude Code workers in sequence. Halts on failure. Reports blockers back to EVA. That is all ZION does.
Claude Code workers
Execution layer. Called by ZION. Each worker performs one task. Returns output or failure to ZION.
COMMUNICATION RULE
ZION never contacts me directly. ZION never posts to
3. Non-Negotiables
You have latitude on implementation approach with two hard exceptions.
3.1 ZION is a pure orchestrator
ZION coordinates workers. ZION does not perform computation, transform data, validate business logic, repair errors, retry silently, or contain fallback logic. If ZION does any of these things it becomes unmaintainable. This is the most common mistake and it will not be accepted.
SIMPLE TEST
If ZION were removed from the system, no business logic should be lost. Only coordination is lost. If removing ZION breaks logic, ZION was doing too much.
3.2 Single responsibility workers
Each Claude Code worker does one thing. A worker that reads data is not the same worker that processes it. A worker that processes data is not the same worker that writes it. Single responsibility means a failure is always isolated to one worker. The blast radius never cascades.
4. EVA Specification
•
•
• Generates structured task briefs and passes to ZION
• Receives escalations from ZION, attempts to resolve using known context before pinging me
• Posts project updates to correct
• Saves every conversation as a .md file to /opt/devagent/conversations/ with topic-based filename
• Manages the SOP decision engine (see Section 6)
5. ZION Specification
• Pure Python orchestrator — no n8n, no Zapier, no low-code tools
• Receives structured briefs from EVA
• Maintains independent task queue per project
• Calls Claude Code workers non-interactively in defined sequence
• Respects task dependencies — does not run step 3 before step 2 is complete
• Halts on worker failure — no silent retry, no self-repair
• Reports failure to EVA with enough context for EVA to escalate or resolve
• Returns deterministic exit state on completion
6. SOP Decision Engine
EVA manages a decision engine that learns my preferences over time and reduces how often I need to be interrupted.
• Every decision I make is logged as PENDING with vote count 1
• Same decision type resolved the same way — vote count increments
• Three consistent votes promotes the decision to a standing rule (SOP)
• On promotion EVA sends
• Conflicting resolution before 3 votes — votes reset, EVA sends
• REVOKE command deletes any standing rule
7. Accounts & Credentials
Service
Requirement
Google Workspace
Telegram
Created
New token for EVA. Separate from existing Profe bots.
Claude API
Key provided by me. Connected to Claude Code and EVA.
GitHub
New account under claude@
8. VPS & Deployment
• IONOS VPS — 8 vCores, 16 GB RAM, 480 GB NVMe, Ubuntu
• New installation at /opt/devagent — isolated from everything else on the server
• EVA and ZION run as systemd services with auto-restart on failure
• Claude Code installed globally and callable non-interactively
• All credentials in .env files — nothing hardcoded
DO NOT TOUCH
/opt/openclaw — existing customer-facing bots. You have no authorization to access, read, or modify anything in this directory.
9. Acceptance Criteria
Item
Pass Condition
Claude Code
Installed globally, callable non-interactively by ZION, test task executes cleanly
ZION
Pure orchestrator, no business logic, single failure does not cascade, task queue works
EVA —
Receives messages, generates briefs, passes to ZION, posts to correct channels
EVA —
Receives messages, sends notifications, REVOKE command works
SOP engine
3-vote promotion works, conflict detection fires, REVOKE deletes rule
Conversation archiving
Every conversation saved as .md with topic-based filename
Systemd services
Both services auto-restart, survive server reboot
End to end test
Task sent via
Handoff document
All credentials, file paths, service commands, restart procedures documented
10. Before You Apply
Answer these two questions. They tell me whether you read this brief.
• In your own words: what is ZION's job and what is it explicitly not allowed to do?
• This build is pure Python on a Linux VPS. No low-code tools anywhere in EVA or ZION. Are you comfortable with that and what similar Python systems have you built?
Jaimi M. Saunders, PhD | Fidelis Consulting & Training LLC