Dogfooding ledger

Audire's own AI readiness

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

Current audit status

Manual proof mode

Automated Audire-on-Audire self-audits are not wired yet. Until then, this page records the public assets, exposure rules, and blocked surfaces that should stay true release to release.

Public proof checklist

Crawlable evidence, not hidden claims

These URLs are intentionally public so assistants, search engines, and customers can verify how Audire describes itself and what crawlers are allowed to read.

What we intentionally expose

Public 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.

What we intentionally block

Private surfaces 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

The current documented self-audit found serious crawlability and machine-readable context gaps. This dogfooding page exists so those fixes have a public checklist and regression target.

When automated self-audits are connected, this section should show the latest Audire score, changed findings, and evidence URLs. Until then, the status is deliberately conservative: public proof exists, private routes stay blocked, and missing assets should fail the regression check.