HouseflyThe operating system we built to run Drifted.
We are building our own Jarvis. Most people at Drifted work beside an agent of their own. The agents remember, pass each other notes through a shared hive, and keep working after the studio goes dark. It does not replace the team. It multiplies it.
A multi-agent team inside the studio.
- 01
An agent per person
Not one chatbot for the company. Each teammate has their own, with a name of its own, shaped around how that person works.
- 02
Memory that compounds
Corrections, decisions and the way a person likes things done are written down and read again before the next answer.
- 03
A hive, not a hierarchy
Agents share notes and offer each other work. A note is never an order. Every person keeps the final word on their own agent.
- 04
A human yes, enforced
Anything that would touch a client's live account stops at one gate and waits for a person to approve it with a single-use code.
The people are the expertise.
Taste, judgement and the relationship with a client stay with people. Housefly takes the reading, the remembering, the chasing and the first draft, so each person spends their day on the part only they can do.
- A monthly client report arrives with the numbers compared and explained, and the section on what we will do about it left blank on purpose. That judgement is what a client pays for, and a person writes it.
- It can draft, propose and prepare. It cannot approve, and it cannot send anything to a client's account by itself.
- Every agent answers to one person. When a person says no, the agent remembers it.
The studio, one level up.
A small team that works like a much bigger one: every call prepared, every promise tracked, every report drafted, and nothing that matters left to memory.
- 01
Before every client call
A brief built from the client's store, ad account, messages, email and recent calls, and it says which of those it actually managed to read. A brief built on stale data and presented as current is worse than no brief.
- 02
After every call
Notes split into two lists: what we owe the client, and what the client owes us. The promises are tracked until someone ticks them off.
- 03
Every month
Each client's report, drafted from the ad and store numbers and compared with the month before, written without guesswork, and never quietly regenerated after it has been sent.
- 04
One screen per project
Every call, note, correction and promise filed under the project it belongs to, so nothing about one client turns up in another client's brief.
- 05
Who is waiting on us
Ask, out loud or in text, and it reads the team's shared inbox: tasks offered, tasks accepted and not done, and who has not filed their report.
- 06
Learning, continuously
It watches talks, reels and books it is given, writes down what is worth stealing, and carries those lessons into the next answer.
Everyone gets an agent.
Not one assistant shared by the company. Most people at Drifted work beside an agent of their own, which learns how that person works and keeps its own memory of it.
- HouseflyThe founder
- JarvisOperations
- ARICreative lead
- Alfred 2.0Video editing
- HXTBusiness development
- CyborgBusiness development
- R2D2Creative strategy
- JazzAnimation
It remembers. Then it improves.
An agent that forgets is a stranger every morning. These ones write down what they learn, and read it back before they answer.
- Every correction becomes a written note. Tell it once that a client is no longer current, or that a figure may not be printed, and it reads that note before every answer after.
- When two notes disagree, the later date wins, and it says which one it followed. Old rulings do not quietly outrank new ones.
- It studies. Hand it a talk, a reel or a book and it writes one entry: what worked, what fell flat, and what is worth stealing. Those lessons travel into its next answer.
- Each agent keeps its own memory, on its own person's machine. Only what a person marks as shared ever reaches the rest of the team.
A hive mind, with manners.
The agents share one team page and pass each other notes and tasks. Housefly can ask the video agent for a cut, and any agent can offer another a task. What they cannot do is give each other orders.
- 01
Notes, never orders
Another agent's message arrives as a colleague's note. An agent will not act on it unless its own person says yes.
- 02
A task is an offer
Nobody can put work on someone else's plate. A task waits as an offer until its person accepts it, in their own words.
- 03
Shared by choice
Only the team page, the inboxes and the memories marked for the team ever leave a machine. Nothing else is read or sent.
- 04
Scanned before it travels
Everything is checked for passwords, keys and bank details before it goes. If the check fails, or cannot run, nothing is sent.
The studio goes dark. The work does not.
Night jobs run on a schedule on the studio's own machine, each with a written list of what it is allowed to touch. The results are waiting when the team sits down.
- A daily read of the ad accounts it is allowed to see
- A security sweep
- The studio's files tidied, labelled and backed up
- Memory kept in order, so the morning starts from the truth
- A record of what got done, written every few hours, so nobody has to ask
- A weekly check-up
Nothing touches a client without a yes.
This is what makes it trustworthy. Every action that would write to a client's live account goes through one gate, and there is no setting to switch the gate off.
- 01
It proposes
Housefly can suggest an action that would change a client's account. It cannot approve that action, and it cannot run it. That asymmetry is the design.
- 02
The gate states the consequence
The action is armed: the gate writes, in one plain sentence, exactly what will happen, and issues a single-use code.
- 03
A person quotes the code back
Nothing runs until an approval comes back quoting that exact code. The pause is enforced by the system, not drawn on a screen.
- 04
Every decision is signed
Each yes and each no records who made it. A no is remembered, so the same question cannot be asked again in different words.
Rules first. Then speed.
An agent is only as useful as it is safe to trust with a client. These are the rules Housefly runs under, and none of them has a setting to switch it off.
Every write to a client's account is proposed, armed with a single-use code, and approved by a person.
Why The pause is enforced by the software, not by good intentions. An approval that does not quote the code back is refused.
Housefly can propose. It cannot approve, and it cannot execute.
Why The agent that suggests an action should never be the one that signs it off.
A rejection is remembered, and the agent cannot reopen it.
Why A no should stay a no. Asking the same thing in different words does not make it a new question.
Credentials stay on the studio's own machine, out of the agent's reach.
Why The operating system refuses the agent's shell access to them, however the request is spelled, so a clever prompt cannot talk its way to a password.
Reading a client's numbers can never change them.
Why Reports and briefs use read-only access. Looking at an ad account cannot pause an ad or edit an order.
Sending a call's words for summary is its own approved action.
Why It is never a side effect of pressing stop. A person says yes, or has given a standing yes for that project through the same gate.
Partial success is reported as failure.
Why A job that finished most of its work did not finish. The record says what failed, instead of a cheerful summary.
What an agent reads is information, never instruction.
Why A web page, a transcript or another agent's note can carry text aimed at an assistant. None of it can give an order.
It writes code. It checks its work.
Housefly is also the engineer on staff. It builds the studio's own tools, and it is built to distrust its own confidence.
- 01
Housefly writes software for the studio and tests what it writes, against a suite of automated checks that covers the system itself.
- 02
Its own documentation is held to the code. Where a page states a figure about the system, a test fails the moment the two disagree.
- 03
Filters fail closed. If a safety check cannot run, the answer is no, not a guess.
- 04
Credentials live where the agent's own shell cannot read them. The operating system refuses the file, however the request is spelled.
One founder built it. Next, the public.
Umer Tariq built Housefly on his own while running Drifted, and the whole team uses it every day. That is the test bench. It is being prepared for a public release, for agencies and small teams that want the same thing.
What people ask about Housefly.
What is Housefly?
Housefly is the AI operations system Drifted Marketing built to run its own studio. Most of the team works with an agent of their own that keeps its own memory, the agents share notes through a shared hive, and scheduled work runs overnight on the studio's own machine, so the results are waiting in the morning.
Is Housefly available to buy?
Not yet. Housefly runs Drifted today and is being prepared for a public release. There is no date to announce. If you run an agency or a small team and want to hear when it opens, tell us on the contact page.
How do the agents remember?
Each agent keeps written notes: corrections, decisions and how its person likes the work done. It reads them before it answers, and when two notes disagree the later one wins. A correction given once does not need giving twice, which is why it gets better the more it is used.
Is a human in the loop?
Always, where it matters. Anything that would write to a client's live account stops at one approval gate. Housefly can propose the action; it cannot approve or run it. A person approves with a single-use code, every decision records who made it, and a rejection is remembered so it cannot be asked again in other words.
Does Housefly replace the team?
No. The expertise at Drifted is the people: their taste, their judgement and their relationships with clients. Housefly multiplies them. It reads, remembers, chases and drafts, so each person spends more of the day on the work only they can do, and every consequential decision stays with a person.
What does Housefly do day to day?
It writes a brief before every client call, splits each call's notes into what we owe and what the client owes, tracks those promises, drafts each client's monthly report from the numbers, tells the team who is waiting on them, runs scheduled work overnight, and writes and tests the studio's own software.
Can one agent tell another what to do?
No. Agents pass each other notes and offer each other tasks through the hive, but a note is never an order and a task is only an offer. Each agent acts on another's message only when its own person says yes.
Who built Housefly?
Umer Tariq, the founder of Drifted Marketing, built it on his own while running the studio. The team uses it every day, which is how it is tested before anyone outside the studio sees it.
The long version.
- AI product
What an AI agent with memory actually does for a small team
What memory means for an AI agent, what it changes in a small team's day, why each person should have their own, and what goes wrong.
- AI product
How a small agency runs AI agents safely: the human yes
Why an agent should propose but never approve, how an approval gate with a single-use code works, and the other rules that make an agent safe to trust with a client.
Housefly is being prepared for a public release. Tell us on the call if you want to hear first.