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 |
| Operator evidence review guide |
Reviewing evidence bundles, dashboards, and report-only findings before deciding the next guarded action. |
It assumes the core operator workflow and evidence vocabulary are already understood. |
| Release-readiness evidence handoff |
Preparing or reviewing a release-readiness handoff across evidence producers and consumers. |
It is a specialized handoff contract rather than a first-run guide. |
| 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 |
| Upgrade next commands |
Converting an accepted upgrade checkpoint into the next bounded operator commands. |
It is a follow-up execution aid tied to upgrade work. |
| Next 10 follow-ups |
Reviewing an ordered backlog of subsequent operational improvements. |
It is planning material rather than a stable operator contract. |
| 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. |
| Real workflow operations |
Studying realistic workflow-operation scenarios and guarded remediation boundaries. |
It supplements, rather than replaces, the recommended CI and operator paths. |
| Operations execution checklist |
Running a structured checklist for an established operations program. |
It is program execution material, not first-use documentation. |
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.