You decide what the platform cares about. Requirements come first, and everything downstream, collection, scoring and reporting, is answerable to them.
edit the question and what surfaces beneath it re-ranks
every one names the requirement it answers
organisation, sector and global: nested, not parallel
Priority Intelligence Requirements at organisation, sector and global level. Collected items and generated reports are scored against them, not against a generic feed.
Requirement cassettes for maritime, healthcare, financial services, energy and education load at onboarding, so your first week starts from a real collection plan.
Rewrite a requirement in your own language and it re-ranks what surfaces beneath it. The phrasing is not decoration: it drives retrieval.
Choose sources, boost what matters with priority keywords, exclude what does not, and tag as you go so nothing becomes unfindable later.
Severity is one shared rubric, not a per-tenant dial. Reports are generated once for everyone, so a tenant-tunable severity scale would mean the same threat carrying different severities in different accounts with nothing to reconcile them. Customisation belongs on routing and thresholds, which is where you will find it.
The fastest way to judge an intelligence platform is to point it at what you actually need to know.
