# AI visibility remediation ticket

Version: 1.0
Example status: synthetic; replace every example value before use.
Owner: unassigned
Independent reviewer: unassigned

## Find record

- Observation ID: SYNTHETIC-OBS-001
- Fixed panel version: SYNTHETIC-PANEL-1
- Verbatim prompt: Which inventory platform fits a two-person operations team?
- Declared surface: declared-example-surface
- Collected at: 2026-08-15T09:00:00Z
- Selected hypothesis: the published robots.txt rule blocks the documented search crawler from the target path.
- Evidence that would challenge the hypothesis: the served policy allows the exact affected URL for the documented token, or direct evidence identifies a different delivery failure.
- Credible alternatives: CDN or WAF enforcement, failed identity verification, indexing state, retrieval choice, prompt fit, entity clarity, and ordinary answer variability.
- Evidence artifact: attach the served robots.txt response, exact test URL, response headers, genuine request evidence when available, and raw answer observation.

## Bounded change

- Exact policy URL: https://example.org/robots.txt
- Exact affected content URL: https://example.org/docs/public/widget
- Protected negative-control URL: https://example.org/docs/private/secret
- Expected protected result after change: disallowed for the same documented crawler token.
- Matched crawler token and role: documented-search-crawler; replace with the current first-party name and purpose.
- Matched before rule: Disallow: /docs/
- Provider role under review: replace with the documented crawler and purpose.
- Before version or hash: REQUIRED
- Proposed rule change: REQUIRED
- Why this option: REQUIRED
- Explicit non-goals: do not change unrelated crawler policy; do not promise indexing, ranking, a mention, recommendation, or citation.

## Acceptance checks

- [ ] The production robots.txt response returns the intended status and content.
- [ ] RFC 9309 group merging and most-specific matching were evaluated for the exact test URL.
- [ ] The affected content URL is allowed while the protected negative-control URL remains disallowed under the same served policy and RFC evaluation.
- [ ] The crawler role matches current first-party provider documentation.
- [ ] CDN, WAF, authentication, redirects, and the final HTML response were checked separately.
- [ ] A curl request with a copied User-Agent is labelled a path test, not proof of crawler identity.
- [ ] The final policy, headers, deployment time, owner, and version or hash are attached.

## Deployment, rollback, and corrections

- Change owner: unassigned
- Approver and approval record: REQUIRED
- Deployment timestamp: REQUIRED
- Deployed version or hash: REQUIRED
- Rollback trigger: unintended access, security review failure, or mismatch with the approved policy.
- Rollback steps: restore the saved before version, deploy, and repeat the acceptance checks.
- Corrections contact or record: REQUIRED

## Proof protocol

- Baseline panel version: SYNTHETIC-PANEL-1
- Post-change window: predeclare dates before re-testing.
- Stable cell key: panel version + prompt ID + declared surface + locale + account state + repeat index.
- Raw evidence location: REQUIRED
- Concurrent changes or protocol deviations: REQUIRED; write "none observed" only after checking.
- Keep fixed: prompt wording, declared surface or configured adapter, locale and account state when controllable, matching rules, and exclusion rules.
- Report separately: planned, unavailable, failed, and observed cells; mentions, owned links, other citations, recommendations, competitors, and absence.
- Interpretation: report later observations after the shipment. A change does not establish that the robots.txt edit caused the outcome.