High-ArchyTech-SolutionsThis plugin has no README in the catalog yet.
All plugins
archytan-lite
Every tool call is decided by Archytan Lite, an authorization gate that runs outside Hermes with its own signing key, before the tool runs. A call becomes checks on what it touches (each file path, each program and git subcommand a command runs, every path and URL it names, each host fetched, MCP and plugin tools by name); all must be ALLOWed, and each ALLOW is a single-use permission spent just before the tool runs. Refusals use the block directive, so they hold under /yolo and approvals.mode: off. Anything the plugin can't read precisely ($VAR, $(...), loops, unpinnable paths), any error, an unreachable gate or a bad signature is refused. Every decision is an Ed25519-signed, hash-chained receipt; `hermes archytan verify` checks the whole log. Starter policy for one workspace, edited as JSON and applied with `hermes archytan reload`. Disclosure: the gate is proprietary software by the plugin's maintainer, free under its Community license, run from ghcr.io/high-archytech-solutions/archytan-lite@sha256:205703a7fc67a9e96aa0930fd9dda83fe2b9694b724b13dea8c1854948e82071 (2.7.1), which the plugin never pulls unless you pass --pull; `hermes archytan setup|reload|verify` and `/archytan verify` run docker with a minimal environment and create the volume archytan-hermes-data and the container archytan-hermes (restart unless-stopped, bound to 127.0.0.1:8431); the hook sends each gated call's action, resource (path, program, host or tool name) and hermes:<session id> to that local gate, never argument contents or results; stores its caller token through Hermes's credential store as ARCHYTAN_LITE_HERMES_TOKEN; writes the gate's policy, callers file (token hash only), public key and a capped decisions.jsonl under plugin-data/archytan-lite; carries the gate's MIT Python client (archytan-lite 2.1.1 client.py, byte-identical) so it has no Python dependencies; no telemetry. Until setup has run, every gated tool call is refused.
About
Every tool call is decided by Archytan Lite, an authorization gate that runs outside Hermes with its own signing key, before the tool runs. A call becomes checks on what it touches (each file path, each program and git subcommand a command runs, every path and URL it names, each host fetched, MCP and plugin tools by name); all must be ALLOWed, and each ALLOW is a single-use permission spent just before the tool runs. Refusals use the block directive, so they hold under /yolo and approvals.mode: off. Anything the plugin can't read precisely ($VAR, $(...), loops, unpinnable paths), any error, an unreachable gate or a bad signature is refused. Every decision is an Ed25519-signed, hash-chained receipt; `hermes archytan verify` checks the whole log. Starter policy for one workspace, edited as JSON and applied with `hermes archytan reload`. Disclosure: the gate is proprietary software by the plugin's maintainer, free under its Community license, run from ghcr.io/high-archytech-solutions/archytan-lite@sha256:205703a7fc67a9e96aa0930fd9dda83fe2b9694b724b13dea8c1854948e82071 (2.7.1), which the plugin never pulls unless you pass --pull; `hermes archytan setup|reload|verify` and `/archytan verify` run docker with a minimal environment and create the volume archytan-hermes-data and the container archytan-hermes (restart unless-stopped, bound to 127.0.0.1:8431); the hook sends each gated call's action, resource (path, program, host or tool name) and hermes:<session id> to that local gate, never argument contents or results; stores its caller token through Hermes's credential store as ARCHYTAN_LITE_HERMES_TOKEN; writes the gate's policy, callers file (token hash only), public key and a capped decisions.jsonl under plugin-data/archytan-lite; carries the gate's MIT Python client (archytan-lite 2.1.1 client.py, byte-identical) so it has no Python dependencies; no telemetry. Until setup has run, every gated tool call is refused.