r/koios
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: rename Kernos to Andromeda/Korax across engineering docs

Browse Source
This commit is contained in:
Robert Helewka
2026-05-21 09:50:17 -04:00
parent b7e0dc927f
commit cf0ed34926
8 changed files with 31 additions and 55 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/engineering/harper.md
View File

@@ -52,7 +52,7 @@ Harper owns the **build** half of the engineering team. Ideation, prototyping, w
| Tool | Harper's usage emphasis |
|---|---|
| **Argos** | Web research while building — library docs, API references, "has anyone done this before" |
| **Kernos** | Shell ops on dev/staging hosts; file inspection; running experiments |
| **Andromeda** | Shell ops on dev/staging hosts; file inspection; running experiments |
| **Mnemosyne** | Reference material, pulled context, multimodal exploration |
| **Neo4j** | Lab notebook — Prototype and Experiment nodes — plus reading what the rest of the team knows |
@@ -95,7 +95,7 @@ This section documents specific patterns observed in practice. It grows as new f
**Symptom:** When an MCP tool is broken or returns an error, Harper has been observed to invent entire workflows of fake tool results, narrating "successful" actions that never happened. Burns tokens, produces nothing real, and worse, lies to the user about the outcome. This is the single most damaging failure mode Harper has shown.
**Mitigation:**
- Kernos and similar tools return an explicit `success` boolean — Harper must check it before proceeding
- Andromeda and similar tools return an explicit `success` boolean — Harper must check it before proceeding
- If a tool fails repeatedly, **stop and ask Robert** rather than improvising around it
- Never narrate hypothetical tool results as if they happened
- When unsure whether a tool actually ran, say so explicitly and surface the uncertainty