Research / proof of work
Long-form proof-of-work papers from orfloat.
Orfloat’s own WhatsApp assistant: a Claude Code session that answers a prospect’s questions, runs a booking conversation, and writes to the founders’ real calendar behind code gates, all through one number serving two roles. Sealed: a private preview shown by a recorded two-screen demo.
An internal research preview: a form-gated web page where a caller talks to a native speech-to-speech agent that answers questions about the studio, proposes real open slots from the founders' calendar, and books a meeting behind server-side code gates. Proven end to end from an iPhone on Omani mobile data, one day after its first demo failed on infrastructure and the stack was rebuilt overnight. Sealed: a private preview, shown by a recorded demo and its dated build figures.
A Claude Code session agent built to serve a marketing-agency principal and his prospective clients through one business number: it answers leads, books consultations, manages the principal's calendar in conversation, and the moment a booking lands it hands him a calendar link and a ready-to-review welcome draft. Built first on Telegram, then re-homed onto WhatsApp's Cloud API through a self-authored channel, brain unchanged. Sealed: a private client demo, shown by its dated build figures.
We pointed Claude Opus 4.8 and Claude Code's new dynamic workflows at the previous version of our own website: 42 agents, about 48 minutes, one production deploy. The workflow surfaced a genuinely high-value fix and then nearly fooled itself. The judgment that caught it is the whole point.
A Claude Code plugin that lets parallel agent sessions DM each other through a shared SQLite bus. No daemon, no ports, no network.
A research preview: niotebook is a free, MIT-licensed learning companion for CS50 students that collapses the lecture video, a real multi-language code editor and terminal, and an AI tutor into one synchronized canvas. Ask the tutor what the professor is explaining right now and it answers from the transcript at that exact timestamp, not from a guess. Every language runs in the browser behind its own isolation primitive, with no server and no remote code execution, and the learner's own API key is encrypted inside a boundary that never hands it back. Open: the repository is public, and its commit history, continuous integration, and test suite stand as the mark.