About these docs

This site lives at docs.platypus.tickets, built and deployed straight from the same repository as the product itself. It's reference documentation, not marketing. A few mechanics keep it honest:

• It documents current behavior. Where the product has a quirk (say, what your subscription does and doesn't control), the docs say so rather than describing the system we'd like to have.
• API examples can't drift. Every JSON example in the API section is a fixture file asserted byte-for-byte against real API responses by the Platypus test suite. If the API changes, the tests fail until the examples are regenerated.
• Coverage is enforced. Each documented feature is tied to the capability specs that define Platypus. A new capability can't ship without either a docs page or an explicit, justified exemption — the docs build fails otherwise.
• Every build says what it documents. The footer (and /build-info.json) carries the exact source commit these pages were built from.
• LLM-friendly. The full content is published as /llms.txt and /llms-full.txt for AI tools to consume.

Found something that doesn't match the product? That's a bug in the docs — report it via a venue's contact page.