Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
{
"prompt": "Follow Yorkie Coding Constitution strictly.\n\nUpdate docs/ARCHITECTURE.md with latest changes and Mermaid if needed.\nOutput the FULL updated file.\n\n<!-- YORKIE VALIDATED — workflow defined, architecture documentation automated, system docs maintained -->",
"variables": [],
"notes": "Keeps docs/ARCHITECTURE.md current",
"metadata": {
"source": {
"provider": "github-windsurf-workflows",
"repository": "https://github.com/yorkiebrown1/psychic-parakeet",
"path": ".windsurf/workflows/update-architecture.md",
"ref": "f2a50423ef650ff08abebdeac3c18e18b95484ab",
"url": "https://github.com/yorkiebrown1/psychic-parakeet/blob/f2a50423ef650ff08abebdeac3c18e18b95484ab/.windsurf/workflows/update-architecture.md",
"key": "yorkiebrown1/psychic-parakeet/.windsurf/workflows/update-architecture.md"
}
}
}
Installed into a catalogue, chosen by a router
Install Update Architecture Doc and it becomes one more candidate the router can pick - when it fits.
A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.