Generative Metrics logo
Checking…Create account

Audit observation inventory

What is recorded, separated by protocol layer, before any finding or verdict is derived.

Observation is not interpretation

32 checks · 6 layers

Direct artifacts, derived observations, findings, remediation instructions, and later verification are separate records. That separation is what makes the result inspectable — by you, by your client, and by your finance team.

Layer 1

6 checks

Acquisition evidence

  • Requested URL and final URL
  • HTTP status and bounded redirect chain
  • Declared media type and bounded byte length
  • Allowlisted response headers with other header names redacted
  • Full or prefix SHA-256 scope and truncation state
  • Sitemap artifact: presence, bounded byte length, document validity, listed URL count, and newest lastmod

Layer 2

5 checks

Policy evidence

  • Documented actor identity and purpose
  • Policy applicability for that actor
  • Matched robots group and selected rule
  • Allowed, disallowed, no matching rule, no policy file, or indeterminate
  • Required versus informational profile status

Layer 3

5 checks

Representation evidence

  • Raw HTTP artifact
  • Browser-rendered DOM artifact
  • No-JavaScript DOM artifact, with missing capture reported as incomplete
  • Mechanical hash and byte comparisons
  • Explicit statement that semantic equivalence was not evaluated

Layer 4

5 checks

Extraction evidence

  • Raw and rendered main-content extraction outcomes
  • Word counts and content hashes without persisted page text
  • Raw-to-rendered word ratio
  • Material deficit threshold and minimum rendered-content condition
  • Parser failure or abstention state

Layer 5

6 checks

Structured-data evidence

  • JSON-LD blocks found, parsed, and failed
  • Supported schema types in raw and rendered representations
  • Schema present only after browser rendering
  • Bounded checks for selected name, headline, and description properties
  • Raw-versus-rendered type presence and bounded Organization identity fields as booleans
  • No automatic defect when structured data is absent

Layer 6

5 checks

Date evidence

  • Strict ISO date and timezone validation
  • Supported meta, JSON-LD, time-element, and HTTP header sources
  • Contradictory and out-of-range declarations
  • No stale/fresh grade
  • No defect inferred from an undated page
Create accountReview proof contract