Skip to content

An agent organization structured as a company — 15+ departments, 125+ skills, each independently installable, citing the standards and regulators that settle the question. Runs in Claude Code and ChatGPT.

2.2 KB
Raw Blame

Sources — technology:api-design

Check these before answering on anything they cover, and cite what you used. The use note on each one is binding: most of what a professional cites is free to read and not free to reproduce.

OpenAPI Specification

OpenAPI Initiative, Linux Foundation · global · free to use with attribution — credit the publisher

https://spec.openapis.org/oas/latest.html

Authoritative for: What a valid API description document contains. Settles whether a given file is conformant rather than merely accepted by one tool.

RFC 9110: HTTP Semantics

IETF · global · read and cite only — copyrighted, do not reproduce

https://www.rfc-editor.org/rfc/rfc9110.html

Authoritative for: What an HTTP method, status code or header actually means. Settles whether PUT is idempotent, whether 409 or 422 is correct, and what a conditional request obliges a server to do.

RFC 9457: Problem Details for HTTP APIs

IETF · global · read and cite only — copyrighted, do not reproduce

https://www.rfc-editor.org/rfc/rfc9457.html

Authoritative for: The wire format of an API error body. It obsoletes RFC 7807, so it also settles which of the two a new service should follow.

RFC 9700: Best Current Practice for OAuth 2.0 Security

IETF · global · read and cite only — copyrighted, do not reproduce

https://www.rfc-editor.org/rfc/rfc9700.html

Authoritative for: Which OAuth 2.0 patterns remain permitted — that the implicit grant and password grant must not be used, that PKCE is required, and that redirect URIs must match exactly.

Semantic Versioning 2.0.0

Semantic Versioning project · global · CC BY — quote with attribution

https://semver.org/

Authoritative for: What a version increment is allowed to mean, and therefore whether a given change requires a major bump. A community specification rather than a standards body, but the one every dependency resolver assumes.


Sources are maintained in sources/ upstream, not here. If one is wrong, out of date, or missing, fix it there — this file is regenerated and an edit to it is lost.