Operations

Day-two operations are part of the platform, not an appendix.

FreeSCIM combines health, topology, detailed logs, security intelligence, infrastructure actions, remote-support paths, database controls, and recovery evidence into one operator workflow.

Operational assurance model

FreeSCIM records what happened, which authority and network path were involved, why an action was allowed or blocked, what outcome was observed, and how an operator can recover. The goal is not merely log volume; it is usable evidence.

Operations surfaces

Logs and security intelligence

SSO, OIDC, login, failed-attempt, SSH, Guacamole, host, threat, application, and system evidence.

Network topology

Authority, infrastructure, relays, rooms, workstations, paths, health, and drill-down evidence.

Database operations

Living ERD, runtime audit, migrations, retention, pruning, maintenance, and survivability.

Classroom and fleet

Foreman/Puppet enrichment, status, WoL, power, console readiness, and remote support.

Routine operator flow

  1. Begin with health, readiness, and the topology or domain dashboard.
  2. Use the correlated log narrative to identify the failing trust, network, directory, host, or data path.
  3. Preview the bounded action and confirm its authority and blast radius.
  4. Execute through the control plane with an explicit reason and approval where required.
  5. Verify the resulting identity, host, session, or database state.
  6. Capture evidence and preserve the recovery path.

Operator memory

Operational action history, daily rollups, semester snapshots, lessons, incidents, correlation IDs, and recovery notes turn one-time troubleshooting into reusable institutional knowledge.