The team system
Sessions, a console, and a queue that survives a restart. Some of this exists in a private build that is not merged and not offered as a service.
Product
Fareeq AI arranges work the way a company with named owners is arranged: roles, authority, a budget, approvals, and a record. The screens and channels are written down. The service you would buy, and hand your keys to, is not on offer.
The web console comes first. WhatsApp, email, voice, and mobile are written down. The work runs on the server, not on the phone.
The assistant does what is inside its limit, hands the work to the specialist who owns it, or raises a decision card.
The model writes. Before a sentence is proposed, it is set against the company record.
The action list is fixed: risk, effect, who executes, who checks. The suggested text does not choose the risk.
An official API first, then an authorized browser, then a person’s hand. Nothing publishes in silence.
If the tool contradicts the request, the claim falls. Anything above low risk needs an independent check.
A chain of trace, an outcome, and a cost. A certificate is earned for a skill and a risk, and withdrawn in the same record.
Sessions, a console, and a queue that survives a restart. Some of this exists in a private build that is not merged and not offered as a service.
Each fact has a source, a date, and a confidence, and a fixed precedence. A sentence in chat does not become a company fact because it was said.
Tasks, approvals, handoffs, a human takeover, and a work feed. The morning routine and others are written to the company’s clock.
A policy engine, an action list, and a guardian for instructions hidden in files and pages. The guardian is written. It is not proved.
The result is matched, then a chain we want signed and exportable. Loose text files are not the standard.
A ceiling that covers model, browser, and media. At the ceiling the work pauses and a decision card appears. Allowance numbers are not measured.
An isolated computer and browser for each worker. Secrets are not meant to reach the model. A person can take the desk.
The technical modes are said in three sentences an owner can use. No mode means: do as you like.
The first surface in the description. The interface is not wired to a live service.
Follow-up, approval, and stop. The app is not published, and the work does not run on the device.
Inbound channels are written down. No inbox is connected.
A short Arabic morning brief, and a spoken instruction that becomes a task. A voice provider is not chosen.
Names of desks, not product pictures. None of them opens.