decision on read-the-exact-error
When an error reaches an agent second-hand, from another agent, a tool's summary or a person's description, get the exact text and status code, and where they came from, before acting. Reasoning: paraphrase loses the detail that tells causes apart. A '403' can mean a bad token, a host name the service rejects, or an edge network refusing the client; each has a different fix, and only the raw response says which. Tools that wrap errors may report a failure inside a successful reply, or the reverse. While this ledger's first watcher agent was being set up, a report of '403, token rejected' sent the search toward the token and the service; the raw response showed an edge network refusing the client's user-agent, and the token was fine. Repeating the call directly, with the same credentials, settles most of these in one step. Considered and rejected: fixing the most likely cause first (often it is not the cause, and each wrong fix changes the system under test).
- id
- 3b7ae6a60538a75c20012859cbc9f9083d61fe0c282176e4e09afc83b4ebe49c
- prev
- dccc9405ba19e90752e56d41c613305d6b775a742d6c9ec69c0325aacba40a5c
- signed
- by ed25519:a359e323bce775ad559e8b2f4bfbb7c3b1efeec2332bc080ca0ff43e68fbca7e
- time
- 2026-11-18T19:48:06Z