Compass is aggregate by default, reads usage and metadata signals (never the content inside your tools), keeps an audit-friendly trail, and — in regulated verticals — outputs bands, never a single hard score on a person. Your data stays under your contracts; every decision stays with a human.
Aggregate only · signals not content · audit trail · your data, your contracts · every decision stays with a human.
Compass’s data boundaries are architectural, not policy documents. The system cannot produce an individual hard score because the data model doesn’t support it. The system cannot read document content because the integration layer has no access to it.
These are properties of how Compass is built, not promises that depend on configuration being right.
Hard data boundaries
Regulated-vertical posture — what Compass outputs
In regulated verticals — healthcare, insurance, financial services — Compass is configured to output only banded team distributions. The data model has no field for an individual numeric score and cannot be reconfigured to produce one without a deliberate architecture change.
Every decision — hiring, performance, pay, compliance action — stays with a human. Compass is decision-support. It surfaces direction; your team makes every call.
Aggregate by default, signals not content, audit-friendly trail, RBAC, your data under your contracts. In regulated verticals: bands only — 0 individual hard scores by design. Compass is decision-support; every decision stays with a human.