Follow runtime contracts

← Recipes

Question

Which producers, handlers and registrations form this runtime contract, and where is one side missing?

Recipe

Choose the surface that represents your framework:

loct events --limit 8
loct follow events --limit 8
loct commands --limit 8
loct trace save_document
loct routes --framework fastapi
loct pipelines

These are alternatives, not a universal six-command pipeline. commands and trace target the Tauri command bridge. The installed help used for this catalog describes routes as FastAPI/Flask detection. Event families and runtime bridges vary by language and version.

Expected answer shape

Identify the producer, exposed contract name, receiving handler and registration evidence. Distinguish a matching name from a proved connection. Record which framework family the detector actually covers.

For HTTP, a route declaration is only part of the answer: inspect router mounting, prefixes, method, client URL construction and parameter shape. A declared handler may be intentionally called by an external client.

Decision

Choose which missing registration or contract mismatch needs verification. A pairing result can guide a focused integration test; it does not prove successful execution, authentication or delivery.

Check the interpretation

loct find save_document --literal --group-by-file --limit 30
loct body save_document --max-lines 80 --json

For an event, verify emit/observe semantics and receiver identity. For a route, verify declaration and mounting. If events finds a framework bridge while pipelines reports zero events, investigate the summaries' supported families before interpreting the zero.

Counterexample

server.listen(PORT) is not necessarily an application-event subscription. A custom emit_status method is not automatically a Tauri emitter. Rust enum-message protocols, Swift process launches and cross-language FFI may require evidence outside a surface's supported family.

Evidence

The September round found duplicate HTTP route registrations and NotificationCenter pairs, but lacked complete coverage of enum IPC and C ABI contracts. October trials again found useful event bridges with narrower pipeline summaries. Missing cross-family coverage belongs in the answer, not behind a healthy-looking zero.