The self-hosted evidence includes endpoint definitions, condition checks, suite grouping, alerting channels, storage, metrics, and API surfaces. Guardus should preserve those proven primitives while naming them around customer scenarios.

Documentation should teach users to describe a journey first, then attach the technical checks that prove the journey is healthy.

• Endpoint checks cover HTTP, DNS, TCP, TLS, timing, and response validation.
• Condition rules express what healthy means instead of only recording that a request completed.
• Suites connect multiple checks into one workflow-level status signal.

Docs should be structured so they can later become Console help content: create a scenario, configure checks, attach alerts, publish a page, review incidents, and invite teammates.

• Keep examples static-export friendly while the hosted product is not implemented.
• Use roadmap wording for accounts, billing, RBAC, and tenant storage.
• Keep references to self-hosting as evidence, not as the main CTA.