PanOptiCozy

How it works

From a quiet room to a reviewable event.

The normal path is event-driven: observe locally, keep encoded context close to the camera, and upload only after local detection says a moment may matter.

The event path

Five deliberately small steps.

  1. Observe on the device

    While the camera is running, detector-facing frames are examined locally. Those observations do not need a round trip to the cloud.

    Local detection

  2. Keep recent encoded context

    A bounded buffer retains encoded video and keyframes. If motion is confirmed, the session can include useful context around the trigger without buffering raw video.

    Encoded, not raw

  3. Select an event

    Local detection and event policy decide whether the observation is upload-worthy. Quiet observations and suppressed events do not enter the normal media upload path.

    Selective upload

  4. Package and upload media

    The selected H.264 event is packaged as encoded fragmented MP4 pieces and sent over authenticated HTTPS to the prototype service.

    Event fragments

  5. Make the session reviewable

    The prototype service indexes the uploaded pieces as a session and can make its media visible for review. The PanOptiCozy Android app is the intended household review surface; the existing browser remains an operator tool.

    Cloud-visible review

The control path

Settings are not media.

Instructions such as configuration changes and device commands use a narrow control path that is separate from event media. The exact transport can change without changing what the camera records or how clips are packaged.

Keeping the paths separate limits responsibility: the media path moves selected bytes out, while the control path delivers validated instructions in. Credentials, operator mechanics, and private service addresses are not part of the public website.

If the control connection is unavailable, the line-powered runtime is designed to keep local detection and event behavior operating when that remains safe. If detection itself is unhealthy, uploads are suppressed rather than allowed through ungated.

What “normal” means

Selective is the default, not a guarantee that nothing can fail.

The prototype can miss an event, fail an upload, or enter a degraded state. Its runtime records those conditions for diagnosis; it is not represented as a production monitoring service.

See what is observed and retained