Skip to content
DURABLE AGENT OPERATIONS

PraxisForge AI

Three bounded Hermes roles turn permitted knowledge into reviewed drafts, commitments and internal receipts.

PraxisForge AI public agent-operations website
CURRENT SCOPE

Deployed owner operations with exact human approval

WHO IT'S FOR

Independent build

My self-hosted Hermes-powered operations platform. A configured owner reviews exact artifacts; internal receipts do not imply external email or CRM delivery.

THE ENGINEERING

A self-hosted agent operations platform using Nous Research's Hermes Agent, PostgreSQL workflow ownership and bounded coordinator, researcher and operator roles. Authenticated Operations provides versioned text knowledge, durable tasks, retries/cancellation, source-linked structured outputs, exact human approval, internal receipts and persisted workflow memory. The October 15 live workflow recovered after a worker interruption, completed all three roles and recorded two source-backed commitments with an internal receipt. Altered approval and replay were rejected; encrypted off-host database restoration matched schema and business records. This is one successful workflow, not a statistical reliability benchmark. Approval commits internal records; email delivery and third-party CRM updates are not enabled. Open registration, subscription checkout, broader customer admission, scheduled recovery guarantees and million-user capacity remain separate gates.

Hermes AgentPythonPostgreSQLNext.jsLocal inference

BEFORE → AFTER

Real problems from this build, what I changed and the verified result.

  1. CASE 01
    Before

    An interrupted agent worker can lose task ownership or allow stale work to settle.

    After

    The same live task recovered after a deliberate worker interruption, completed three roles and reached approval without another submission.

    How I fixed it

    Stored durable task ownership in PostgreSQL with fenced leases and bounded recovery attempts.

  2. CASE 02
    Before

    Approval can be replayed or applied after the artifact, actor or source changes.

    After

    Altered approval and replay were rejected in the actual UI flow; approved commitments and an internal receipt were recorded together.

    How I fixed it

    Bound approval to the exact actor, workspace, task, operation, content, source hashes and expiry; committed business records atomically.

  3. CASE 03
    Before

    An encrypted backup file alone does not prove recovery is possible.

    After

    Schema and 11 business tables with 26 rows matched the tested snapshot. Full host replacement and scheduled RPO/RTO remain unproven.

    How I fixed it

    Authenticated an off-host encrypted export and restored it into a fresh isolated database.

Evidence reviewed: Source review October 16, 2026; October 15 release evidence and open gates stated above