Documentation map

Use these paths to move from product capability into protocol, authority, infrastructure, observability, and maintenance detail.

Implementation-backed topics

TopicOperator question
SCIM and password convergenceDid the current transaction reach policy, FreeIPA, and a successful Linux login without persisting the password?
SAML and OIDCWhich trust path is active, healthy, secure, and responsible for the session?
Foreman and PuppetWhich host facts enrich the workstation record, and when were they reviewed or backed up?
Classroom remote supportWhich jump and Guacamole path reaches the workstation, and is SSH or VNC launchable now?
TopologyIs a relationship configured, inferred, cached, or currently observed?
Logs and securityWhat happened, what was affected, what is the confidence, and what should happen next?
DatabaseWhat will a migration or prune change, was it backed up and approved, and how is it verified?

Start with the capability, finish with proof

  1. Choose the domain and identify its authority.
  2. Review prerequisites, secrets, network paths, and safety gates.
  3. Use the preview or readiness surface before enabling writes.
  4. Run a bounded proof and capture correlation evidence.
  5. Document the outcome and recovery path.