Skip to main content

Module fleet_inventory

Module fleet_inventory 

Source
Expand description

Read-only inventory of Cognitum cloud-registered Seeds (card mesh-placement-23; fleet-compat.md sections 1b, 2(b2)).

Calls the Cognitum cloud MCP’s fleet_status tool and lists the Seeds as candidates for node binding (super::seed_bind). It never places, configures or registers anything through the cloud: every call passes ReadOnlyFleet, which refuses any tool outside READ_TOOLS before it reaches the transport. The OAuth token lives in the operator secret store behind super::fleet_mcp::OAuthTokens; it is only ever placed in an Authorization header and never appears in a chain event, error or log.

The parser accepts the output of fleet_status in the shapes its schema is expected to take (see fixtures/cognitum_fleet_status.json, an assumed shape until the owner captures the real one) and skips, never guesses at, an entry without a device id.

Structs§

FleetCandidate
A cloud-registered Seed, proposed as a node-binding candidate.
FleetInventory
The read-only inventory adapter.
ReadOnlyFleet
Wraps a transport so only READ_TOOLS can ever be called.

Enums§

FleetCheck
What the local-versus-cloud key comparison found.
FleetError
Why an inventory call failed.

Constants§

EVENT_KIND_FLEET_INVENTORY
Chain kind of an inventory read.
INVENTORY_CHAIN_SOURCE
Chain source of inventory events.
MAX_DEVICES
Most devices accepted from one reply.
READ_TOOLS
The only MCP tools this adapter may call: reads.

Traits§

FleetMcp
One MCP tool call transport.

Functions§

parse_fleet_status
Parse a fleet_status output into candidates; the second value counts entries skipped for lacking a device id.