The 44 controls / TS44
TS44 · AI crawling and agents
Critical content and evidence remain accessible without undocumented JavaScript execution.
Protocol wording · 0.1.0-draft.28 · Documentation view; no website assessment.
Control rule version : 0.1.0-draft.28
Reading guide: start with applicability and required evidence, then read expectations together with their limitations. Understand C, NC, NT and NA outcomes · Prepare a dossier
Expectations and evidence
- Required inputs (protocol identifiers)
- http, html, render, content, intent
- When it applies
- Content intended for declared automated consumers.
- How to check
- Declare critical facts and paths before collection; verify no-JS access, values and exact representation reviews under critical-content-nojs-v1.
- Expectation
- All three rules pass for the no-JavaScript reference client, with qualified delivery, coherent values and bound reviews; no actual consumption inferred.
- Evidence to retain
- Prior plan/review, complete HTTP chains, raw HTML/JSON, attributed rendered tree and bound context reviews.
- Non-applicability
- No content intended for these consumers in scope.
- Limitations
- First bounded HTML/JSON profile, optional Node and supplied rendered evidence; no authenticated CSS visibility, truth, reviewer identity, ingestion or citation. Authored DOM explicitly synthetic.
- Outcome clarification
- C requires all expectations across the declared scope. NC requires evidenced contradiction; otherwise NT. NA requires evidence of non-applicability.
- Reference scope
- Partial scope: Google documents JavaScript rendering for Google Search. This control cautiously extends verification to consumers whose rendering capabilities are not uniformly documented.
Atomic rules
TS44-A01 — Prior critical scope
- Required inputs (protocol identifiers)
- content, intent
- When it applies
- Content intended for declared automated consumers.
- How to check
- Check inventory, no-JS client, planned states/resources and bound review predating captures.
- Expectation
- Complete scope supported by review; bound rejection = fail.
- Evidence to retain
- Prior plan/review, complete HTTP chains, raw HTML/JSON, attributed rendered tree and bound context reviews.
- Assumptions
- Supplied inventory, expected references, context and reviews; scope fixed before capture, unauthenticated evidence.
- Inconclusive outcome
- Missing, late, unbound or incomplete plan/review, or different reference capability.
- Non-applicability
- No automatic atomic exemption.
- Limitations
- First bounded HTML/JSON profile, optional Node and supplied rendered evidence; no authenticated CSS visibility, truth, reviewer identity, ingestion or citation. Authored DOM explicitly synthetic.
TS44-A02 — Delivery path without JavaScript
- Required inputs (protocol identifiers)
- http, html, intent
- When it applies
- Content intended for declared automated consumers.
- How to check
- Check the prior path, explicit resource link if needed, anonymous HTTP and all critical elements.
- Expectation
- Expected destination/response and present elements; any qualified denial, wrong path or absence fails.
- Evidence to retain
- Prior plan/review, complete HTTP chains, raw HTML/JSON, attributed rendered tree and bound context reviews.
- Assumptions
- Supplied inventory, expected references, context and reviews; scope fixed before capture, unauthenticated evidence.
- Inconclusive outcome
- Missing capture, unsupported format/runtime/link/context or incomplete unqualified reading.
- Non-applicability
- No automatic atomic exemption.
- Limitations
- First bounded HTML/JSON profile, optional Node and supplied rendered evidence; no authenticated CSS visibility, truth, reviewer identity, ingestion or citation. Authored DOM explicitly synthetic.
TS44-A03 — Value and context coherence
- Required inputs (protocol identifiers)
- http, html, render, content, intent
- When it applies
- Content intended for declared automated consumers.
- How to check
- Compare qualified values from each representation/rendered state to the plan; review whole critical context with representation-specific bindings.
- Expectation
- Coherent values and reviews; qualified contradiction retained despite other missing evidence.
- Evidence to retain
- Prior plan/review, complete HTTP chains, raw HTML/JSON, attributed rendered tree and bound context reviews.
- Assumptions
- Supplied inventory, expected references, context and reviews; scope fixed before capture, unauthenticated evidence.
- Inconclusive outcome
- Missing/unknown review, rendering, value or attribution; unplanned supplied state or unsupported context.
- Non-applicability
- No automatic atomic exemption.
- Limitations
- First bounded HTML/JSON profile, optional Node and supplied rendered evidence; no authenticated CSS visibility, truth, reviewer identity, ingestion or citation. Authored DOM explicitly synthetic.