Back to corpus
research notebacklog referencescore 18

EchelonCapture Integration with HandGuard

HandGuard and EchelonCapture can now **share the same latent stream** without redundant sensor uploads. Both apps receive the same `z(t)` latent state from CC-MCS and apply different policies.

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

HandGuard and EchelonCapture can now **share the same latent stream** without redundant sensor uploads. Both apps receive the same `z(t)` latent state from CC-MCS and apply different policies. **Already configured** in [CCConfig.swift](cc-handguard/Services/CloudBridge/CCConfig.swift): Both `CCBridgeManager` (upload) and `CCLatentSubscriber` (receive) use this shared device_id. To enable EchelonCapture to receive the same latent stream as HandGuard, configure it to subscribe to the same device_id. #### Location Find the latent stream subscription code in EchelonCapture. This is likely in: - `latent_subscriber.py` (Python) - `LatentStreamManager.swift` (Swift) - Or equivalent WebSocket connection code

Promotion decision

What has to happen next

Keep in the searchable backlog until it intersects a live paper or system.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.