Dogfooding ledger

Audire's own AI readiness

Audire applies the same recommendations to audire.dev that it gives customers: publish crawlable proof, ship model-friendly context, and keep private product surfaces out of crawler paths.

Current audit status

Manual proof mode

We have not wired automated self-audits yet. This page lists the public assets, exposure rules, and blocked surfaces we keep stable release to release.

Public proof checklist

Crawlable evidence you can verify

These URLs stay public so assistants, search engines, and customers can verify how Audire describes itself and what crawlers may read.

robots.txt

Crawler policy for public and private surfaces.

sitemap.xml

Public URL inventory for search engines and AI crawlers.

llms.txt

Concise machine-readable context for AI assistants.

llms-full.txt

Extended context for deeper model review.

llms.txt guide

Public guidance on the file format and how to publish it.

Public pages we expose

Pages that help models explain Audire

Marketing pages that explain the product and category.
Pricing, tools, competitor analysis, and educational resources.
Public report share pages that customers explicitly choose to publish.
Machine-readable llms files and structured page metadata.

Private surfaces we block

Routes that should stay out of AI answers

Dashboard, account, and authenticated workspace routes.
Private audit reports that were not shared publicly.
Admin, billing, and operational back-office surfaces.
Auth flows and audit runner routes that should not become search destinations.

Status copy

Current audit status

Our last self-audit flagged crawlability and machine-readable context gaps. We use this page as the public checklist and regression target for those fixes.

Once we connect automated self-audits, this section will show the latest Audire score, changed findings, and evidence URLs. For now we keep the status conservative: public proof stays live, private routes stay blocked, and missing assets fail the regression check.