Above the systems. Not instead.

Public search is loud with two pitches that sound opposite and end the same way. One sells a rip-and-replace: dump the ERP, buy the new stack. The other sells a chat that “sits on top” and quietly becomes a second truth. Both miss the cut operators need.

Spectacle keeps the cut sharp. Above the systems. Not instead. Agents assemble a named measure from what your systems already hold. A person releases it. The source of record stays where it is.

Layer is not replacement

A new UI that re-enters Wareneinsatz is still a second system. A fluent paragraph that “knows” the Dienstplan is still guessing if Zeitwirtschaft already holds the plan. Mixing them is how operators get confident wrong work.

On Spectacle, the layer sits above ERP, Warenwirtschaft, and Zeitwirtschaft. It does not replace them. It does not invent a parallel Betrieb. It turns what those systems already know into a named measure — simulated in code, released by you.

Same-series cuts already live: the screen (dashboard is not a decision); the file (right numbers can still be reporting); the commercial offer (agents take the work); the category (one core, every kind of business); the release gate (Freigabe holds the switch). Arithmetic stays in code. This piece locks the stack law under those cuts.

What stays the system of record

The ERP keeps the master. The Warenwirtschaft keeps Wareneinsatz. The Zeitwirtschaft keeps the Dienstplan you already publish. Spectacle does not become a thirteenth tile that asks you to look harder in a new place.

Agents propose. Freigabe decides. Logged. Reversible where the source system allows. Silent auto-rostering is not the job. Tax, Buchführung, and Jahresabschluss stay with the people who own them. A sealed Kasse is never in the write path. Legally sealed systems of record are never written to — that is a hard exception, not a roadmap item.

What the layer is for

Ontology describes the Betrieb as objects and relationships. Forecast and simulation stay in code. Language sits on top: explain, name the measure, ask for Freigabe. The model does not become the calculator, and it does not become a second ERP.

Co-CFO, Co-HR, Co-CEO are lenses on that stack — not SKUs that replace the tools you already run. New sector = configuration, not a new product that rips out the floor.

The pattern, not a sector SKU

It fits where three things hold at once: demand is uncertain, capacity is fixed in the short run, and labour and material must be committed before demand is known.

Six public bands sit as equals — manufacturing and production; warehousing, logistics and distribution; technical service and maintenance; health and care; retail and multi-site; venue operations. Gastgewerbe is one band among six, never the product story. The stack law is the same in every band: above the systems you already run, not instead of them.

What we are not selling

Not a rip-and-replace ERP. Not a second Warenwirtschaft. Not Dienstplan software. Not a dashboard that asks you to look harder. Not a website. Not a chatbot that invents a second truth. Not restaurant software. Not invented hours or migration savings.

If the object model already exists in your trade, twenty minutes is enough to see whether a layer over your stack is worth building. If the data cannot answer the question, we say so.

FAQ

Do you replace our ERP? No. Spectacle sits above it. The ERP stays the system of record.

Do you replace Warenwirtschaft or Zeitwirtschaft? No. Wareneinsatz and the Dienstplan stay where they already live. Agents propose; Freigabe releases.

Is this a chat that becomes a second truth? No. Arithmetic stays in code. Language sits on top. Fluent language without a deterministic path is still reporting theatre.

Do you write the Kasse? No. Legally sealed systems of record are never written to. The Kasse is not in this loop.

Do you invent hours or migration savings? No. Time back is the want. We do not publish invented hours, ROI, or accuracy bands.

Is this only Gastgewerbe? No. Six equal bands. The fit is the operating pattern, not a beachhead SKU.

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