Protocol resources
Crawlers and access.
An explicit policy.
This website’s choices for automated crawling, multilingual reading and documentation access. An explicit policy with a defined scope.
01 / This website’s choice
Open access.
To documentation.
The public website currently publishes one robots.txt rule for all agents: Allow: /. That file does not distinguish search crawlers, training crawlers and agents acting at a user’s request.
User-agent: *
Allow: /robots.txt ↗ · TS42 · Agent governance →
This choice describes the crawling signal. It is not a contractual agreement covering every use of content: protocol wording remains under CC BY 4.0 and other assets retain their notices.
02 / Read and find
Two languages.
The same source.
French and English have separate URLs and reciprocal links. For unmatched languages, x-default explicitly identifies the English version of the same page. No automatic language-based redirect is imposed.
Each control is also available in Markdown. llms.txt is a documentation index; it grants neither additional access nor citation priority.
03 / HTTPS transport
An HSTS policy.
An explicit scope.
Enabled on 28 October 2026: the public website sends the Strict-Transport-Security header on HTTPS responses from its canonical host, with an initial one-day duration.
Strict-Transport-Security: max-age=86400- Scope
- Only the tsep-protocol.org host, on its HTTPS responses. The application subdomain is managed separately: no includeSubDomains.
- Initial duration
- One day, for an initial observation phase. A longer duration will be decided after checking certificates, redirects and embedded resources. No preload is planned at this stage.
- Verification and review
- HTTP/HTTPS access, host variants, certificates, errors and resources are checked at publication. Received headers and the activation date are retained. Review these points before increasing the duration.
An HSTS policy received over HTTPS asks the browser to reuse HTTPS for this host for the stated duration. Without preload, it does not protect the very first HTTP request before the policy is received.
Responsible for activation: Edikka. This policy is not a complete TS37 assessment. TS37 ↗ · MDN · HSTS ↗
04 / The scope
A declared signal.
Usage to verify.
This policy covers tsep-protocol.org. It does not describe TSEP Control’s access rules, accounts or dossiers. Local previews remain non-indexable.
Allowing crawling establishes neither an agent’s visit or identity nor its compliance with the policy. Those questions require their own observations and logs. A policy change should identify the agents, their purposes and relevant mechanisms.
Responsible publisher: Edikka. Policy documented on 28 October 2026. Report a problem →