Poid-ZA HERMES Engineering workspace and automation stack

Current engineering workspace

Durable memory, low-token execution, and verified recovery in one Hermes-based setup.

The current stack is centered on Hermes: a local engineering workspace with durable memory, reusable skills, secure backup discipline, and static-first delivery for real projects rather than demo theatrics.

View current posture Open Hermes backup repo
  • Hermes durable memory
  • Reusable skills and workflows
  • Sanitized backup + restore path
  • Static website delivery
Current posture
WorkspaceHermes local engineering stack
MemoryDurable memory + user profile + skills
ExecutionTool-first, low-token, verification-driven
RecoverySanitized backup repo with integrity checks
DeliveryStatic HTML/CSS/vanilla-JS handoff

Overview

A cleaner public explanation of the current stack, not the retired one.

The earlier public surface still reflected the older APEX/OpenClaw phase. This version is aligned to the live Hermes workspace: memory-aware, skill-driven, security-conscious, and built around low-token execution with static delivery where practical.

01

Workspace core

Hermes provides the local operator shell, durable memory, user profile, and tool-driven execution model.

02

Skill layer

Reusable skills capture working patterns for planning, debugging, security review, site building, and backup discipline.

03

Recovery posture

Sanitized GitHub backup, integrity verification, and restore scripts make configuration recovery straightforward.

Systems

Built around a practical Hermes loop: remember, execute, verify, recover.

Loop

Memory → Execution → Verification → Recovery

Work starts from retained context, moves through tool-first execution, is checked before signoff, and stays recoverable through sanitized backups.

Memory → Execution → Verification → Recovery
Memory

Durable workspace memory

  • User profile and compact durable memory
  • Session search for past work recall
  • Skill-based capture of reusable procedures
Execution

Low-token, tool-first delivery

  • Search before create, inspect before edit
  • Static HTML/CSS/vanilla-JS as the default web handoff
  • Verification scaled to the risk of the task
Improvement

Security and integrity discipline

  • Prompt-injection and secret-handling guardrails
  • Integrity-checked configuration backups
  • Conservative updates after user correction

Proof

The public page now matches the current controls and artifacts.

Current workspace summary

WORKSPACE  : Hermes local engineering stack
MEMORY     : Durable memory + user profile + skills
EXECUTION  : Tool-first, low-token, verification-driven
BACKUP     : Sanitized GitHub backup + restore scripts
SECURITY   : Prompt-injection and secret-handling guardrails
DELIVERY   : Static GitHub Pages surface

Backup integrity

Configuration backup now lives in a sanitized GitHub repo with manifest hashes, verification, and restore scripts.

Operating style

Current work is optimized for concise output, explicit verification, and conservative changes after feedback.

Website delivery

The site itself is delivered as static HTML, CSS, and vanilla JavaScript with no framework dependency after handoff.

Evolution

From the older APEX/OpenClaw phase to the current Hermes-based workflow.

Earlier phase

OpenClaw and APEX groundwork

The earlier stack established strong ideas around memory, operational discipline, backup thinking, and local control surfaces.

Migration

Hermes adopted as the active workspace

The current environment moved into Hermes with durable memory, reusable skills, and a cleaner tool-driven workflow.

Memory

Memory and skills refined

Preferences, environment facts, and repeatable procedures are now captured through Hermes memory and skills instead of ad hoc notes.

Security

Backup and integrity hardening added

Sanitized backup repositories, manifest verification, and restore scripts now support easier recovery without leaking secrets.

Now

Low-token, static-first operating style

The live workflow now emphasizes concise execution, conservative changes, static delivery, and verification that scales with task risk.

References

Relevant current artifacts, without dragging the homepage back into the old stack.

Hermes config backup Sanitized backup, integrity checks, and restore workflow Website repository Source for the current static site Earlier platform repo Historical context for the pre-Hermes phase

Delivery

Static, deployable, and aligned to the live Hermes setup.

The public site now reflects the current operating reality: Hermes for the active workspace, a sanitized GitHub backup for restore, and static HTML/CSS/vanilla-JS for straightforward delivery.

Hermes workspace Sanitized backup repo Vanilla JavaScript Centered static layout
Open website repo Open Hermes backup repo