What is Gestalt?

Status: Fixture Preview. This page describes Gestalt’s intent and shape. The runtime today is a fixture rehearsal of that intent. See reference/capability-state.md.

The one sentence

Gestalt is the authority runtime where mutable business intent becomes admissible company reality.

The deeper sentence

Gestalt lets mutable business bodies act inside durable authority fields.

The thesis in one paragraph

Modern companies — especially German SMBs — are split across shop systems, banks, DATEV exports, payroll tools, contract folders, HR SaaS, DMS, email, Steuerberater correspondence, lawyer correspondence, internal spreadsheets, and AI-generated operational apps. The pain is not bad UX. The pain is that nobody knows which system is the real source of truth when an audit, refund, employee termination, late payment, tax filing, dispute, insolvency event, or legal hold arrives.

Gestalt answers: there is one governed company reality. Every app and advisor is a lens, projection, or actor around it.

The trinity

Gestalt’s core model is three organs, not one.

• Geist — the governed truth organ. Holds durable company facts: invoices, payments, contracts, payroll facts, obligations, consents, mandates, attestations, legal situations, advisor opinions, filings, proofs, counterparty commitments. Narrow, slow-moving, signed, append-only.
• Koerper — the mutable operational body. Product data, UI state, CRM fields, inventory tables, workflows, dashboards, caches, AI-generated apps, experiments, local projections. Vast, fast-moving, replaceable, customer-authored.
• Mesh — the emergent field of all Geists in bilateral contact. Not a global database. Not a blockchain. The shape made by local relationships: company to customer, company to supplier, company to Steuerberater, company to bank, company to regulator.

The core sentence:

AI can write the Koerper. Gestalt preserves the Geist.

The core axiom:

Application code may mutate the Koerper, but only the Geist may issue business reality.

An app can draft an invoice. The Geist issues the invoice. An AI can propose a posting. The Geist commits the balanced entry. A lawyer can review a termination. The Geist records the opinion.

For more, see concepts/geist-and-koerper.md.

What Gestalt is not

Gestalt is not, and is not trying to become:

• an ERP,
• a legal-tech product,
• an accounting app,
• a BaaS,
• a contract-lifecycle management product,
• an agent platform,
• a database,
• a compliance dashboard,
• a generic PaaS,
• an app marketplace,
• a global graph,
• a legal oracle,
• a surveillance ontology.

Some of these may become surfaces around Gestalt. None of them are Gestalt.

What ordinary software asks

Can this user call this function?

What Gestalt asks

Can this actor, under this mandate, in this situation, citing these facts, under these active authority fields, with this evidence, cause this act to become company reality?

That is the runtime.

The atom

Every serious transition in Gestalt is an atom. An atom carries:

• Subject — who acts or speaks?
• Cause — which prior facts does this depend on?
• Authority — who or what makes the act admissible?
• Content — what material claim is being made?
• Evidence — what supports the claim?
• Governance — which rules, policies, laws, contracts, or packages evaluated it?
• Effects — what future operations are created, required, blocked, warned, or escalated?
• Commitment — what proof seals the transition?

Atoms cite capability atoms — published, accountable definitions of what the act means. See concepts/atoms-and-capabilities.md.

Authority before automation

Gestalt starts with authority, not convenience. Every serious operation must answer:

• Who may do this?
• Under which mandate?
• For which subject?
• In which scope?
• Citing which prior facts?
• Against which active restrictions?
• With what evidence?
• Under which law, policy, contract, or advisor condition?
• Who carries responsibility if it was wrong?

An autonomous AI agent may act without a human click. It may not act without identity, mandate, scope, evidence, and liability topology.

Pendulums, spheres, Verlag

• Pendulums are Geists whose emissions affect other Geists. They radiate authority or reliance within bounded spheres. Sovereign Pendulums (states, courts, registries, Finanzamt). Professional Pendulums (Kanzleien, Steuerberater, auditors). Commercial Pendulums (insurers, banks, payment rails). Verlag Pendulums (publishers of legal-operational instruments). Company Pendulums (boards, officers).
• Authority spheres are intersections of subject, actor, territory, time, matter, operation, product, counterparty, company form, professional qualification, contract, policy, legal situation, and reliance terms. Gestalt does not ask whether a rule is globally active; it asks whether a sphere is active for this act.
• Verlag digests authority into usable legal-operational instruments: clause libraries, contract templates, predicates, evidence requirements, operational effects, and SDK-level workflows. The Verlag is not the source of law; it is the accountable publisher of bridges between law and business operation.

