How it works
Four beats + a gate. Same loop as the Iris soft-body milestone (body/v0.4).
1. See
Iris takes a screen observation—pixels plus UI elements (icons, windows, focus)—and builds an observation_packet.
2. Plan
A planner picks a soft tool: e.g. find-and-click a dock icon, type in a focused window, or open an app on the owned desktop.
3. Predict & gate
Before anything irreversible, a predict step scores success / harm / uncertainty. SafetyGate admits or denies. Denied acts don’t run.
4. Act & remember
On admit, Iris performs the OS action (or dry-runs it in early demos) and writes a trace to memory so the next step isn’t amnesia.
vision → observation → planner → predict → SafetyGate → act → memory
Soft-loop demo (owned box)
A short run of Iris on our controlled desktop: open an app path, read what’s on screen, take one gated action, show the memory/trace. Early public demos use dry-run acts (no silent live click) unless an owned-machine live cue is shown.
Optional affect / interoception logging may appear on the trace as soft suggestions only (confirm_more / slow_down / escalate). Those flags do not override SafetyGate or claim live autonomy.
Demo recording placeholder
Record per DEMO-SCRIPT.md on the owned box. Embed unlisted video or local MP4 here later.
Prefer text? See the demo script in the Iris public pack (DEMO-SCRIPT.md) and run locally:
cd soft-loop-demo python3 soft_loop_demo.py python3 soft_loop_demo.py --abort
Get early access notes
Builders, agent hackers, and the curious—join the list. We’ll send the demo, the owned-machine policy, and invite-only experiments. No spam; unsubscribe anytime. No promised ship date.
FAQ
Is Iris another AI browser agent?
No. Browser agents live in a tab. Iris is a software body: full-screen vision, OS-level actions, memory across steps, and a planner—with a SafetyGate before acts.
Will it control my computer from this website?
No. This page is a landing + waitlist. Iris demos run on systems we control (or later, machines you explicitly run the body on). We do not claim remote control of visitor PCs.
What’s a SafetyGate?
A check that admits or denies an action using predicted harm, uncertainty, and reversibility (and related body/v0.4 rules). If denied, the act doesn’t run. Early public demos may show dry-run acts plus traces.
What about affect / “mood” logging?
Optional v0 stubs can log affect and machine-body pressure as soft suggestions on the demo trace. They do not bypass SafetyGate, do not issue live acts, and are not a claim of felt emotion.
Is this malware / a RAT / “undetectable automation”?
No. We don’t frame Iris that way. It’s an honest embodiment stack for builders: observe, plan, gate, act, remember—on owned systems.
Is the physical robot part of this?
No. Iris here is the software body lane. Physical embodiment (Soma) is a separate track and isn’t what this waitlist is for.
Can I use Iris on other people’s systems without permission?
No. Unauthorized access is out of scope and against how we demo. Owned / authorized machines only.
When do I get access?
When we open a cohort. Waitlist gets the recorded demo first, then invite notes. No promised ship date on this page.