Outcome specification
A method of specifying model behavior by describing the desired end result, constraints, and available resources rather than detailing the procedural steps to achieve it
As defined in Your AI Stack Isn't Ready for Claude Mythos
Where it comes up · 1
Most important claims · 3 of 3Search all claims for “Outcome specification” →
- Constraints and guardrails should be business rules that remain valid across model upgrades (e.g., 'never disclose customer financial data', 'always verify refund eligibility against policy') and should survive the shift to outcome specifications.Your AI Stack Isn't Ready for Claude Mythos
- Outcome specifications may not be achievable today with current models, but organizations should start architecting systems to use outcome specs now to be ready for Mythos release.Your AI Stack Isn't Ready for Claude Mythos
- Example of good outcome specification for customer service: 'Resolve this customer's issue using our knowledge base, policies, and account history. Customer should leave satisfied and resolution comply with our return policy.' This contrasts with process-heavy specifications that route through intent classification, handler assignment, and specific retrieval methods.Your AI Stack Isn't Ready for Claude Mythos