Harnesses: the pub operating system hiding in plain sight
If you care about AI systems, you will have heard the word harness. Hospitality should care too, because a good pub has always run on one.
If you have any interest in AI systems, you will have heard the term harness. It is a big thing right now among the people who truly understand AI.
That matters, because the useful conversation has moved on from simply asking which model is cleverest. A model is only one part of the system. The harness is what gives it a job, feeds it the right context, sets the boundaries, checks the work and remembers what happened.
I think hospitality should pay attention. A strong pub already works this way. It has a harness, even if nobody calls it that.
What a harness actually is
In AI, a harness is the operating layer around the model. It is the part that turns raw capability into useful work.
It knows the goal. It knows the rules. It knows where the information lives. It knows which tools can be used. It knows when to stop. It knows how to check whether the output is good enough.
Without that layer, even a capable model becomes a bright person dropped into a dark room. It can talk. It can guess. It can sound convincing. But it cannot reliably improve the business.
Pubs already understand this
A pub has its own operating system. I do not mean software. I mean the things the team does every day so the business can trade.
Opening up. Cellar checks. Bookings. Prep lists. Allergens. Rotas. Briefings. Handovers. Table plans. Complaints. Cash-up. Cleaning. Ordering. Menu changes. The way the team spots pressure before the guest feels it.
None of that is glamorous. Most of it is invisible when it works. But it is the difference between a pub that copes and a pub that trades with intent.
The best operators are not relying on heroics every shift. They have made the normal day strong enough to carry the unusual day.
The Alpha Harness idea
JoeBrain is my version of an Alpha Harness. It is not a chatbot bolted onto a laptop. It is a controlled working space where intent becomes output.
I bring the judgement. The harness brings the context, the stored thinking, the repeatable steps, the checks and the trail of what changed. That is the useful part. It means the system can get better because the work is visible.
That is also how good hospitality management works. You cannot improve what nobody can see. You cannot train what only exists in one manager’s head. You cannot scale the shift that depends on one tired person remembering everything.
Do not shrink a broken process
This is where a lot of AI projects will hurt businesses. They take a poor process and make it faster.
Cutting back a poor process just gives you a smaller poor process.
If the cellar routine is vague, AI will not make the beer better. If the handover is lazy, AI will not save the evening shift. If the rota is built on hope, AI will only move the confusion around more quickly.
The physical process has to be strong first. That does not mean perfect. It means clear enough that a capable person can follow it, challenge it and improve it.
Productivity then becomes a real question. What should the team stop doing? What should the system remember? What should be checked every time? What needs human judgement? What is just noise wearing a work uniform?
How to harness the harness
The work starts in the pub, not in the software demo. Walk the shift. Watch what really happens. Follow the handoffs. Find the places where people wait, repeat, guess or apologise.
- Walk the real shift. Do not design from the office. Stand where the work happens and write down the actual route.
- Name what good looks like. A harness needs a target. For a pub, that might be faster table turns, fewer voids, cleaner handovers or a calmer close.
- Find the weak handoffs. Most waste lives between people, not inside people. Look at manager to team, kitchen to bar, booking to floor and close to open.
- Make one source of truth. If the answer lives in four places, the shift will choose the easiest one, not the right one.
- Remove stupid work. Some work should be automated. Some should be deleted. The distinction matters.
- Keep people on judgement. Guests still need humans. Teams still need leadership. The system should carry the memory and the routine, so people can carry the moment.
- Prove the loop improved. Measure the thing that mattered at the start. If the work is calmer, cleaner or more profitable, keep going. If it only sounds clever, stop.
The point for hospitality
AI will matter in pubs, restaurants and hospitality groups. But it will matter most where the operating system is already visible.
The businesses that win will not be the ones with the flashiest bot. They will be the ones that know how work moves through the building, where quality is won or lost, and which parts of the day should never depend on memory alone.
Build the harness first. Then add the AI.
What leaders should do next
- Look at the real shift before looking at AI. If the work is vague on the floor, automation will only move the mess faster.
- Define the harness: intent, context, work, proof and memory. Every good pub already needs that loop.
- Fix weak handoffs first: manager to team, kitchen to bar, booking to floor, close to open.
- Do not shrink a broken process. Make it clear enough for a capable person to follow, challenge and improve, then bring in AI.