Skip to main content

Module hermes

Module hermes 

Source
Expand description

A Hermes home written from the orchestration (hermes.mjs::toHermes). Tiers per file: byte for cron/jobs.json, cron/executions.db, webhook_subscriptions.json (inline secrets re-inlined from the vault), config.yaml when unchanged, every unmodeled file, and state.db when bindings/obligations are UNCHANGED since import (copied). A FRESH destination gets a store born at the fixture’s schema (22) carrying the bindings as sessions rows and the obligations as delivery_obligations rows — Hermes migrates it on open; the transcripts live in the worker’s store and are not carried (semantic). A LIVE destination store is never written: that first write into a shared WAL single-writer store is UNI-18’s, refused by name. state.db with changed rows is REFUSED: the Hermes session-store write path is behind UNI-22. Semantic for SOUL.mdAGENTS.md and a re-rendered config.yaml (the O-blocks ride as top-level keys — ORC-1 F5).

Structs§

HermesReport
What a Hermes decompile did.
Refusal
A write the codec would not guess at.

Functions§

from_hermes
Load a Hermes home into the orchestration.
to_hermes
Write a Hermes home. Byte-tier files whose records are unchanged since a Hermes import are copied from the import source; everything else is emitted canonically.