RuView: Locking Down Cognitum Spaces Access
RuView shipped a new Cognitum Spaces integration with strict, layered access controls, then documented the production rollout with evidence in an architecture decision record. The through-line: read-only access, one fixed endpoint, and no credential shortcuts.
Duration: PT2M28S
Episode overview
This episode is a short developer briefing from RuView.
It explains recent repository work in plain language.
- Show: RuView
- Published: 2026-08-19T06:05:04Z
- Audio duration: PT2M28S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good day, I'm your host with RuView, it's August 19th, 2026.
The top story tonight: RuView opened a door to Cognitum Spaces, and then spent real engineering effort making sure that door only opens one narrow way.
Start with PR 1631. It introduces explicit consent for read-only Spaces access, a bounded Rust client, and a command line surface. Critically, it enforces a strict boundary at the HomeCore Edge, recursively rejecting raw sensor data, recordings, pose frames, vital waveforms, and identity observations. This isn't a…
That backstop gets reinforced in PR 1644. This change adds a spaces list tool and delegates all OAuth refresh and decoding to the existing wifi-densepose client, rather than building a second path. More importantly, it closes off several possible attack surfaces at once: no bearer tokens, no caller-supplied API…
The third piece, PR 1639, is documentation, but it matters. It records the production release chain for Spaces, the gateway, and Identity, and captures sanitized OAuth evidence. It also makes explicit which milestones are still unimplemented, including deferred hierarchy and memory work. Commit 2c249ec links those…
The pattern across all three: this team…