EXPERIMENTALAGENTS · SYSTEMS2026

HERMES

One orchestrator. One engineer. Zero fabrication.

A working experiment: it orchestrates files, contracts, and evidence locally. External action and full autonomy remain explicitly out of scope.

HermesOpenCodeMarkdownCLI toolingSQLite
A

Overview

Hermes is the executive agent inside the Aethelion operating system. It keeps the registry of companies and departments, writes task contracts, persists memory, and delegates implementation work to Engineering — specifically to OpenCode.

The architecture is deliberately interior: it orchestrates files, contracts, and evidence on the local system. It does not pretend to act on the outside world without the owner's approval.

B

Problem

AI-assisted development decays into scattered chats and unverifiable claims. Hermes exists to make the loop observable: a documented chain from decision → delegation → execution → verification → report.

C

Approach

  • A registry of departments and agents — Executive, Engineering, Research, Product, Design, QA, Security, Marketing, Sales.
  • Task contracts with explicit acceptance criteria and an audit trail.
  • Persistence in SQLite and a documented memory log (verified success on write).
  • A hard boundary: no autonomous external action, sales, or deployment without the owner.
D

Architecture

Architecture

INTENT: this is the actual design the system was built against — not a decorative diagram.

E

Implementation

  • Agent registry and department definitions written as markdown, verified by inspection.
  • Task contracts with PASS/FAIL states — task-001 (foundation build) passed with files verified.
  • SQLite persistence across agents, tasks, projects, executions, and evidence tables.
  • Mission reports (001b, 002, 003) document each run, including where OpenCode was blocked by permissions and where fallback execution was used — failures documented as honestly as successes.
F

Technology

Hermes agent (orchestration)OpenCode v1.18 (engineering delegate)Markdown-structured contracts and knowledgeCLI tooling and file-system operationsSQLite for the audit trailFlask API exposing the evidence
G

Workflow

  • Hermes defines the mission and scope.
  • Engineering is delegated via OpenCode; where access is blocked, the limit is documented.
  • Hermes verifies artifacts by direct inspection (ls + read).
  • Results are written into mission reports with an explicit verdict.
  • Nothing external happens without owner approval.
H

My Role

  • Designed the architecture and the doctrine, defined the departments and contracts,
  • operate the orchestrator, verify every artifact, and audit the results.
I

Demo

Inspected evidence

The full operating artifacts — registry, reports, task contracts, SQLite database — live in the Aethelion repository and can be inspected.

K

Source

  • AETHELION/ working repository: agents/, knowledge/, tasks/, reports/, core/.
  • HERMES_REPORT.md — master inventory of everything verified, dated.
L

Status

Verified

  • Agent registry exists and is consistent.
  • Department structure defined: Executive, Engineering, Research, Product, Design, QA, Security, Marketing, Sales.
  • Engineering delegation to OpenCode verified available; invocation pattern documented.
  • Task-001 PASSED — foundation artifacts verified by direct inspection.
  • Memory persisted with verified success flag.
  • SQLite database present with 6 real tables including an audit trail.
  • Flask API built and parameterized against that data.
  • Mission reports 001b/002/003 exist with honest verdicts — including documented failures.

Planned / Out of scope

  • Full autonomy or uninstructed external action (explicitly out of scope).
  • Research, Product, Design, QA, Security, Marketing and Sales remain defined but unassigned.
  • Public deployment of the orchestration dashboard.

Separating verified from planned is a design principle of this portfolio — not a footnote.

No live URL is shown because this project is not publicly deployed. If that changes, the link appears here automatically.