nosaint-connectarchitecture docs
Overview

The nosaint-connect ecosystem

The cloud side of the NS-C1, a connected vaporizer that only works for its verified adult owner: how devices, people, apps and AWS fit together.

  • Initial documentation

    The first version of the nosaint-connect architecture docs: how the ecosystem fits together, how data moves between devices and AWS, and the concepts behind locking and verification.

Outside services: Persona (ID, face and age check), Twilio (SMS), and AWS Device Location (cell towers to positions).

What the system does

Each NS-C1 has a cellular connection. It reports its position, draws, pods, charging and battery to AWS. A new device stays locked until its owner passes age verification on their phone. After that, the backend watches for two things:

  • A change of owner. The device starts spending its nights somewhere else. The owner is asked to verify again, and the device locks.
  • Use in a school zone during school hours. The device locks until it leaves the zone or the school window ends.

The rules that spot these situations are versioned models. The answer to “what happens next” is the trust ladder.

Suggested reading

The technical picture

How data moves and what runs where.

  1. From a device to AWS
  2. From AWS back to a device
  3. AWS architecture
  4. Key design decisions

The product picture

What owners experience and where the work stands.

  1. Real, virtual and simulated devices
  2. Owners and verification
  3. Trust ladder
  4. Project status

Start with the Glossary: a few words here have a precise meaning, like draw, virtual device, shadow and outbox.

Where things stand

Everything on these pages runs on the dev and staging stages. Production isn’t deployed yet, and real devices aren’t in the loop: a virtual device stands in for them. See Project status.