Authoritative source systems
Read-firstThese systems keep their own authority. LeadershipOS reads certified context and never overwrites the authoritative fact.
- Perfect HRPeople and approved assignment facts
- SIS / RegistrarStudent records and academic transactions
- ERP / FinanceLedger, budget and collection transactions
- CRMProspect and customer relationship records
- DMSDocuments and controlled attachments
- Identity providerSSO, MFA and lifecycle signals
Intelligence and assurance
BoundaryAnalytical certification and enterprise publication stay outside LeadershipOS by design.
- Central MISCertifies analytical truth
- Central DashboardPublishes enterprise KPIs
- CEPAOIndependently assures evidence
Connector rules
Read-first, reconciled, and honest about state.
A connector is only as trustworthy as what it discloses about itself.
APIs, events and MCP contracts
Versioned contracts with scopes, tenant bounds, correlation IDs, idempotency and replay. No direct database writes.
Read-first posture
Write-back is disabled by default and requires separate approval, a named owner and a rollback rehearsal.
Reconciliation and connector health
Every surfaced figure carries source, period, evidence grade and freshness. A degraded connector is shown as degraded.
No unverified 'connected' claim
A system is only shown as integrated where verified integration evidence exists. Everything here is currently a mock adapter.
No system on this page is shown as “connected”. Every adapter in the current prototype is a mock, and integration evidence has not been produced or verified.