radio-moe v0.3.1 — Cognitum Spaces

radio-moe 0.3.1 — Cognitum Spaces integration

This release checkpoints the Autogenous adapter that turns authorized Cognitum Spaces state into bounded, derived radio-moe observations.

Included

• Strict HTTPS client for the legacy Space-twin route and all eight versioned spatial collections.
• RuView OAuth bearer support and rotating COGNITUM_SPACES_API compatibility-key support.
• Typed pagination with opaque, collection-bound cursors and explicit workspace UUIDs for API-key reads.
• Recursive rejection of raw sensing fields and enforcement of P2/P3, anonymous entity, hierarchy, timestamp, confidence, event, alert, and response-size contracts.
• spacesEnvelopeToObservation and spatialResourceToObservation mappings with derived lineage, provenance, expiry, tenant, message, and sequence preservation.
• Detailed Cognitum Spaces user guide and final ADR-402 production evidence.

Published artifact

radio-moe@0.3.1 is published on npm with provenance. The release workflow installed, type-checked, tested, audited, packed, installed, and smoke-tested the exact tarball before publication:

https://github.com/ruvnet/autogenous/actions/runs/32287166991

Changes and architecture

• Initial integration: #7
• Provenance hardening: #8
• Final release/OAuth evidence: #9
• Design of record: ADR-402

Boundaries

The adapter is read-only. It cannot publish spatial state, approve policy, pair devices, command actuators, or convert cloud recollection into sensing authority. MQTT federation, real-hardware accuracy, and long-duration operational claims remain outside this release's evidence.