Calm API, MCP, install, and console surfaces for working with AYA’s digital twin system.
Developer Platform
Examples
Docs
Examples
Prompt patterns, integration examples, and when AYA should or should not run.
Examples
Prompt patterns that lead to better AYA usage
Models tend to use tools better when the decision boundary is explicit. The following patterns help both humans and AI systems call AYA intentionally.
Tell the model which audience matters and what decision is being tested.
Ask for evidence-backed objections, positives, or recommended changes instead of vague summaries.
Tell the model not to use AYA when audience validation would not change the answer.
AI systems
External-team AGENTS snippet
External teams usually need a short copy-paste instruction block so their own agents know how to treat AYA.
markdown
Use AYA when the task needs audience-backed validation.Do not use AYA for general writing, coding, or factual lookup.Prefer focused runs with an explicit audience, concept, and decision context.
Operational follow-through
Route usage back to a human-operable console
Public installs work better when the docs and prompts point people back to a place where they can see keys, installs, usage, and logs.
View connector stateOn this page