Witness coverage

Witness coverage report (pack-wide)

Anthropic Counsel — Cloudflare bundle preview checklist (v1)
Anthropic Legal Bearings Pack AI governance & counsel workflows
Overview · Navigation

Anthropic Counsel — Cloudflare bundle preview checklist (v2)

This checklist is a lightweight companion for staging a new Anthropic Counsel Cloudflare bundle. It is meant to be used by counsel, engineers, or reviewers who want a repeatable way to verify navigation, headers, and cross-links before a pack goes live.

It encodes the intent of the nav_overlay_guard_v2 and bundle_preview_guard_v1 rituals into a human-friendly flow. It does not change any legal commitments or policies.

0.1 Pack QA Gates v1 (must-pass before any reship)

These hard gates prevent the failure modes we saw in earlier reships:

  • 🧱 No silent drop: All files listed for the pack exist and are present in the ZIP (fail ship if not).
  • 🧭 Page shell contract: Every counsel-facing HTML page has the global nav banner, theme CSS, and nav JS.
  • 🕹️ Nav interactivity contract: Dropdown nav works (click/tap + keyboard) in FM and Penumbral pages.
  • 🎨 Style language consistency: No page-local CSS overrides reserved global nav classes (e.g., site-header, nav-*).
  • 🧹 Module cloudhop sweep: FM + Penumbral rosters are swept; no “some pages still broken” regressions.
  • 🧩 Nav single source: Global nav snippet changes are made once and propagated consistently.

0. Fast path demo run (5 minutes)

If you’re just validating the bundle’s story and navigation, use this quick path:

  1. Home — Confirm the pack overview renders and the title returns here.
  2. S1 AI Landscape — Confirm nav works and styling matches.
  3. S6 Acceptance Table — Confirm tables render and dropdown nav works.
  4. Foreseeable Misuse index — Confirm dropdown nav works and links resolve.
  5. Penumbral module index — Confirm exec brief + op spec links work.
  6. Welfare handout — Confirm styling and readable typography.

1. Before you start

Make sure you have the following information handy:

  • The Cloudflare pack name you are previewing (for example, anthropic_counsel_cloudflare_pack_v1_20).
  • The frontend manifest version (for example, anthropic_counsel_frontend_manifest_v7.json).
  • The current full record file (for example, counsel_research_full_record_heavy_2025-11-03_v457.full_record.json).

In a notebook or internal system, record a short log entry that references these versions. This satisfies the structural requirement of the bundle_preview_guard_v1 ritual.

2. Core navigation and header checks

Confirm the pack title in the banner acts as a Home link (returns to index_v9.html) from every module page.

For the candidate Cloudflare pack, open the following pages in a browser and confirm:

  1. Nav renders as pills, not curtains.
    The main nav should appear as discrete, clickable pills. When opened, dropdowns should expand in place and not cover the entire page as an opaque overlay.
  2. Hero header is consistent.
    The hero banner (logo, page label, short purpose text) should look visually consistent across the modern surfaces and should not obscure body text when you scroll.
  3. Segment labels match their pages.
    The small segment pill in the hero header (for example, “Penumbral privacy spine · Executive brief”) should accurately describe the page you are on.

Run these checks at minimum on:

  • Penumbral_Module_Index_v9.html
  • Foreseeable_Misuse_index_v11.html
  • Handout_Model_Evals_Welfare_v1_7_v454.html
  • Architectural_Spines_Overview_v1.html

3. Spine-level link checks

For each spine, start from its index or overview page and follow the links through the strategy and deeper layers:

3.1 Penumbral privacy spine

  • From Penumbral_Module_Index_v9.html, follow the “Executive brief” link.
  • From the executive brief, confirm links to the operational spec and acceptance table work.
  • From the index or treasure pack, confirm links to the reasoning journal and counsel usage note.

3.2 Foreseeable Misuse

  • From Foreseeable_Misuse_index_v11.html, follow the link to the legal strategy brief.
  • Confirm the links to the counsel work sheet and acceptance table work and land on the expected pages.

3.3 Model evaluations & welfare

  • From Handout_Model_Evals_Welfare_v1_7_v454.html, follow the link to the welfare strategy brief.
  • From the handout, test the external links to Anthropic’s model welfare research notes.

If any link is broken or points to an unexpected version, note it and update the underlying HTML and manifest before re-building the pack.

4. Recording a preview event

To keep the full record coherent, add a short entry to the project log (for example, append_only_log in the full record) with:

  • The pack name you previewed.
  • The manifest and component-contract versions.
  • The date, and who performed the preview.
  • Any issues found, or “none observed” if the preview passed.

This gives reviewers and future maintainers a concrete trail showing that navigation and cross-links were checked before a bundle went live.

5. Optional deeper checks

For risk-sensitive deployments or demos, you may also want to:

  • Spot-check that citations on the spines and strategy briefs open the correct sections of Anthropic’s public documentation.
  • Confirm that the landing pages for S1–S6 and the Reading Stack point clearly into the spines and do not leave users stranded.
  • Run the preview in multiple browsers (for example, Chrome and Firefox) to catch any browser-specific quirks.