{"samples":[{"id":"saas","title":"SaaS agent readiness sample","score":54,"grade":"D"},{"id":"api","title":"Developer/API sample","score":62,"grade":"C"},{"id":"ecommerce","title":"Commerce readiness sample","score":48,"grade":"D"},{"id":"web3","title":"Web3 product sample","score":71,"grade":"B"}],"selected":{"id":"saas","title":"SaaS agent readiness sample","score":54,"grade":"D","summary":"A SaaS site with pricing and docs, but no dedicated agent discovery files or manifest.","output":"EXECUTIVE DECISION SUMMARY\n\nReadiness: 54/100 (Grade D)\nDecision: Core implementation recommended\n\nPRIORITY 1 - Public discovery\nStatus: Open\nOwner: Website team\nWhy it matters: Assistants do not have a stable route into current product context.\nAcceptance: Public discovery routes resolve and match approved website facts.\n\nPRIORITY 2 - Buyer handoff\nStatus: Open\nOwner: Marketing and commercial\nWhy it matters: Plan, support and next-step context is spread across separate pages.\nAcceptance: A fresh review can identify the product, audience, plans and human buying route without assumptions.\n\nPACKAGE OUTCOME\nSYA Standard Discovery Layer, customer review workflow and assisted installation.\n"}}