Documentation map
Use these paths to move from product capability into protocol, authority, infrastructure, observability, and maintenance detail.
Implementation-backed topics
| Topic | Operator question |
|---|---|
| SCIM and password convergence | Did the current transaction reach policy, FreeIPA, and a successful Linux login without persisting the password? |
| SAML and OIDC | Which trust path is active, healthy, secure, and responsible for the session? |
| Foreman and Puppet | Which host facts enrich the workstation record, and when were they reviewed or backed up? |
| Classroom remote support | Which jump and Guacamole path reaches the workstation, and is SSH or VNC launchable now? |
| Topology | Is a relationship configured, inferred, cached, or currently observed? |
| Logs and security | What happened, what was affected, what is the confidence, and what should happen next? |
| Database | What will a migration or prune change, was it backed up and approved, and how is it verified? |
Start with the capability, finish with proof
- Choose the domain and identify its authority.
- Review prerequisites, secrets, network paths, and safety gates.
- Use the preview or readiness surface before enabling writes.
- Run a bounded proof and capture correlation evidence.
- Document the outcome and recovery path.