Owner, 2026-09-28: recall and ask_memory query Honcho from a session of any class, since Honcho stores no query and rift's models and telemetry stay on the owner's hosts; the assumption is written down, with what changes if rift's configuration does. A query holding a known-prefix secret is refused. ask_memory names at most two workspaces, both asked at once inside brokerd's wait. A session keeps the tools array it started with, so M5c-2 needs no new epoch. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2.2 KiB
2.2 KiB
Egress
Every outbound network call the project makes, at run time or in development. Nothing else is allowed.
| When | From | To | What |
|---|---|---|---|
| Development | cargo |
crates.io | Downloading the crates listed in docs/dependencies.md |
| Development | make verify-device, tools/check-m3a-device.sh |
straylight's llama-server |
Checks against the real model through a private inferproxy; the script also reads /slots with curl first |
| Development | make audit |
github.com/rustsec/advisory-db | The RustSec advisory database, fetched by cargo deny check advisories |
| Run time (M2a) | inferproxy |
the llama-server router on the host (straylight:11434) |
Every inference request loopd makes, forwarded byte for byte |
| Run time (M3b) | brokerd's egress proxy container, for one http_fetch call |
only the hosts the call's grant names, on port 443, at public addresses | The tool's HTTPS request, end to end; the proxy sees only the host name |
| Run time (M4a) | gatewayd |
the owner's Mattermost at https://straylight.scylla-hammerhead.ts.net (tailnet) |
REST calls and one WebSocket: the owner's messages in, Boxmaker's answers out. Mattermost stores messages unencrypted in its database; the server is the owner's |
| Run time (M5c) | memoryd, through roncho |
the owner's Honcho at [honcho] url (rift: http://rift.scylla-hammerhead.ts.net:8000, tailnet) |
Finished turns (the speaker's message and the final reply), conclusions mirroring trusted memory writes and untrusted notes, deletions of those conclusions; from M5c-2, searches and dialectic questions, from a session of any class (queries are not stored; see the M5c spec, section 8). Nothing written to it from a secret session or above private. Honcho runs its own models on the owner's hosts to derive conclusions (none on the fleet workspace); its server counts telemetry events but sends none (telemetry_events_emitted_total, 0 on 2026-09-27) |
| Development (M5c) | the design model, planning M5c-1 | rift's Honcho | Recording real responses for the tests' fake server, in the throwaway workspace boxmaker-plan-probe only, deleted afterwards |
The two run-time rows for M2a and M3b were missing until 2026-09-23; they were added with the M4a spec.