Objects from the Betrieb. Not a chat demo.

A chat window can look like work. You paste a screenshot. You ask for a plan. You get fluent language back. The morning still starts the same way: someone has to name what is true in this Betrieb — which Schicht is open, which Auftrag is late, which Freigabe is waiting — before anything can move.

Spectacle does not start with a chat paste. It starts with objects from the Betrieb.

What “objects from the Betrieb” means

The Betrieb is already full of entities and relationships your systems hold: people, sites, shifts, orders, stock lines, machines, care cases, dock windows. An ontology names those objects and how they connect — so a measure is about a real Schicht or Auftrag, not a paragraph that could belong to any shop.

That is the first pillar: Ontologie. New sector = configuration on the same core, not a new product and not a second homepage. See one core, every kind of business and above the systems, not instead of them.

Without objects, an agent has nowhere honest to stand. With objects, a proposal can point at something you can release or refuse.

Not a chat demo

A demo that only talks is not the commercial offer. Chat over bad figures does not bind capacity. It does not assemble what ERP, Warenwirtschaft, and Zeitwirtschaft already know into a named measure for the hours left. It does not keep Freigabe human.

We will not sell Spectacle as a chatbot bolted onto a dashboard. The sell is agents on a layer that already models the Betrieb — simulated work, released by you. Time back. Not another window that asks you to re-explain the floor in prose every morning.

Agents propose. You keep the switch.

Spectacle is the layer over the Betrieb you already run. Agents on that layer take operational work the Inhaber still does by hand: redeciding, coordinating, assembling numbers that already exist into what to do next.

They propose a named measure against named objects. You release it. Logged. Reversible where the source system allows. Without Freigabe the agent sleeps — proposal is not release; you keep the switch. Arithmetic stays in code. The model only writes language. We do not write sealed systems of record. We do not auto-assign shifts without human release.

Six bands equal

Objects are not a gastro thesis. Six public bands sit as equals. We name them so nobody reads ontology as one trade’s SKU:

• Manufacturing and production
• Warehousing, logistics and distribution
• Technical service and maintenance
• Health and care
• Retail and multi-site
• Venue operations

Venue ops is last on purpose: equals, not a beachhead story. A Schicht in production, a tour in field service, a case in care, a line in retail, a Dienstplan in venue ops — same product conversation when the three-part pattern holds: uncertain demand, short-run fixed capacity, labour and material committed before demand is known.

What we are not selling

Not a chat demo. Not restaurant software. Not “AI for hospitality.” Not a dashboard that invents hours, ROI, euros, or accuracy bands. Not a website. Not a second homepage per industry. Not silent write-back into the Kasse.

If your morning still depends on retyping the Betrieb into a prompt, the gap is objects and Freigabe — not a better paste.

If mornings still start by explaining the floor to a blank prompt, request an Erstanalyse. Twenty minutes is enough to see whether objects from your Betrieb — with agents and Freigabe — are worth building. If the data cannot answer the question, we say so.

FAQ

What does “objects from the Betrieb” mean? Named entities and relationships your operation already runs — Schicht, Auftrag, stock, people, sites — bound in an ontology so agents propose against something real, not a chat paste.

Is Spectacle a chatbot? No. Chat can be a surface. The product is agents on a model of the Betrieb, with Freigabe. Not a demo that only talks.

Do agents act without me? No. Agents propose. Freigabe releases. Without Freigabe the agent sleeps. You keep the switch.

Is this only for Gastgewerbe? No. Six equal bands. Configuration, not a beachhead SKU.

Do you invent hours saved by the ontology? No. Time back is the want. We do not publish invented hours, ROI, euros, or accuracy bands.

Where should I start? Spectacle. The Insights series is how we write about the operation.