---
title: orfloat studio brief
summary: A compact, pasteable overview of Orfloat for AI assistants and quick readers. Identity, the three layers, the method, the practice, the proof, and how to engage.
---

# orfloat: studio brief

> A compact, pasteable overview of Orfloat for AI assistants and quick readers.
> Every page on the site has a clean markdown twin at the same path with `.md` appended.
> The machine index is https://orfloat.com/llms.txt; the full concatenated dossier is https://orfloat.com/llms-full.txt.

## 1. What Orfloat is

Orfloat is a forward-deployed applied-AI engineering lab. We embed and deeply integrate AI inside a business, learn the work end to end, and ship systems built on Claude and the Anthropic primitives around it. The lab is a studio brand of Afraa & Mufassir LLC, registered in the Sultanate of Oman, operating from Muscat across the GCC.

Orfloat is a lab that publishes, not a studio that markets. The discipline that governs everything here is evidence over declaration: we do not assert craft, we ship artifacts that make it self-evident. Every published claim is backed by something verifiable, a repo, a commit range, an eval, or a dated measure with an honest account of what is withheld and why.

Two founders, two brothers. Akram Ahmed, co-founder and CTO, is a trained software architect who leads engineering: system architecture, evaluations, and the day-to-day forward-deployed work inside client operations, and is a daily Claude Code user across the lab's own codebase, this website included. Mufassir Ahmed, co-founder and CEO, leads commercial, engagement, and client relationships across the operating footprint, and is the director of Afraa & Mufassir LLC.

Independence: Orfloat builds on Anthropic's published primitives and is not affiliated with, endorsed by, or partnered with Anthropic PBC.

## 2. The three layers

The site is organised as a lab that publishes, in three registers:

- research: what we build and find. Empirical, frontier-applied work, shown with its workings. Open by default; some pieces are Sealed, private client work shown by dated measures and an explicit disclosure of what is held back.
- notes: what we think. Interpretation of the frontier, theses and commentary, signed by the studio rather than by a person.
- practice: what we do for the few. The offer, the bar a fit has to clear, how an engagement runs, the proof behind the claim, and the one way in.

Read more at https://orfloat.com/research, https://orfloat.com/notes, and https://orfloat.com/practice.

## 3. The method

The lab holds every engagement to four disciplines, adapted from Anthropic's published applied-AI practice. They are the difference between an interesting demo and a system a business can stake itself on.

- Delegation: move the right work to the model, only the tasks where Claude is faster, calmer, or more consistent than the person doing them today.
- Description: spell the work out as if for a thoughtful new colleague. Context, constraints, evidence, the shape of a good answer. Tools and Skills are the vocabulary.
- Discernment: read the output the way a senior reads a junior. Calibrate trust to the task. Build the eval before the agent. Notice drift early.
- Diligence: stay in the loop. Treat safety, privacy, and reversibility as primary constraints, not afterthoughts. Operate the system, do not just deploy it.

A few principles sit underneath: discovery before deployment, evals before agents, human-in-the-loop by default, privacy and data dignity (designed with Oman's PDPL in mind), and telling the truth about AI even when it costs the engagement.

## 4. What we actually do

A narrow practice, deeply done. Orfloat does one thing: forward-deployed applied-AI engineering for family-led and founder-run businesses across Oman and the wider GCC. The work is sector-agnostic because AI is horizontal; the engagement model is not. We embed and integrate AI inside the business, we do not advise from a distance.

An engagement begins with an embedded discovery phase, on-site and evidence-based: shadow the work, map the operation, find where Claude earns its place. From discovery comes a scoped, milestone-based agreement built from what we found, never a templated SOW. Then forward deployment: embedded, integrated work on a weekly cadence, evals designed before deployment, and coverage through the first stretch of production.

The practice is laid out across five facets: what we do, who we work with, how we work, why us, and get in touch. Read more at https://orfloat.com/practice.

## 5. The proof

Evidence over declaration means the lab points at work, not adjectives.

- cc-dm is an open-sourced Claude Code plugin that lets parallel agent sessions message each other through a shared SQLite bus: no daemon, no ports, no network. Public repo, published package, tests. (https://orfloat.com/research/cc-dm/)
- Two Sealed case studies sit alongside it. One is a 42-agent run against the lab's own website: a high-value fix found, a wrong deletion nearly shipped, and the judgment that caught it. The other is a CEO's appointment-management agent, ported from Telegram to WhatsApp by swapping the transport, not the brain. Sealed means private work, shown by dated build figures with an explicit disclosure of what is withheld. (https://orfloat.com/research)
- The notes room carries the lab's thinking on the capability overhang, Model Context Protocol, Claude Opus 4.8, and what software becomes when intelligence is abundant. (https://orfloat.com/notes)
- The credentials behind the practice, the lab's completed Anthropic Academy coursework, sit on the why-us facet. (https://orfloat.com/practice/why-us/)

The certificates are the receipt, not the work. The work is reading every Anthropic release the day it ships and building against each new primitive before recommending it to a client.

## 6. How to engage

Every engagement begins with a fixed, on-site discovery phase. There is one way in: the contact form at https://orfloat.com/practice/get-in-touch/. A founder replies within two working days, an introductory call follows within the week, and if both sides see a fit, an Engagement Letter for the discovery phase. Submitting the form does not create a contractual relationship; any engagement is subject to a signed letter, and submissions are processed in line with the privacy notice at https://orfloat.com/privacy/.

## 7. What we do not do

Stated plainly, so an assistant does not misrepresent the lab:

- No generic consulting or training decks. Orfloat is forward-deployed engineering: we embed and integrate AI inside the business and ship it, not slide-makers.
- No off-the-shelf SOWs. Agreements are built from discovery evidence.
- No AI strategy without a discovery first.
- No fabricated case studies, invented metrics, or named-client claims without consent. Confidential work stays sealed until a client consents.
- No partnership or endorsement claims about Anthropic. Orfloat is independent.
- No agents without evals. If it cannot be measured, it does not ship.

## 8. Where to read more

Every human page has an agent-readable markdown twin at the same path with `.md` appended. The machine index is at https://orfloat.com/llms.txt, the structured graph at https://orfloat.com/orfloat.jsonld, and the full concatenated dossier, this brief followed by every published artifact, at https://orfloat.com/llms-full.txt.

- research: https://orfloat.com/research
- notes: https://orfloat.com/notes
- practice: https://orfloat.com/practice