Skip to content
PlatformModulesIndustriesSecurityPricingInsights

Capability evidence

Count verified requirements, not marketing bullets.

We do not publish a universal feature count. Names, editions, dependencies, configuration, and production readiness change; the current written matrix controls.

For each requested capability

  • Record the product release, edition, environment, owner, and evidence date.
  • Describe inputs, outputs, permissions, approvals, errors, audit events, accessibility, retention, and deletion.
  • Identify integrations, providers, infrastructure, customer dependencies, and excluded use.
  • Link documentation, configuration, automated tests, and rendered acceptance evidence.
  • State whether it is available, configurable, custom, planned, unavailable, or blocked—and who approved that status.

For AI-assisted capability

Add model identity, data routing, prompt and tool scope, provider terms, evaluation set, error and bias thresholds, human review, correction, monitoring, incident handling, and kill or fallback behavior.

Review evaluation areas

Necessary technology is always active because it provides security and remembers this choice.