use-case-c

name

use-case-c

description

The Squeeze Loop instance for Use Case C — an HTTP API where the document plane (OpenAPI contract) and the runtime plane (live server) are forced into exact lockstep, on terrain C (split planes). The dominant failure is blending — a clean schema masking broken runtime behaviour (id leaks, tracebacks, missing auth), or a clean runtime escaping stale documentation. The exerciser RUNS the live server over HTTP but is physically denied the server source and the published schema (the load-bearing "run, don't read" channel). Use when working on src/C — the API governance policy, the canonical OpenAPI contract, the schema linter, the live server, the conformance test matrix, the legacy route-signature regression oracle, or the no-blend cross-check. Trigger phrasings: "use case C", "instance C", "split planes", "document vs runtime plane", "no-blend", "run don't read", "OpenAPI conformance squeeze", "id leak / missing auth on an untested route".

Use Case C — the split-planes API squeeze loop

Use Case C is a base squeeze loop (instance-c, terrain C): an API whose document plane (the published OpenAPI schema) and runtime plane (the live HTTP server) are forced into exact lockstep so neither can mask the other. Its SL-1.0 self-description is src/C/instance-c.sl.json; the companion write-up is src/C/docs/use-case-c.md.

The dominant failure it guards

Coherent-and-wrong here = blending — one plane's weak check standing in for the other's strong claim: a clean schema masking broken runtime behaviour (id leaks, tracebacks, missing auth on an untested route), or a clean runtime escaping stale documentation.

Terrain C — split planes

Correctness divides across two planes, each with its own authority: