Bootstrap CAP Server

Bootstrap a generic CAP server over a user-provided graph or causal runtime. Classify the runtime shape first, prefer the smallest honest public surface, then expand only if the user's graph actually supports stronger semantics.

When to Use

• The user has an existing causal graph, runtime, or internal causal API that should expose GET /.well-known/cap.json and POST /cap.
• The user wants a fresh CAP server scaffold or wants to wrap an existing service behind CAP.
• It is unclear whether the runtime supports structural, observational, or interventional verbs honestly.
• The capability card should be derived from the mounted surface instead of maintained by hand.

When NOT to Use

• The main task is auth, gatewaying, tenancy, rate limits, or other product-perimeter work.
• The main task is inventing vendor extensions instead of exposing CAP core verbs honestly.
• The user has no graph, runtime, or causal API yet and needs help building causal machinery from scratch first.
• The request depends on claiming Level 3 or counterfactual support.

Workflow