Aleph Hospitality · Deep Hospitality

What is inside
the engine

The handover pack is one folder of 161 files. This page does two things: it shows what those files are and what each part does — and then it walks you from the zip you received to the first sentence you type.

144
Built for this
Rules, staging intelligence, tooling, and three standards taken end to end as proof.
17
Aleph's own material
Fourteen evidence files and the three source procedures the worked runs began from.

Every file in the pack, by origin.

The six working parts

Select any one to open it.

From the zip to the first sentence

Five steps and a sentence. Two happen once and never again, one belongs to whoever looks after the SOP library, and Claude Desktop is assumed already installed.

1
You
Unzip it
One file arrives: DH_SOP_Engine.zip. Unzip it and you get a single folder called DH_SOP_Engine. Do not rename it, and do not move or rename anything inside it — the engine expects to find every file exactly where it is.
You should see: five numbered folders — rules, inputs, worked runs, toolchain, register — and five pages at the top, including START_HERE and HOW_TO_START.
2
You
Put it where it will live
Once, at installation
Move the folder to the drive where your division keeps its working files. If that drive is OneDrive or SharePoint, right-click the folder and choose the option that keeps it always on this device. Files that live only in the cloud look like they are there and are not, and the engine cannot read them.
3
You
Let the pack prove it arrived intact
Recommended, two minutes
The pack carries its own inspector. Open a terminal and run python3 4_Toolchain/check_pack.py from inside the folder. It verifies all 161 files against the manifest and runs every whole-pack check in under a minute.
You should see: All checks pass. The pack is internally consistent — plus two lines noting what is deliberately blank on arrival, which brings us to step 4.
4
Librarian
Point it at your library
Once, fifteen minutes — the one true prerequisite
The pack holds no procedures: your SOP library stays on your drive, and the engine has to be told where. Whoever looks after the library opens 2_Inputs/Where_The_Sources_Live.md and fills the three rows marked BLOCKING — where the English SOPs are kept, where the French are kept, and where the divisional manuals are (or no manual exists, if that is true). Paste the folder path or link, save, done.
Until this is done, the engine stops on purpose. It will not draft a standard it cannot locate, and it will tell whoever asks exactly which rows need filling and by whom. That is the rule working, not a fault.
5
You
Open Claude, choose Cowork, point it at the folder
In Claude Desktop, choose Cowork rather than Chat, and point the session at your DH_SOP_Engine folder. Leave Claude open while you work — it reads the folder on your machine, so closing it stops the work.
Step 6 · The whole instruction
“What's next for Rooms?”
Use your own division. Name a division, never a procedure — choosing the procedure is the engine's job, on the evidence. First it tells you in one line whether it can start and what it is working from. Then it names one procedure, gives its reasons, and stops for your go.
Read before you send up
Two documents come back: what the procedure is missing, then your own standard marked up with a reason on every change. A wrong finding is cheap to fix here and expensive after it reaches the person signing.
Never send up a bracket
Anything like [P3] still in the text is a value only your General Manager can give. A procedure issued with a bracket in it is a promise nobody made.
You do not approve it
Neither does the property. The document stays in tracked changes until somebody above property signs, and nothing is built from it before then. HOW_TO_START, one page, stays beside you for all of this.
Most of the weight is not where the file count suggests.

The worked runs are 109 of the 161 files and 44 of the 59 megabytes — but almost all of that is font data embedded inside Word documents, and their job is to be evidence rather than machinery. The engine itself is five rule documents and nine scripts: 31,674 words and 1,525 lines. That is the part that runs on the next procedure, and the one after, and the two hundred and sixty-sixth.

DH SOP Engine · pack v1.0 · 161 files · 59 MB unpacked Deep Hospitality · 10 August 2026