# Docs

> The Assure documentation, rendered from the Assure repository at a pinned commit.

**The docs.**

- [Quick start: the GitHub Action](/docs/quickstart-action) — Known-vulnerability scanners check your code against a list of what has broken before. Assure checks whether the way your code meets the foundational software it runs on stays inside a regime that can be shown safe and r
- [Quick start: the API](/docs/quickstart-api) — The API runs the checker on Symbolia's server. The Assure GitHub Action is a client of this API. You send collected files. You get back a verdict.
- [First run: the Action](/docs/first-run-action) — This page gets a first run to a verdict. The full reference is QUICKSTART-ACTION.md.
- [First run: the API](/docs/first-run-api) — This page takes you to a first verdict from the HTTP API with the postgresql-observed-baseline profile, which needs no declaration. The full reference is QUICKSTART-API.md.
- [Declarations](/docs/declarations) — A declaration is to your database's access rules what a Playwright test is to your UI — a file in your repo, run on every PR.
- [Reading a verdict](/docs/verdicts) — A check writes one JSON file. The Action writes it at its output path. The API returns it as the response body.
- [Your data](/docs/data) — The collector runs in your runner. It connects as your collection role and runs a fixed, published set of SELECT queries. The collector asks for a read-only session. A pooler may not pass the request on. The collector ru
- [What a verdict claims](/docs/scope) — This page describes the claims of postgresql-observed-baseline; the declared profile is below, the HTTP profile's scope notes are in the Action quick start, and what each served profile never detects is listed per profil
- [First-line samples](/docs/first-line-samples) — The first line of the job summary, word for word, as the serving path writes it for each case, and the sentence under it that says what it means. Each line comes from recorded readings, or from recorded readings changed 
- [MCP](/docs/mcp) — The Assure API as five tools. An agent — Claude Code, Codex, Cursor, or your own — calls them the way it calls any tool and reads the verdict as JSON. One command installs it. Your key stays in a file on your machine.
- [The Action README](/docs/readme-action) — Assure checks the software your code runs on. From your own GitHub Actions workflow it reads your PostgreSQL server or your site's HTTP responses and tells you, obligation by obligation, what holds, what is disproven, an
- [Beta tester brief](/docs/beta-tester-brief) — You administer one self-hosted PostgreSQL server, major 14 to 18, and you can run a GitHub Actions workflow that reaches it.
- [Fixtures](/docs/fixtures) — Every fixture committed under tests/ and docs/ in a layout serve/devfixture.py reads (a directory holding raw/, or a repository directory holding declaration.json) is either tabled below or named, with the reason, under

- [Skills](/skills)
- [Measurements](/figures)
- [Changelog](/changelog)
- [Status](/status)
- [OpenAPI](/openapi.json)
- [llms.txt](/llms.txt)