Operation and HTTP variables

Operation collections

Operation values

Derived values:

Use role and derived classification instead of inferring behavior only from HTTP method or operation name.

Parameters

Each parameter exposes:

location distinguishes path, query, header, and cookie values. Effective path parameters include both path-level and operation-level declarations while preserving their source location.

Request bodies

Responses

Each response exposes:

primary_response is the normalized preferred success response. Templates that emit complete clients should still inspect all relevant responses.

Media types

Use media-type-specific schemas when one operation returns different representations.

Security

Operation security preserves explicit overrides and inherited API-level requirements. Empty operation security can intentionally mean public access.

Sources

Each source exposes:

Sources help templates generate selectors, relation inputs, or data-loading helpers without hardcoding response inspection.

Cache

Read policy:

Invalidation policy:

Resolved operation and resource targets are available after the registry is complete.

Query targets

Operations can expose normalized query, params, body, and response schemas through:

Example service template

Real packs should use language and import helpers rather than assuming TypeScript names directly.