Reference
This section holds the authoritative tables you reach for when you have a specific question and don’t want to re-derive the answer.
- Capability state — what each membrane
operation can truthfully do today (
shape-only/fixture-rehearsed/staging-durable/authentic). Updated with every contract change. - Outcomes — the
MembraneOutcomeenum and what each value means. - Refusal codes — the documented refusal taxonomy across all operations.
- Default posture — the contract’s
per-condition defaults (
refuse/pend). - Fixture vs production — what you can actually do today, what is gated, what the markers mean.
How to use these pages
Section titled “How to use these pages”- Building a Koerper UI? Bookmark outcomes and refusal-codes. Your UI must handle every documented outcome and surface the structured refusal correctly.
- Reviewing a contract change? Update capability-state in the same PR. The page is the user-facing ledger; if it falls behind the contract, end users will be misled.
- Debugging a refused call? Look up the refusal code in refusal-codes for the canonical meaning.
- Operating Gestalt? Read fixture-vs-production before showing anything to a real customer.