Skip to content

Allow AI use signals in docs robots.txt - #154

Merged
HDauven merged 1 commit into
mainfrom
agent/allow-ai-content-signal
Sep 30, 2026
Merged

HDauven merged 1 commit into
mainfrom
agent/allow-ai-content-signal

Conversation

@GeorgianDusk

Copy link
Copy Markdown
Contributor

Summary

The docs crawler policy permits indexing but does not declare how AI systems may use the content. This adds a wildcard Content-Signal directive that permits search, real-time AI input, and model training.

The regression test parses the generated dist/robots.txt and verifies that the static build publishes all three affirmative preferences unchanged from the source file.

Validation

  • node scripts/verify-package-release-ages.cjs --days 7 — 469 lockfile entries passed
  • npm audit signatures — 362 verified registry signatures and 85 verified attestations
  • npm rebuild esbuild — passed
  • npm run verify — 72-page production build passed, all internal links passed, 5/5 tests passed
  • git diff --check — passed

Deployment

This PR changes source and tests only. docs.dusk.network/robots.txt will expose the new signal after merge and deployment.

@HDauven
HDauven marked this pull request as ready for review September 30, 2026 15:57
@HDauven
HDauven merged commit 6beb20c into main Sep 30, 2026
1 check passed
@HDauven
HDauven deleted the agent/allow-ai-content-signal branch September 30, 2026 15:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants