01
Knowledge
One authoritative project structure, a vault of stakeholders, teams and project summaries, and retrieval notebooks over the source documents. Context survives, not just files.
BarichellaBRAIN OS
The cognitive layer of a 24-year practice.
Paolo Barichella's Infinite Brain.
BRAIN OS is an agentic AI platform built on one body of work: Paolo Barichella's method for food design, hospitality concept creation and food service engineering. Developed and owned by Food Lifestyle Consulting QFZ LLC.
In development
Overview
BRAIN OS in motion.
What it is
A method made operational.
Twenty-four years of Food Design and Hospitality Concept Creation have been digitised: processes, decision criteria, technical standards, project archives, failures worth remembering. Paolo Barichella has transferred that know-how into BRAIN OS and used it to train a specialised network of AI agents.
The agents do not replace the designer — they work alongside him. Each one draws on an exclusive, secured Shared Agent Memory (SAM): a cognitive memory that keeps every project, standard and precedent available to every agent at once. What used to live in one head and forty archive boxes now answers a question in seconds.
The output is not text. It is project material — zoning studies, service flows, equipment specifications, format economics, concept documents — produced to the same standards the studio has always applied, and always reviewed by a human before it leaves the system.
Corporate & asset management
The value of the system is formally recognised and capitalised. The “Heritage” intangible assets transferred into the platform — know-how, expertise, IPR, goodwill, trade secrets and copyright — have been converted into digital tokens held by Food Lifestyle Consulting QFZ LLC, sole owner of the platform.
Architecture
Knowledge, reasoning, action.
BRAIN OS is not a chatbot with a good prompt. It is three planes that stay separate on purpose: what the practice knows, what reasons over it, and what actually does the work — with a human signature between the system and the client.
02
Reasoning
Thirty-one specialised agents — from operations and project management to legal, finance, creative direction and systems — plus two bridges that connect them to the wider toolset.
03
Action
The agents do not only advise. Automations, connected business tools and meeting capture turn a decision into a task, a document, a drawing or a brief that lands where the team already works.
04
Oversight
An agent never holds knowledge natively — it knows where to ask. Requests above a defined threshold pass a plan gate; low-confidence answers escalate to Paolo. Nothing reaches a client unsigned.
Inside the system
The Advisory Board of the Luminaries.
A scientific committee of the highest order — illustrious and multidisciplinary — permanently on call inside BRAIN OS. It gathers the thinking and the working method of forty-nine of the great masters of their disciplines — from Michael Porter to Henry Ford, from Pierre Bourdieu to Steve Jobs — across eleven domains, each distilled into a lens you can question.
What would he have done?
What would he have said?
How would he have thought it through?
What advice would he give me?
01
A lens, and a procedure
For every master, two artefacts: the lens — how he reasons, the questions he asks first, the criteria he weighs most, the anti-patterns he hunts, the cases where the lens should not be used, and his canonical sources — and an SOP that turns that method into numbered, applicable steps.
02
Each lens answers only from its own record
No lens speaks from the model's general memory. Summon Byron Sharp and what answers is his codified framework, not a vague notion of what someone in marketing might say. That single rule is the difference between an authentic distillation and a plausible caricature.
03
Chosen to disagree
Two or three lenses are convened precisely for their structural disagreement — Godin's vision against Sharp's evidence, Adrià's ambition against Marchesi's subtraction, Ford's standardisation against Jobs's product view. Each argues its position; the strategist then synthesises the debate and states the trade-offs.
04
Presets for recurring arguments
Some disagreements come round again and again, so they are kept ready as clusters: kitchen, front of house, positioning, menu and culture, industrialise versus artisanal, product versus evidence. One click convenes the right table.
05
Lenses, not oracles
The decision stays yours, and it gets recorded. Each saved decision feeds the committee's self-improvement loop, so the lenses sharpen against your real context — clients across Italy and Qatar, your constraints, your history: the one thing none of these masters ever had.
- Lenses
- 49
- Domains
- 11
- Convened per decision
- 2–3
Corporate strategy04
Richard Rumelt · Michael Porter · Clayton Christensen · Hamilton Helmer
Marketing04
Byron Sharp · Seth Godin · April Dunford · Philip Kotler
Professional hospitality06
Danny Meyer · Will Guidara · Ferran Adrià · Gualtiero Marchesi · Auguste Escoffier · Pellegrino Artusi
Design08
Renzo Piano · Dieter Rams · Don Norman · Ilse Crawford · Achille Castiglioni · Gae Aulenti · Jasper Morrison · Le Corbusier
Bioengineering04
Robert Langer · Frances Arnold · George Church · Jennifer Doudna
Food technology04
Harold McGee · Hervé This · Nathan Myhrvold · J. Kenji López-Alt
Sociology04
Pierre Bourdieu · Erving Goffman · Ray Oldenburg · Zygmunt Bauman
Anthropology04
Clifford Geertz · Mary Douglas · Claude Lévi-Strauss · Marc Augé
Anthropometrics04
Ernst Neufert · Henry Dreyfuss · Niels Diffrient · Stephen Pheasant
Ergonomics04
Étienne Grandjean · Alphonse Chapanis · James Reason · Erik Hollnagel
Production, operations & leadership03
Henry Ford · Sergio Marchionne · Steve Jobs
Source consultation · not a lens
Regulation is not a method. It is a document you cite.
Compliance is deliberately not one of the forty-nine lenses. A lens is a way of reasoning; a regulation is not something to reason your way around. So the rules sit in their own category — a body of roughly twenty-three official sources on professional kitchen design, queried directly by the committee and by CAD Studio.
It answers with the official reference, not a paraphrase: the clause, the standard, the code of practice. In an inspection an opinion is worth nothing and a reference is worth everything.
The corpus is assembled by a dedicated deep-research routine, which can be re-run for any new market: a different city, a different authority, the same discipline.
What the corpus covers
International
- Codex Alimentarius — general principles of food hygiene and the HACCP system
- EU Reg. 852/2004, used as the reference for the compliance score
Qatar
- Ministry of Public Health — Code of Practice for food establishments
- Ministry of Commerce and Industry — cloud kitchen requirements
- Law No. 8 of 1990 on the control of human food
Gulf
- SFDA — Saudi Food & Drug Authority regulations and technical guides
- Dubai Food Code
Engineering & services
- Public works MEP standards for water, drainage and services
- Ventilation, grease management and extraction requirements
Fire protection
- UL 300 — wet chemical suppression for commercial cooking equipment
- NFPA standards for kitchen ventilation and fire protection
Design practice
- FCSI foodservice design guidelines
- Dimensional and clearance standards for professional kitchens
Concept illustration. The figures named are historical references whose published method is used as a disciplinary lens inside an internal review protocol: none of them, nor their estates, are affiliated with, endorse or advise Paolo Barichella, Food Lifestyle Consulting QFZ LLC or BRAIN OS.
The surface
The Cockpit.
Everything above has one place where it is actually operated. Not a dashboard of charts — a working surface: the morning glance, the project hierarchy, the people, the agents, and the actions that follow from them.
- Specialised agents
- 31
- Bridges
- 2
- Stakeholders mapped
- 139
Home
The morning glance
Active projects and archive at a glance, the week's agenda, the relationships that need reconnecting — and operational gaps: any project missing a stakeholder, a notebook or a folder.
Projects
Client → programme → project
The whole hierarchy as a tree or a sortable table. Open one and a side panel gives its summary, budget, team with defined responsibilities, channels and open tasks.
Agents
One entity, several planes
Each agent exists at once as execution, as knowledge and as material. The Cockpit shows all of its incarnations in one card, so you always brief the same entity.
People
Stakeholders, network, radar
Relationship strength, an interactive graph of who holds several projects together, and three lenses: gaps, follow-ups gone quiet, and partnership openings between projects that share a stakeholder.
Meetings
Call to minutes to tasks
A notetaker joins the call and transcribes in Italian or English. One action turns the transcript into minutes — attendees, decisions, action items — and one click turns those into real tasks.
Portal
What the client sees
A private area reached with a personal link and a PIN, no account needed, showing only that client's own project folder — plus the team and modules working on it. Confidential folders are never exposed.
Project management
Five levels, one project.
Every client, venture or internal area is an entity; beneath it sit projects and sub-projects. The Project Management Engine keeps each of them in step across five levels that used to drift apart — held together by a permanent key, so nothing breaks when a folder is renamed.
Level 01 · Registry
The source of truth
Every node that matters has a short, permanent code bound to the ID of its folder, not to its name. Rename anything and every link holds. A code, once used, is never reused.
Level 02 · Archive
One mother folder per entity
A single folder for each client or venture, with the same structure everywhere: working materials, a curated selection for the notebooks, and a reserved area that is never indexed.
Level 03 · Knowledge
Notebooks on what matters
Retrieval runs over a curated selection, not over the whole archive: the latest version of each document, minutes and contracts always, fifteen to twenty-five sources per node.
Level 04 · Reasoning
One workspace per entity
The conversational memory sits at entity level and is fed with the same curated documents, so a question about any sub-project is answered with the history of the whole relationship.
Level 05 · Execution
Tasks receive, never define
Task lists carry the node's code and execute the structure above them. A list can no longer create a project by accident, and a service folder can never hold one.
Stakeholder management
One profile per person
Role, organisation, projects held, channels and relationship history in a single record — fed by meetings, e-mail and a business card scanned on site.
Responsibility
Who does what
Every project states its team with defined responsibilities, so the person accountable for a decision is never a guess.
Continuity
Nothing goes quiet
Stalled follow-ups, projects missing a stakeholder, relationships that need reconnecting — flagged before they turn into a problem.
Access
The right view for each
A stakeholder can be given a private portal with only their own project and only the modules they need. Nothing else is ever exposed.
The command chain is fixed: Paolo decides, the system orchestrates, the registry keeps the links, the archive keeps the files — and the interfaces show the state of a project, they never create it.
Modules
Kitchen Architect & CAD Studio.
The first vertical in operation: an app inside the system, covering the whole of professional kitchen design — from a floor plan or a sketch on paper to HACCP layout, services, quote and render.
Kitchen Architect is the agent: it holds the HACCP rules, the ergonomic standards and the real equipment dimensions, and it decides. CAD Studio is the design module that lives inside it — the part that draws, models, prices and renders, with the regulatory check built in rather than bolted on.
Founding principle
Nobody moves a mouse. Geometry is generated as code — parametric, in millimetres, repeatable. And the real plan is always the base: the landlord's drawing, or your own sketch. The envelope is never invented.
Receivinggoods in
Dry storageambient
Cold storagechilled · frozen
Preparationraw handling
Cookinghot line
Pass · dispatchplating
Washpot · dish
Wasteback of house
Step 01
Digitise the input
A floor plan as image or PDF, a vector drawing, or a hand sketch: the system reads the dimensions written on it, rebuilds the footprint and the rooms in metres, and seeds the layout. With no drawing at all, a guided brief — venue, covers, area, budget, style — starts it instead.
Step 02
Zone it, three ways
A deterministic engine places the zones and checks the things that matter — raw and cooked kept apart, forward flow, dishwashing away from clean areas — and scores the result. It returns up to three alternative layouts, not one opinion.
Step 03
Compare with numbers
The variants are measured against each other on density, HACCP flow and score. The choice between layouts is argued with figures, not taste.
Step 04
Take over in 2D
Zones and equipment can be dragged and resized on a 100 mm snap, equipment generated straight onto the plan, and the HACCP score recomputed on your arrangement rather than the machine's. Every state is kept in the project history.
Step 05
3D, concept, render
A parametric 3D build for dimensional truth, a volumetric concept for the conversation with the architects, and a presentation render for the client — top-down, eye-level or isometric.
Step 06
Price it and hand it over
An editable equipment schedule, service loads — electrical, water and drainage, gas, extraction airflow — a full quote including installation, engineering, design and margin, and a compliance report scored against EU Reg. 852/2004.
The brain
Kitchen Architect
The agent. Holds the rules, decides the zoning, and orchestrates every engine below. Assignable to a project, and visible to that project's team.
Deterministic
Zoning & scoring
Layout generation and HACCP evaluation by rule, not by generation. The same brief gives the same answer twice — which is what makes the score worth quoting.
Dimensional truth
Parametric 3D
The technical model in millimetres, with drawing sheets, plus a massing concept for the architects. Exports as DXF, PDF, SVG, PNG and structured data.
Regulatory check
Sources on call
One action queries the regulatory corpus from inside the drawing and answers citing the official source — so the layout is argued against the code, while it is still cheap to change.
Presentation
Render layer
The client-facing image, generated from the approved layout, queued and filed so a render never floats free of the project it belongs to.
What leaves the studio
- Zoning + 3 variants
- HACCP score
- Equipment schedule
- Service loads
- Full quote
- 3D model
- Concept
- Render
- DXF · PDF · SVG · PNG
Further verticals — concept economics, food service engineering, content and publishing — are in development, and released only when they meet studio standard.
Shared with the client team
HACCP compliance and zoning, in the client's hands.
The first BRAIN OS modules opened to a client team. On a cloud-kitchen and gelato project in Qatar, the owner and the project's HACCP consultant each have a private project portal, with two assistants working beside the project files.
HACCP compliance
Regulation, cited
Food-safety and licensing questions are answered from the public regulatory corpus — Codex HACCP principles, the Ministry of Public Health code of practice, cloud-kitchen licensing, grease-trap and drainage specifications — always citing the official source, and always reminding that the final HACCP opinion belongs to the consultant.
Studio CAD Architect
The zoning, explained
The same Kitchen Architect that draws the layout answers on the project's current zoning — rooms, flows, separations, equipment — from the approved version, updated at every revision.
Boundaries
Only public sources
Confidential material never reaches a client portal: partner brands under NDA, internal manuals and the studio's own research stay inside BRAIN OS.
Traceability
Every question logged
Each consultation is recorded in the project's audit trail, so what was asked, and what was answered, can always be reconstructed.
What the client team gets
- Private project portal
- Compliance assistant
- Architect assistant
- Official citations
- Shared project folder
- Audit trail
Built as a module other clients can adopt — always delivered inside Paolo's advisory, never as stand-alone software.
In the pocket
BRAIN OS Companion.
Most of this work does not happen at a desk. It happens on a site visit, in a supplier's warehouse, in a kitchen at service. The Companion app is BRAIN OS where the work actually is.
One screen, no menus to learn. It opens telling you whether the system is online, and everything below it is one tap: ask a question, start recording, or capture what is in front of you. Whatever you capture lands in the same memory the agents read — so a photograph taken in a kitchen at eleven in the morning is available to a layout question that afternoon.
Capture
- Scan docA supplier quote, a permit, a spec sheet — read and filed.
- Business cardA contact from a trade fair, straight into the record.
- Barcode / QRA product identified from the shelf.
- Describe scenePoint the camera at a space and get it described back.
- PhotoEvidence from site, attached to the project it belongs to.
- Upload filesAnything already on the phone.
Intelligence
- TranscribeA meeting or a voice note turned into text.
- TranslateBetween the languages the practice works in.
- Polish textA rough note made ready to send.
- EntitiesNames, companies, figures and dates pulled out and linked.
Ask & record
- Ask BRAINThe same routed system as the desk, in one field.
- Record · Voice noteDictate on the move; the transcript reaches the right agent.
Decisions & control · new in version 4
- BRAIN CentreDecisions waiting for Paolo, with confirm and deny; a refusal always needs a reason.
- Confirm from a notificationWhen an agent needs approval — even to restart a machine — a push arrives with Confirm and Deny. Nothing sensitive runs without it.
- System & usageThe state of every service and the AI models used today, at a glance.
- Ask an agentPut a question to a specific agent, and search across past working sessions.
- Personal profilesEach person on the team has a profile: their own memory, their own notifications.
- Works offlineOn-device AI answers the basics when there is no signal.
Claude connector · for client teams
BRAIN OS inside your own Claude.
The client's team connects BRAIN OS to its own Claude — the desktop app or claude.ai — and a Project Cockpit appears pinned in the sidebar, next to the conversation. It shows one project only, always live, and every module is designed for the day-to-day of a food business project: the kitchen, the suppliers, the inspections, the menu, the opening date. The reasoning runs on the client's own Claude plan; the method, the data and the judgement stay with Paolo Barichella and FLC.
BRAIN OS CockpitPinned in the Claude sidebar · pop-out · full screen
Good afternoon
Cloud kitchen, Doha · TuesdayUpdated 14:45↻ Refresh
8Open tasks
1Completed
3Next meetings
12Minutes
23Items in project
4Plan phases
🗓️ Agenda — next 3 weeks
✅ Open tasks All
Validate all kitchen flows against HACCPNo raw vegetables through the hot kitchen; FLC supports with the zoning review.HCHACCP consultant
Deliver the menu list and purchasing strategyKey dependency for the final zoning and the equipment selection.ECExecutive Chef
Review menu vs equipment and zoningFLC updates zoning review and equipment list once the menu is in.PBPaolo Barichella
📝 Latest minutes All
Weekly coordination — kitchen flows28 Sept
OpenOwner review — menu and storage21 Sept
OpenSite visit — utilities and MEP17 Sept
Open📐 Zoning Open
Zoning review — ground floor, rev. 03The FLC zoning review is the source of truth for layout discussions.
⚡ Quick actions
🛡️ Ask compliance✉️ Send a request✨ Status update🌐 Web portal
Set up once, in three steps
- Add the connectorIn Claude: Customize → Connectors → Add custom connector. One address, nothing else to install — no extra software, no browser extensions.
- Sign in with a codeThe team member types the email FLC registered and receives a six-digit code. The sign-in lasts months, on desktop, web and phone.
- “Open my BRAIN OS Cockpit”Claude installs the Cockpit by itself, pins it in the sidebar and sets it up. Three clicks, once. New versions arrive with a one-click “Update now”.
Built for client teams
Your project only
The page holds no data: it reads everything live, with each person's permissions.
Nothing written silently
Creating, assigning or closing a task, uploading a file, sending a request: Claude asks first, and FLC is notified.
Switched on per person
FLC activates modules member by member, and can switch any of them — or the access — off at any time.
The workspace
- BRAIN OS Cockpit ArtifactThe project's home in the Claude sidebar, with pop-out and full screen: key numbers, agenda for three weeks, tasks, latest minutes, quick actions.
- BRAIN OS AssistantA chat in the corner of the Cockpit that knows the project. Ask in English or Arabic; switch on Compliance Qatar or the Architect when the question needs them.
- Cloud document sharingThe project folder: open documents, drawings, images and spreadsheets, upload new ones, and have the Assistant summarise any file.
- Direct requestA request to FLC in two lines: it reaches Paolo Barichella as a task and an email, and is followed up.
- Guide & instructionsA condensed quick start and an extended manual in English, built into the Cockpit and always up to date.
Project management
- Project Management PlanPhases, milestones and responsibilities of the food project, from concept to opening.
- GanttPhases and progress, plus a timeline of tasks and meetings on one view.
- Tasks, team & stakeholdersEvery task has an owner among the project's stakeholders and a due date. Filter by person, assign, close; each new assignment reaches its owner by email.
- Meetings, minutes & reportsThe project meetings with their links, every recorded call with summary, action items and transcript (Fireflies integration), and progress reports ready to share.
- Weekly digest & triageEvery Monday morning, what moved, what is late and what needs a decision, by email.
Kitchen, compliance & operations
- Qatar HACCP complianceQuestions on Qatar food safety, HACCP and fit-out rules, answered with citations from the official sources. The final assessment stays with the project's HACCP consultant.
- Zoning, Kitchen Architect & CAD StudioThe current zoning review, the project drawings, layout revision requests to FLC, and an Architect that reasons on flows: staff entrance, waste route, cold rooms.
- RenderingPhotorealistic views of any area of the project, generated by FLC's render engine and saved in the project folder.
- Equipment & supply chainThe equipment list by zone, with quantities, suppliers, status and prices, and a running total.
- Menu engineering & food costDishes, recipes per portion and food-cost percentage against the target; what is over target shows in red.
- SOP & trainingStandard operating procedures drafted from the Qatar sources, in English or Arabic, as drafts for the HACCP consultant to validate.
- InspectionsSite checklists with photos taken from the phone; issues counted visit by visit.
Decisions & reach
- Board of LuminariesA panel of virtual experts — Executive Chef, Food Safety & HACCP, Kitchen Architect & MEP, Brand & Guest Experience, F&B Finance, Operations & Sustainability — debates a question and proposes decisions and next steps, saved as minutes.
- BRAIN OS CompanionThe project on the phone: notifications, the digest, and BRAIN OS in any Claude chat on the move.
- Arabic interfaceMenus and titles in Arabic for the members who prefer it; the Assistant answers in Arabic too.
The connector is part of the BRAIN OS operating method: it is activated only within an advisory mandate, module by module, and quoted with it. It is not sold on its own.
How BRAIN OS is engaged
A strategic asset, quoted as a service of its own.
BRAIN OS was not built to be sold as software, and it never will be: no licences, no code, no self-service. It is the strategic asset behind Paolo Barichella's advisory — the Infinite Brain that keeps twenty-four years of method, projects and precedents working at once. Clients reach it in three layers, and the operating method is quoted separately from the advisory.
Layer 01 · Always first
Strategic advisory
Paolo's judgement, signed deliverables, the Advisory Board of the Luminaries, the decisions that matter. BRAIN OS works in the background, making every answer faster and better grounded. Every engagement starts here.
Layer 02 · Quoted separately
The BRAIN OS operating method
The client's team works inside the system: the Cockpit, the five-level project engine, shared project documents, and modules such as Studio CAD Architect and Compliance. It sits on top of the advisory — never on its own — and is sized to the project: a single venue, a structured team project, or a multi-site format.
Layer 03 · By contract
Royalties and equity
When what is created together multiplies, the value is shared: a royalty on each new opening of a format, a royalty on the sales of a product, or — in research and development — a royalty on the intellectual property or a stake in the venture.
Studio CAD Architect can be activated only for the months of layout design; a one-off onboarding sets up the Cockpit, the shared archive and the project notebooks. Every proposal is written for the project, never sold by the day.
Demo
Talk to the assistant.
The assistant on this website is a small public window on BRAIN OS: a language model running on our own server, answering only from Paolo's public profile, in your language. It is not software for sale: BRAIN OS is the strategic asset behind Paolo Barichella's advisory, and its operating method is quoted as a separate service, on top of the advisory.
Access
Not software for sale. A practice you can brief.
BRAIN OS is not open for self-service. It runs on client mandates, alongside Paolo, under NDA. If you are considering a project where it would make a difference, describe it.