primer · adamo kernels

Four Adamo kernels, demystified.

Every idea in this repo picks one of four moves on Adamo. All four run from a phone: the Lovable sandbox exercises the SDK once at build time and writes a JSON proof; the deployed app renders that proof. The robot performance happens later at the showcase.

The sandbox protocol

The Lovable build sandbox runs this once. The phone never touches Python.

python -m pip install --no-cache-dir adamo
python scripts/adamo_smoke.py     # ADAMO_API_KEY is in the sandbox env
# writes public/adamo-smoke.json — the proof the phone renders

ADAMO_API_KEYAdd it via Lovable's secret prompt. It lives only in the sandbox process env. Never in .ts/.tsx code, never in import.meta.env, never in a server function.get one ↗

mobile authoring

Author

294 ideas use this

kernel

a phone-first authoring surface — touch sliders, tap pads, cue lists, timeline scrubbers — that composes a robot program as JSON. The Lovable sandbox validates the key with `scripts/adamo_smoke.py` at build time; the artifact is played back on the physical robot later by an operator

how it drives the UI

a single-column mobile UI with 44px+ tap targets and a thumb-reachable primary action — one tap edits a cue, one tap saves the take

EXAMPLE IDEAS

sandbox simulation

Simulate

250 ideas use this

kernel

a build-time Python script (`scripts/adamo_simulate.py`) that connects to Adamo from the Lovable sandbox, publishes the authored program on a `sim/<slug>` key, subscribes to the echo, and writes `public/adamo-take.json` — the mobile app renders that JSON so the participant sees the program roundtripped through Adamo without needing a robot

how it drives the UI

a page that shows the authored program alongside the sandbox-verified take: sample count, latency, ok/failed badge, and a re-run hint

EXAMPLE IDEAS

shareable artifact

Publish

206 ideas use this

kernel

a build-time Python script (`scripts/adamo_publish.py`) that validates every step of the authored artifact against the Adamo SDK, writes `public/adamo-publish.json`, and generates a shareable URL/QR so an operator with a robot can pick it up at the showcase

how it drives the UI

a mobile card that shows the verified artifact, a copy-URL button, and a QR code the operator scans at the venue

EXAMPLE IDEAS

sandbox-verified replay

Witness

250 ideas use this

kernel

a read-only surface fed by prior sandbox artifacts (`public/adamo-smoke.json`, `public/adamo-take.json`, `public/adamo-publish.json`) — the app is a timeline of verified moments, not a live control panel

how it drives the UI

a scrollable timeline of sandbox-verified events with timestamps, latency, and an inline JSON viewer for each take

EXAMPLE IDEAS