Skip to content

audit-workflow.md

Latest commit

 

History

History
27 lines (19 loc) · 1009 Bytes

audit-workflow.md

File metadata and controls

27 lines (19 loc) · 1009 Bytes
Raw

Audit Workflow

BotV8 audit work should stay practical: run an authorized page flow, collect local evidence, compare behavior, and review the result.

Workflow

  1. Select a profile family and runtime policy.
  2. Run the approved page or request flow.
  3. Record browser signal families touched during execution.
  4. Compare the result with the expected profile behavior.
  5. Save a local report for QA, release review, or support triage.

Report Shape

Public-facing environment report examples should use high-level categories:

  • runtime state
  • locale and timezone
  • graphics and media
  • storage and session state
  • request context
  • timing behavior
  • navigator state

Review summaries can add touched signal families and a local verdict as a separate sanitized file. Keep the runtime report schema unchanged when it comes from env.report().

Reports should not publish customer traffic, credentials, profile internals, reusable test logic, sensitive comparison values, or private environment paths.