Scan & Surfaces Concept Page + Docs Gaps

The scan is the product's entry point — every user runs it first. Surfaces are the headline feature for monorepos — they're what makes the pipeline per-surface instead of project-wide. Application shape is visible in every scan header. But none of these have a concept page. A developer scanning their monorepo sees "3 surfaces" and "web-app" with no reference explaining what either means, how they were determined, or how they flow through the pipeline.

verdict PASSscore 19 / 19findings 4 (0 risk · 1 debt · 3 obs)duration 28mrejection cycles 0shipped May 24, 2026surface website

Pipeline timeline

Intent to proven code in 28m across Think, Plan, Build, and Verify.

Think
2m
Plan
7m
Build
8m
Verify
4m

Assertion ledger

19 claims, each independently verified. Showing 8 — show all →

IDSaysMatcher
A001A scan concept page exists with proper frontmatterverifiedok
A002The scan concept page explains what the scan detectsverifiedok
A003The scan concept page explains surfaces without naming the four detection signalsverifiedok
A004The scan concept page explains application shapeverifiedok
A005The scan concept page explains how surfaces cascade through the pipelineverifiedok
A006The scan concept page includes a concrete cascade example with a surface-specific test commandverifiedok
A007The scan concept page does not reference detection signals by numberverifiedok
A008The scan concept page ends with navigation cards pointing to the pipeline conceptverifiedok

Findings 4 total

debtwebsite/content/docs/guides/configurability.mdx→ closed
Surface management section contradicts itself on path field protection
obswebsite/content/docs/concepts/scan.mdx→ closed
scan.mdx at 80 lines sits at the minimum of AC7's 80-120 range, below spec target of 90-100
obswebsite/content/docs/guides/using-ana-setup.mdx→ closed
Builder converted existing raw apostrophe to ' in unchanged setup guide line
obswebsite/content/docs/guides/configurability.mdx→ closed
Configurability adds third command (build) not in spec mockup

Integrity seal

scopesha256:c377b03a1dbc5...
contractsha256:6ce6422fdc85b...
plansha256:8ded60281997a...
specsha256:690c288cab32d...
build-reportsha256:19fcbfa23be57...
build-datasha256:5dd011ad2ef30...
verify-reportsha256:58f5edf745db1...
verify-datasha256:b12e6e50655a8...
audit cmd$ ana proof audit docs-scan-surfaces-concept   → all hashes match