Module capability 

The capability manifest — what a device can do, stated honestly.

This is the vendor contract of the Janus family. A device declares each capability with a status and the crate that backs it, exactly the way the MATA OEM sidecar’s catalog does: an available capability must name its backing crate, a planned one must not. rusty_esp_mid signs the canonical encoding so the home computer’s catalog can trust it; the encoding is deterministic and needs neither serde nor alloc.

Wire tags are stable forever. Add variants; never rename one.

Structs

Declared

One line of a manifest: a capability, its status, and the crate behind it.

Manifest

A device’s capability manifest, over caller-owned declarations.

ParsedDeclared

One declaration read back from the wire (alloc).

ParsedManifest

A manifest read back from its canonical encoding: what a host holds after janus/rpc/1 answered Manifest, or a bridge after a neighbour sent its own. Owned, so it outlives the bytes it came from; encode reproduces those bytes exactly, which is what lets the signature be checked over what was parsed.

Enums

Capability

A thing a Janus device can do. Tags are the wire form.

Chip

The Espressif part the firmware runs on.

Status

How real a declared capability is. Copy the status; never upgrade it.

Constants

MAX_FIELD_LEN

Longest model or firmware field accepted, in bytes.