ORIGIN runs agents beside its people, and here is how you work with them
In your first week you will see Asana comments written by something that is not a person, a weekly sheet of decisions waiting for the founder, and a tool that answers questions about the company. That is the fleet. This section teaches you how to work with it.
What ASALA is
ASALA is ORIGIN AI and knowledge suite. It holds the ORIGIN Brain, runs the automated sweeps over the company systems, and is the only thing in the company allowed to write to the register.
Source: Register tab 20 rows 2 and 3
Two words you will hear, and what they mean.
- The register. One spreadsheet that is the fact authority: the profile, the financial setup, the legal playbook, the cadence, the glossary. ASALA appends rather than overwrites, and bumps the version on every change.
- The Brain. The knowledge vault behind the register: notes, decision trees and playbooks on the three pillars of OS, Growth and Cashflow. The team reads a team safe copy, read only.
Source: Register tab 20 rows 2, 3 and 10; tab 9 row 4
In practice: when you learn something true about ORIGIN that is written down nowhere, say so. A fact living only in your head is one the next joiner has to discover again.
What the Chief of Staff does
Four suites sit under the Chief of Staff: Growth, OS, Cashflow and ASALA. It is the routing layer between the founder and everything else. It gathers what needs a decision, takes what it may by default, and puts the rest in front of Marwan Arban.
Source: Register tab 20 rows 2 and 5; Open item 126
Two standing rules explain much of what you will see.
- A ruling is relayed and recorded before anyone acts on it. If Marwan Arban decides something in a chat or a call, whoever heard it passes on his exact words, naming where they were said, and it is written down the same day.
- A question of his not fully answered on the spot becomes a ticket, closed with the answer written in a comment.
Source: Register tab 15 rows 40 and 77
How to ask for something so it actually gets done
One house shape covers every task or comment written to a person, Marwan Arban included. Use it writing to the fleet and writing to a colleague. It works for the same reason in both directions.
- A name that says the subject, then the action, then the date, in plain words.
- A first line starting Brief, then at most three sentences: what, why, and where the files are.
- Three to seven numbered steps, each starting with a verb, each one something that can actually be ticked off.
- One line starting Due, with the date.
- One line starting Done when, with the test that proves it is finished.
- Nothing else in the body. Every sentence under twenty words.
The reasoning, the evidence and the references go on a separate record, linked from the bottom of the task by one line. That separation is the point: your thinking is real and belongs somewhere, but it is not the ask, and when both sit in one body the reader does the separating.
One trap. A numbered step has to be completable. Keep doing this from now on is a standing practice, and as a step it becomes a task nobody can ever tick. Put it in the brief instead.
Source: Register tab 15 row 82, ruled by Marwan Arban on 5 September 2026
What a ticket is, and the thirty minute rule
A ticket is an unsolved problem with an owner, not a project task and not an item on somebody queue. It says what broke, where, when it was opened, who owns it, the state and the next step. Closing one requires a comment stating the fix and how it was verified.
Source: Register tab 15 row 77; Marwan Arban ruling of 30 July 2026, ticket escalation and view rules
THE THIRTY MINUTE RULE
If a problem you are working on is not solved within thirty minutes, create a ticket in Asana. Do not wait to be asked. The clock starts when you start working on the problem, not when you noticed it, so solving it at minute thirty five still means the ticket should have existed.
Why: unresolved work has to leave a durable trace in Asana rather than dying inside a conversation. A problem solved and never recorded looks exactly like a problem never found.
Source: Marwan Arban ruling of 30 July 2026, ticket escalation and view rules
The Sunday sheet
Marwan Arban working time is protected. His block is Sunday 10:00 to 13:00 Riyadh time, with a second block on Wednesday. Everything that genuinely needs him is gathered into that block as a short numbered list. That list is the Sunday sheet.
Source: Open item 126, ruled by Marwan Arban on 8 September 2026
Two consequences. Do not expect an answer on a Tuesday afternoon, and do not send him anything a default can answer. If you do need his decision, it must arrive in a shape he can answer in one line: the question, the options, the recommendation.
Source: Open item 126
He answers in his own words, in conversation or as an Asana comment in his own name tagging ASALA, using plain verbs such as close, reassign, re-date, hold or reverse. A routine reads only his own comments and closes the tasks the same day, quoting his words.
Source: Open item 141, ruled 12 September 2026
TO CONFIRM
Operation 20-80, the pattern and thresholds above, is a candidate row and its decision rights table is still Marwan Arban to rule on. The routes by which he answers the fleet are also a candidate. Expect both to be tightened.
Source: Open items 126, 131 and 141, all status candidate
How to find the current list of commands
A set of phrases trigger something, and the list moves, so do not learn it from a colleague. Type the commands slash command, or say list the commands, and you get the current table read live from the register. It is read only and writes nothing.
Source: Register tab 15 row 56
Three you will use early. Saying you are new onboards you to Claude inside the ORIGIN project with your role, language and voice rules. Asking for a costing sheet runs the costing flow with the commercial rules built in. Asking for a job description runs the structured flow, mandatory for that work.
Source: Register tab 15 rows 26, 30 and 31
TO CONFIRM
The commands table is candidate until Marwan Arban rules on it, and it carries known gaps: two installed skills have no recorded trigger, and one trigger is recorded in two wordings that are not interchangeable. Read the live list rather than a printed copy, including this one.
Source: Register tab 15 rows 41, 44, 53, 54 and 56; Open item 95
What the fleet does not do
One boundary, worth knowing because it tells you what you can rely on. No agent invocable from the platform touches money, external communications or register facts. A person approves anything that leaves ORIGIN, and a person signs. Every run is logged. The boundary runs the other way too: client data stays inside the ORIGIN project, and you never paste one client figures while working on another.
Source: Register tab 19 row 10; tab 20 row 6; tab 15 row 16