How Prompt Orchestra Is Different

Compared to ad-hoc “call the model” integrations, Prompt Orchestra binds:

1. Version identity — every run records which skill version and tool versions were used (orchestration_prompt_stack_version_id, tool metadata on the bundle in runPrompt).
2. Contracts — skill versions carry inputSchema, variablesSchema, outputSchema, and outputContractState; validation results flow into validation on run outcomes and traces.
3. Traces — contract, decision, and composition data are persisted and returned on run detail for debugging, not only final text.

The TypeScript SDK narrows the surface to publicRouteContracts so client types match server Zod schemas.

See also

• Run Truth
• Immutability