For more, see concepts/pendulums-and-verlag.md.

Effects

Effects bridge governance to product behavior. Standard modes:

RefuseAtCommit
CommitButWarn
RequireEvidence
RequireIntervention
RequireCounterpartyAck
RequireWaitingPeriod
RequireNotification
RequireAdvisorOpinion
RequireExternalAuthority
MarkContested
OpenReviewMatter

Contracts, insolvency, tax, payroll, banking, refunds, robots, sanctions, and company policies all speak this same operational language. See concepts/effects.md.

Realities and projection

Atoms live in realities. Real company history is record reality. A simulated future (“what if we add a French warehouse?”) is a projected reality. Both go through the same Gravity admission. Promotion from projection to record is itself a governed act. Atoms never silently leak between them. See concepts/realities.md.

Advisors as lenses

Steuerberater, lawyers, auditors, banks, insurers, and regulators do not get generic access. They receive scoped lenses: visible facts, permissible operations, issueable opinions, reliance terms, confidentiality terms, validity windows, revocation paths, proof export rights. The lawyer’s click becomes an atom, not email sediment.

See concepts/advisor-lenses.md. The membrane exposes lens.scope, lens.disclose, advisor.openMatter, advisor.issueOpinion, advisor.requestEvidence, intervention.request, and intervention.issue today as staging-durable fixture operations; production-grade advisor trust remains closed.

Anti-Palantir

Gestalt must coordinate admissible action without becoming a totalizing surveillance ontology. Safety rails:

• no global mesh view,
• no central company graph across all tenants,
• no global reputation score,
• raw sensor streams stay external by default,
• disclosure is bilateral or authority-scoped,
• advisors see through lenses, not omniscient dashboards,
• regulators receive proofs they are entitled to, not universal telemetry.

The AI-age thesis

AI makes Koerper cheap. Apps, dashboards, workflows, CRMs, shop surfaces, HR tools, and internal systems will become cheap to generate and replace. The scarce thing is not application code. The scarce thing is governed continuity.

In the age of omnipotent AI, every company needs a Geist underneath its generated Koerpers.

Agents move fast because the Geist is strict. Generated software can change weekly because company truth does not blink.

Who is this for?

You should care about Gestalt if you are:

• A developer or agency building software for German SMBs and finding the same governance pain repeated in every project.
• A Steuerberater or Kanzlei tired of email-driven attestation and loose evidence.
• A Verlag-style publisher of operational legal instruments who wants a governed substrate for your output.
• An IT consultant placing AI-generated apps inside companies and worried about what happens when those apps drift, get replaced, or fail.
• An operator who wants company truth to survive any specific app or vendor.

Gestalt is probably not for you if:

• You want a turnkey ERP or accounting product.
• You want a marketplace of plug-and-play apps with no governance thinking.
• You want a single-table audit log.
• You want a global business graph or a universal company score.

What you can do today (Fixture Preview)

You can:

• Read the membrane contract and SDK as a stable target.
• Run the fixture cloud locally.
• Hit every endpoint and inspect shape-correct responses.
• Build a Koerper UI / SDK against the contract that will work the day Gestalt becomes authentic.
• Rehearse the German invoice → payment → advisor flow as a fixture.
• Verify the membrane discipline (Koerper ↔ Geist boundary, refusal codes, fixture honesty markers) in shape.

You cannot yet:

• Issue an invoice that becomes real company reality.
• Have a Steuerberater issue a binding opinion atom.
• Connect a real bank or shop and have movements become real evidence.
• Publish or rely on a real authority package.
• Onboard your own tenant or company.

For the full breakdown, see 022 gap report and reference/capability-state.md.

Where to read next

• Glossary — the vocabulary you need.
• Getting started — run the fixture and make your first call.
• Concepts: the membrane — how Koerper and Geist talk.
• API reference — every operation.