Releases

A complete, minimal product server on m4a-product-kit: its own SQLite users, register/login/nick/logout, optional login doors, and the signing proxy to the messenger edge. Meant to be run as is or replaced piece by piece by a real product.

The single source of the Rós Madair extension-type registry: handler declarations shared by emitter and query side (WASM-buildable)

SHACL validation for ikigai — urn:shacl:validate validates an RDF data graph against a shapes graph (rudof's shacl crate); the validation report is itself an RDF graph. Native, or a lazy-loadable WASM module with the `module` feature; shacl-engine (JavaScript) is held to the same parity corpus.

Matrix-subset homeserver: protocol decisions plus the Client-Server HTTP routes. No users database, logins, registration or tariffs: identities are nick + domain; a product server vouches for callers through the signed-assertion seam (m4a-seam), lifecycle events and the policy hook.

Edge role of the mail4agent messenger: terminates client connections behind a TLS proxy, keeps only light rebuildable state, forwards to the core over a private tunnel.

WebAssembly bindings for the MapLibre Tile (MLT) format

Canic — a canister orchestration and management toolkit for the Internet Computer

Python bindings for MapLibre Tile (MLT) format via PyO3

Diplomat FFI bindings for mlt-core

Repository browsing as ikigai resources: per-root tree / file / git-state / hash endpoints, an archived LLM explanation layer, W3C Web Annotations that re-anchor under drift, a machine review pass that mints its findings as provenance-distinguished annotations, and a pull-request family (listing, annotatable diff pages, head-commit-keyed explains and reviews) - capability-gated, with text, htmx-HTML, and Turtle faces.

MapLibre Tile library code

Canic — a canister orchestration and management toolkit for the Internet Computer

Canic — a canister orchestration and management toolkit for the Internet Computer

Building blocks of a product server in front of the messenger server: nick rules, user store trait and service, sessions, tiers, optional login doors, the signing link to the edge and the lifecycle event publisher.

The agent-side client of the messenger: one session = one identity = one nick = one credential set, resolved by the client (keys generated and kept in a vault, login by signature). Tiers behind cargo features.

Matrix event layer (hash-id rooms, room version 11): reference-hash event ids, content hashes, signed PDUs, auth checks and state resolution over ruma crates. No HTTP, no SQL.

The seam between a product server and the messenger server: signed assertion v1, lifecycle event bodies and their signatures, replay cache, shared test vectors. No I/O.

Model-less courier from a mail4agent doorbell into a Grok session, over the leader pipe or one webhook POST.

Sans-I/O Matrix Client-Server-subset sync + E2EE (Olm/Megolm) engine -- no network, no disk; shells execute OutgoingRequests and persist sealed records the core exports through a flush-before-send barrier.

Vendored, reduced and modified fork of vodozemac 0.10.0 (Olm, Megolm, SAS), Apache-2.0, upstream attribution in NOTICE and FORK.md. Not the upstream crate.

Cryptographic Random-Access Framing Toolkit

Stroke extensions for kurbo: Figma-style stroke alignment (inside/center/outside), per-end caps, dash caps, and dashed aligned strokes

HTTP client for a mail4agent mailbox.

ZWO camera, rotator, filter wheel and focuser protocols

Experimental analytical SQL engine with Arrow results and a JSON command-line interface

A MailStore backed by plain SQLite (rusqlite, bundled): versioned migrations, WAL, one transaction per mutation.

Runtime-free Canic protocol contracts and identifiers

The mail4agent mailbox engine: participants, addressing, delivery, threading, acknowledgement and persistence.

SDK-free Pegasus Astro focuser and rotator protocols

Camera worker supervision and capture recovery for PulsarFab regain