Guides
Status: Fixture Preview. Each guide walks an end-to-end pattern against the current fixture cloud. Receipts carry
fixture: true. See reference/fixture-vs-production.md.
These pages are worked walkthroughs for common integration patterns. Each picks one task, runs it through the membrane end-to-end, and shows the receipts at every step.
End-to-end walkthroughs
Section titled “End-to-end walkthroughs”- German invoice / payment / advisor walkthrough — the wedge flow, end to end.
- Projecting context transitions — fork → admit → diff → promote / discard.
Provisioning and authority
Section titled “Provisioning and authority”- Tenant provisioning — key custody → tenant create → company bootstrap → onboarding gate → production admission precheck.
- Publishing an authority package — import → candidate → review → activate.
- Standing and mandates — claim → evaluate → grant; delegate → revoke. How an actor gets the right to act on behalf of a company.
Auth and presence
Section titled “Auth and presence”- Auth and sessions — login start / finish, session issue / refresh / inspect, revocation, recovery, and rate-limit posture.
- Human-auth flows — challenge → passkey verify → presence approval, plus the CPU face-match fallback.
Building Koerpers and connecting evidence
Section titled “Building Koerpers and connecting evidence”- Building a Koerper — patterns for designing a replaceable mutable body around a Geist.
- Generated Koerper discipline — the rules an AI-generated Koerper must preserve.
- Advisor integration — how a Steuerberater / Kanzlei console connects through the lens, advisor, and intervention surfaces.
- Connector evidence — feeding an external system’s witness into the Geist as redacted, content-hashed evidence.
Prerequisites
Section titled “Prerequisites”Every guide assumes you’ve completed getting-started.md
and have a fixture cloud running on 127.0.0.1:3011 with the
fixture bearer token.
Style of the guides
Section titled “Style of the guides”The guides are cargo-cult-friendly: copy-paste the snippets and they work against the fixture cloud. They use the TypeScript SDK by default; equivalents in Rust / curl are easy to derive from sdk/typescript.md and the API reference.