Curated advanced docs material map

Use this secondary discoverability surface after the canonical operator path is working. It helps operators find substantive advanced material without turning every historical, specialist, or evidence-oriented page into primary navigation.

This page is not a primary onboarding path. It does not reclassify historical, generated, archived, or report-like pages. Choose a page by the task you are performing, then return to Docs map and organization for the canonical information architecture.

Evidence review and release handoff

Page	Use when	Why it remains secondary
Evidence circuit architecture checkpoint	Inspecting how evidence sources, transforms, and rendered outputs fit together.	It documents a deeper architecture checkpoint, not routine operation.
Evidence graph summary	Understanding summarized relationships across diagnostic and release evidence.	It is an advanced evidence-model reference.
Dashboard and reporting polish	Reviewing how structured evidence is presented consistently across dashboards and reports.	It focuses on presentation quality after the evidence pipeline is already trusted.
Evidence circuit review pack	Performing a consolidated review of the evidence-circuit documentation bundle.	It is a review pack for maintainers and auditors, not the primary product path.

Operations and follow-up

Page	Use when	Why it remains secondary
Operations handbook	Looking up broader operational practices after the essentials guide is familiar.	It is a deeper handbook and intentionally sits behind the daily runbook.

Policy and repository structure

Page	Use when	Why it remains secondary
Policy and baselines	Reviewing how repository policies and evidence baselines constrain automation and review.	It is a governance reference for advanced maintainers.
Repository index engine	Understanding or operating repository indexing and evidence-discovery behavior.	It describes an internal capability rather than a general operator workflow.

Examples and positioning

Page	Use when	Why it remains secondary
SDETKit versus ad-hoc tooling	Comparing SDETKit's governed evidence workflow with loosely connected tools.	It is positioning and evaluation material, not an operational prerequisite.
Examples	Looking for broader command and integration examples after completing the quickstart.	It is a supporting example catalog rather than the canonical first path.

Boundary

This map adds discoverability only. It does not authorize documentation moves, candidate-page edits, exclusion-rule changes, workflow reruns, issue mutation, or merge.