SyslogSolution/prose-contracts
7
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

2026-07-03: Hermes key enforcement contract + Stirling-PDF docs + config standardization

Browse Source 
- hermes-key-enforcement.prose.md: NEW contract enforcing api_key_env for all harness/LiteLLM providers, exempting external providers
- hermes-config-template.prose.md: Updated with full fix log (15 total fixes across Koby/Koonimo/Mumuni/Tanko), model:auto detection rule, key-to-agent mapping
- infrastructure-control.prose.md: Added Stirling-PDF service details (port 8989, credentials, API key, Swagger URL) replacing Bento-PDF
This commit is contained in:
Abiba
2026-07-03 18:19:41 +00:00
parent a985748994
commit c1bdbbc491
3 changed files with 354 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files
hermes-config-template.prose.md
+152 -10
View File
@@ -5,7 +5,13 @@ description: >
Standard Hermes configuration template for Syslog Solution LLC agents.
Enforces shared infrastructure setup (Firecrawl, SearXNG, local models,
RA-H OS MCP) while keeping agent-specific API keys and model choices.
Updated 2026-06-30: new LiteLLM keys, nginx routing, router back online.
Updated 2026-07-03 (19:14 EDT): Full sweep — Koby (11 fixes), Mumuni (1 fix),
Koonimo (3 fixes). All agents now CLEAN: zero model:auto, zero deprecated
sk-syslog-* keys. Tanko has hardcoded tanko-v2 key (correct, but should use
api_key_env for rotation safety). Kagenz0 is DOWN (no config, no key).
Previous: full key audit — mumuni-v3 + context7-mcp registered,
/etc/environment aligned, double-B8nw incident documented, all 17 LiteLLM
keys mapped with active/inactive status.
---
## Maintains
@@ -16,15 +22,90 @@ description: >
- agent_keys: managed in LiteLLM DB — current aliases in Key Management section below
- infra_endpoints_verified: array
### Agent topology
| Agent | CT | IP | Key Alias | Startup | Zulip Owner |
|-------|-----|-----|-----------|---------|-------------|
| Tanko | 112 | 192.168.68.122 | `tanko-v3` | systemd user + `.env` | Jerome only ✅ |
| Mumuni | 114 | 192.168.68.123 | `mumuni-v3` | systemd user + `.env` | Jerome only ✅ |
| Koonimo | 113 | 192.168.68.114 | `koonimo-v2` | systemd (Discord/Telegram) | N/A |
| Koby | 111 | 192.168.68.129 | `koby-v3` | systemd user (Discord/Telegram) | N/A |
| Abiba | — | 192.168.68.24 | `abiba` | `pi` harness | N/A |
| Kagenz0 | ? | ? | `kagenz0` | unknown | not verified |
### Zulip ownership rules (ALL agents)
**Every Zulip-enabled agent MUST only respond to its owner.** This is enforced
via two env vars in the agent's `.env` file:
```bash
ZULIP_ALLOW_ALL_USERS=false
ZULIP_ALLOWED_USERS=jerome@sysloggh.com
```
- `ZULIP_ALLOW_ALL_USERS=false` — disables the default open-to-everyone mode
- `ZULIP_ALLOWED_USERS=jerome@sysloggh.com` — only Jerome can trigger responses
This applies regardless of whether the agent uses `.env` directly (Mumuni)
or a systemd drop-in (Tanko). Both mechanisms work — the key is that the
env vars reach the Hermes process.
## Key Management
**Source of truth:** LiteLLM PostgreSQL DB. Plaintext keys live ONLY in
`/etc/environment` on each agent host, never hardcoded in contracts or config.yaml.
This contract defines the procedure; it does NOT store plaintext keys.
### Current key aliases (2026-07-02 rotation)
- `tanko-v2`, `mumuni-v2`, `abiba-v2`, `koby-v2`, `koonimo-v2`, `kagenz0-v2`
- `synthetic-monitor` (daily infra report)
### Current key aliases (2026-07-03 audit)
**Active keys (by agent):**
| Agent | Alias | Key (last 8) | Source | Status |
|-------|-------|-------------|--------|--------|
| Tanko | `tanko-v3` | ...JN2OsJw | Process env | Active (needs restart → v2) |
| Tanko | `tanko-v2` | ...1ka8JA | `/etc/environment` | Registered, idle |
| Mumuni | `mumuni-v3` | ...OiWU_B8nw | Process + /etc/env | ✅ Aligned |
| Koonimo | `koonimo-v3` | ...A_wIOA | Config (hardcoded) | Active |
| Koonimo | `koonimo-v2` | ...R7FAobA | `/etc/environment` | Registered, idle |
| Koby | `koby-v3` | ...P4DrWw | `/etc/environment` | ✅ Registered |
| Koby | `koby-hermes` | ...syslog-koby | Config (deprecated) | Active legacy |
| Abiba | `abiba` | ...aLgMw | pi config | ✅ Active |
| Kagenz0 | `kagenz0` | ...Uggg | unknown | Last active Jul 1 |
| Context7 | `context7-mcp` | ...ZPh6VA | Process env | ✅ Registered |
**Unused registrations:** `abiba-v2`, `kagenz0-v2`, `koonimo-v2`, `synthetic-monitor`, `UI Dashboard`, unnamed key
> **2026-07-03 alignment**: Tanko/Koonimo configs updated to use `api_key_env:
> LITELLM_API_KEY` (was hardcoded `sk-syslog-*`). Base URLs corrected to
> `/v1` (was `/litellm/v1`). All active keys now registered in LiteLLM.
> Tanko and Koonimo need Hermes gateway restart for config changes to take
> effect.
### Key lineage
| Agent | Alias | Key (last 8) | Status | Date |
|-------|-------|-------------|--------|------|
| Tanko | `tanko-v3` | ...JN2OsJw | **active** (process) | 2026-07-03 |
| Tanko | `tanko-v2` | ...1ka8JA | idle (in /etc/env) | 2026-07-02 |
| Mumuni | `mumuni-v3` | ...OiWU_B8nw | **active** | 2026-07-03 |
| Mumuni | `mumuni-v2` | ...HcnuOPtQ | superseded | 2026-07-02 |
| Mumuni | `mumuni` | ...62da807e | superseded | 2026-06-30 |
| Koonimo | `koonimo-v3` | ...A_wIOA | **active** (hardcoded) | 2026-07-03 |
| Koonimo | `koonimo-v2` | ...R7FAobA | idle (in /etc/env) | 2026-07-02 |
| Koby | `koby-v3` | ...P4DrWw | **active** (/etc/env) | 2026-07-03 |
| Koby | `koby-hermes` | ...syslog-koby | legacy (in config) | 2026-06-30 |
> **2026-07-03 incidents**:
> - Mumuni: double-B8nw — process had `...POiWU_B8nw`, /etc/environment
> had `...VDtHWd-XiWU_B8nw`. Wrong one registered first.
> - Context7 MCP: `sk-XY2aUfvy2BIs6kp1ZPh6VA` was never registered — the
> original error Kwame reported.
> - Tanko: process key `sk-3ZsdWJbbNSo9zSnJN2OsJw` unregistered. Config
> used deprecated `sk-syslog-tanko`. Both fixed.
> - Koonimo: hardcoded `sk-KFnE3Td6aKEBZxwVA_wIOA` unregistered. Base URL
> used old `/litellm/v1` path. Both fixed.
> - Koby: `/etc/environment` key `sk-x5BnZUUKvz3r8EdLP4DrWw` unregistered.
> Config used deprecated `sk-syslog-koby`. Fixed.
### Verify: all keys working
```bash
@@ -39,7 +120,7 @@ done
### Rotate: generate new key, deploy, verify
```bash
AGENT=mumuni && ALIAS="${AGENT}-v2"
AGENT=mumuni && ALIAS="${AGENT}-v3"
# 1. Generate new key in LiteLLM (master key required)
KEY=$(curl -s -X POST http://192.168.68.116:4001/key/generate \
@@ -60,11 +141,72 @@ ssh root@192.168.68.123 "sudo systemctl restart hermes 2>/dev/null || (pkill -f
### Key deployment rules
1. **Plaintext keys live ONLY in `/etc/environment`** — never in a contract or config.yaml
2. **All configs use `api_key_env: LITELLM_API_KEY`** — indirection prevents staleness
3. **LiteLLM DB is the authoritative key list** — key aliases with active tokens define who has access
4. **Rotate when:** LiteLLM container redeployed, any key 401s, or quarterly
5. **After rotating any key:** restart the corresponding agent gateway
6. **Agents without SSH** (Koby, Koonimo, Kagenz0): deploy via Zulip DM or manual login
7. **Verification is automated** by litellm-self-heal contract (Rule 8: Agent Keys Invalid)
3. **`custom_providers[].api_key` MUST use `api_key_env`** — hardcoded keys shadow env vars and bypass rotation
4. **LiteLLM DB is the authoritative key list** — key aliases with active tokens define who has access
5. **Rotate when:** LiteLLM container redeployed, any key 401s, or quarterly
6. **After rotating any key:** restart the corresponding agent gateway
7. **Agents without SSH** (Koby, Koonimo, Kagenz0): deploy via Zulip DM or manual login
8. **Verification is automated** by litellm-self-heal contract (Rule 8: Agent Keys Invalid)
### Model name enforcement (2026-07-03)
**CRITICAL**: Hermes `model: auto` in any config section gets sent to LiteLLM
as the literal model name "auto", which LiteLLM rejects with 403 because
the registered model is `syslog-auto`, not `auto`.
**Must-fix pattern** — any auxiliary section with `model: auto`:
```yaml
# ❌ BROKEN — sends model "auto" to LiteLLM (403 Forbidden)
auxiliary:
approval:
model: auto
provider: auto
skills_hub:
model: auto
provider: auto
# ✅ FIXED — registered model name
auxiliary:
approval:
model: syslog-auto
provider: harness
api_key_env: LITELLM_API_KEY
base_url: http://192.168.68.116/v1
```
**Detection**: `grep -rn "model: auto" /root/.hermes/config.yaml` on any
Hermes host — if any results found in auxiliary sections, fix immediately.
### Key-to-agent mapping (2026-07-03 final sweep, 19:14 EDT)
| Agent | CT | Key Alias | Config Status | Key Verified |
|-------|-----|-----------|---------------|-------------|
| Tanko | 112 | tanko-v2 | ⚠️ Hardcoded (correct key, no api_key_env) | ✅ 200 |
| Mumuni | 114 | mumuni-v3 | ✅ Clean (api_key_env) | ✅ 200 |
| Koby | 111 | koby-v3 | ✅ Clean (11 fixes applied) | ✅ 200 |
| Koonimo | 113 | koonimo-v2 | ✅ Clean (3 fixes applied) | ✅ 200 |
| Abiba | 100 | abiba | ✅ pi native | ✅ 200 |
| Kagenz0 | 105 | kagenz0-v2 | ❌ DOWN (no hermes, no config) | — |
### Fix summary (2026-07-03 second pass)
**Koby (11 fixes):**
- 7 auxiliary sections: model:auto → model:syslog-auto (compression, flush_memories, mcp, session_search, skills_hub, vision, web_extract)
- custom_providers.harness: deprecated sk-syslog-koby → api_key_env, model:auto → syslog-auto
- delegation: model:auto → syslog-auto, deprecated sk-syslog-koby → api_key_env
**Mumuni (1 fix):**
- delegation: model:auto → syslog-auto + provider:harness + api_key_env
**Koonimo (3 fixes, first pass):**
- auxiliary.approval: model:auto → syslog-auto, provider:auto → harness
- auxiliary.skills_hub: model:auto → syslog-auto, provider:auto → harness
- custom_providers.harness: hardcoded koonimo-v3 → api_key_env
**Tanko (flagged, not urgent):**
- Config has hardcoded tanko-v2 key (correct) instead of api_key_env
- DeepSeek fallback key (sk-b7d9...) is intentional — external service
- Will need fix before next key rotation
### Mumuni sub-agent profiles (6)
Sub-agents in `/root/.hermes/profiles/<name>/config.yaml`: