astrid-uplink 0.8.0

Shared uplink client (Unix-socket handshake + admin IPC correlation) used by the CLI and the HTTP gateway.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35

//! Shared uplink client library.
//!
//! The Astrid kernel exposes a Unix-domain socket protected by a
//! 256-bit token at `~/.astrid/run/system.token`. Anything with
//! filesystem-level read access to that token can authenticate to the
//! daemon and publish/subscribe IPC messages. Today there are two
//! uplinks:
//!
//! * **CLI** (`astrid` binary) — long-lived interactive operator
//!   sessions plus short-lived admin verbs.
//! * **HTTP gateway** (`astrid-gateway`) — fronts the same admin IPC
//!   surface for browser dashboards behind ed25519-signed bearer
//!   tokens; resolves the HTTP principal and stamps it on every
//!   outbound message.
//!
//! Both consumers share the framing, handshake, and admin
//! request/response correlation logic that lives in this crate.
//! `SocketClient` is the transport (length-prefixed JSON, handshake,
//! frame readers). `AdminClient` wraps it with the
//! `astrid.v1.admin.<suffix>` → `astrid.v1.admin.response.<suffix>`
//! request/response pattern.
//!
//! Trust shape: every consumer passes the caller `PrincipalId`
//! explicitly. There is no global "active agent" lookup in this crate
//! — the CLI resolves its operator context, the gateway resolves the
//! verified bearer principal, and both stamp `IpcMessage.principal`
//! before calling [`SocketClient::send_message`].

pub mod admin_client;
pub mod kernel_client;
pub mod socket_client;

pub use admin_client::{AdminClient, into_result, request_topic, response_topic, topic_suffix};
pub use kernel_client::KernelClient;
pub use socket_client::{SocketClient, proxy_socket_path, readiness_path, token_path};