Developer support has an unusual property: the correct answer is almost always derivable from artefacts you already own — the OpenAPI spec, the SDK source, the changelog. A system that answers from prose documentation is working from a lossy copy.
All SaaS & Technology →
Most documentation assistants index the docs site. That inherits every problem the docs have: pages describing a deprecated parameter, an example that stopped working two releases ago, a guide written against the previous major version. The assistant then reproduces those errors confidently, and a developer wastes an hour before discovering the documentation was wrong rather than their code.
The alternative is to ground the system in machine-readable sources of truth: the API specification, the SDK source, the type definitions, the changelog, the migration guides. Those are generated from or checked against the running system, so they are correct by construction in a way prose is not.
Prose documentation still matters — it carries intent and idiom that a spec cannot. But it is a secondary source, and where the two disagree the spec wins and the system should say so. That single ordering removes most of the ways a developer assistant misleads people.
Reindex on release, automatically, as part of the pipeline. An assistant that lags the API by a sprint is generating wrong answers on purpose, and the lag is invisible to users until they are already confused.
Chunk code and specs structurally rather than by character count. An endpoint definition split in half mid-schema retrieves badly and reads worse. This is one of the largest quality levers in a developer-docs retrieval system and it is a parsing decision rather than a model one.
And measure with real questions from your support channels, not invented ones. The distribution of what developers actually ask is quite different from what a docs team expects, and it is sitting in your ticket history waiting to become an evaluation set.
or a pasted error
answer for their version
spec · SDK · changelog first
in their language
against the spec before returning
logged as a docs defect
No. It should absorb the repeated questions — authentication, pagination, common errors, version differences — so support engineers spend their time on the genuinely hard integration problems, which is both better use of them and the part developers most value talking to a human about.
It can generate examples and integration snippets, validated against the spec. Treat them as a starting point rather than production code — which is exactly how developers treat documentation examples anyway.
Access-controlled retrieval, so a developer sees only what their account is entitled to. That is a permission boundary in the retrieval layer rather than a prompt instruction, for the same reason as everywhere else on this site: a prompt is not a security control.
Index the artefacts that are correct by construction. The docs site is a secondary source.
30-minute technical call · no deck
What we built, what stage it is at, and a link to the live thing wherever there is one.
yourOS is an operating system with an AI at its heart. You talk to it like a person, out loud or typed. It makes your calls, plans your days and works on your projects with a crew of agents, on your own private server. Our own product, built from the first commit; the waitlist is open.
Website, backend and app assets for Sonora, a free AI sound-therapy app on iOS and Android published by Cognitive AI.
Brand, website, prototype, apps on five platforms, the AI backend and the algorithm-intelligence pipeline for Podswap, a social growth engine that runs without a human in the loop.
In closed beta: Roxy, a private AI assistant with permanent memory running on infrastructure the user owns. Brand, site, product, backend and conversational design.
Live at coherence.com: brand identity generated with AI agents we directed, the motion system and website for the group behind Sonora, AboutAI, WakeUp and MudShadows. Agent work remains in build.
Live at domainbooth.com for DomainBooth, a premium domain brokerage: a new animated mark, every page redesigned and rebuilt with designed mobile layouts, and a custom CMS for its sales record, featured names, press and enquiries.
Apps, platforms and campaigns for these teams, long before the AI work. Every one is written up on the work page — what we did, and where our part ended.
