Inspect callable Stories through typed interfaces before invoking them.
Find the Stories available in a workspace, inspect their inputs and outputs, and build an integration against their declared contract. The same business operation can serve an application, an agent, or an interactive form.
Discovery stays within the caller's workspace authority. Finding an interface does not grant permission to execute it.
A workspace publishes its own API description. Integrators can inspect the interface where the Story is registered rather than maintaining a separate description by hand.
Executable Use Cases explains how Stories fit the business specification. Native Story calls covers peer-to-peer invocation.
Developer reference
Workspace-scoped openapi.json projects callable Story signatures into OpenAPI operations. Swagger UI serves a browsable interface with local assets. Story discovery exposes signatures, rendered forms, and interface fingerprints.
Input concepts retain their RDF IRIs; HTTP parameter names are interface bindings. XSD datatypes map to parameter schemas. Declared output columns produce a typed row_schema: a singular Story documents one row object; a plural Story documents a table containing columns, rows, and a row count.
An undeclared output remains an open object. A raw SPARQL result names projected variables; it does not acquire a typed business schema merely by travelling through HTTP. Use Case scope distinguishes Stories with identical local names.
The generated description records the declared interface. Authorization, execution, and result validation remain separate runtime responsibilities.