Understand the product through evidence, not only through the interface.
Technical, methodological and operational documentation for M2 Visibility users, enterprise teams, Security, Procurement and developers.
Getting started
1 articles
Methodology
3 articles
AIVM-1.0 measurement framework
Five measurement modes separate spontaneous recall, current evidence, competitive comparison, reputation and purchase intent so incompatible experiments are not collapsed into one story.
AVS-2.0: AI Visibility Score
A versioned composite index that summarizes visibility without hiding its five components: Presence, Share, Position, Evidence and Consistency.
STATS-1.0: statistical confidence
Cluster bootstrap, effective sample size, execution completeness and confidence grades make the difference between exploratory signal and stronger evidence explicit.
Intelligence
7 articles
SRCI-1.0: Source Intelligence
Understand which sources support AI answers, how concentrated the evidence ecosystem is and where cross-model consensus emerges.
Prompt Intelligence
Treat questions as a strategic portfolio by preserving intent, persona, funnel stage, priority and stable identity for comparable measurement.
PDI-1.0: Prompt Demand Intelligence
Discover gaps in the question portfolio, prioritize observed demand and govern new prompts before they enter a MeasurementRun.
WACI-1.0: Web & AI Crawler Intelligence
Audit discovery, crawlability, indexability, semantic structure, AI readability and observable agent policies across owned or authorized sites.
BKG-1.0: Brand Knowledge Graph
Model entities, aliases, relationships, claims and evidence to build a governed semantic representation of the brand.
NPI-1.0: Narrative & Perception Intelligence
Compare what the brand declares in the Knowledge Graph with what AI models state in observed responses.
TAEO-1.0: AI Site Audit & Technical AEO
Turn crawler signals into a prioritized technical audit, remediation plan and post-implementation verification loop.
Operations
3 articles
Recommendations, alerts and automation
Turn signals into actions with priority, ownership, recurrence, evidence and later verification.
Observability, readiness and launch control
How the platform measures its own health, blocks unsafe launches and keeps rollout reversible.
Diagnostics and troubleshooting
A practical path for investigating missing models, incomplete runs, low confidence, webhook failures and unavailable Enterprise controls.
Enterprise
5 articles
Enterprise operating model
Tenancy, entitlements, identity, billing and separation of duties for operating M2 Visibility as a corporate capability.
AUD-2.0: audit and evidence integrity
Append-only events, payload reconstruction, cryptographic chaining, retention, legal hold and periodic integrity verification.
INT-1.0: Integration Hub
Governed control plane for connecting data, collaboration, CRM, content and data platforms to M2 Visibility without confusing connector availability with real authorization.
SSO, JIT, group mapping and SCIM
What EID-1.0 implements, what depends on external configuration and how enterprise identity connects to role and scope.
Plans, entitlements, usage and billing
How ENT-1.0 and BILL-1.0 separate technical capability, limits, price, subscription, usage and reconciliation.
Security
6 articles
Security architecture
Defense in depth across authentication, backend authorization, RLS, tenant scope, secrets, API controls and auditable evidence.
Incident response
A preservation-first workflow to detect, classify, contain, recover, communicate and learn from incidents.
Data retention and legal hold
How technical retention, evidence preservation and legal obligations should be managed without assuming one retention period fits every data class.
Privacy and data handling
Technical minimization and scope principles, separate from the formal legal Privacy Policy that must be approved before final commercial launch.
Continuity, backup and recovery
Technical continuity principles without publishing RPO, RTO or SLA values that have not been formally approved.
Suppliers, subprocessors and data flow
How external dependencies should be governed and why a technical provider catalog is not the same as a legal subprocessor register.
Developers
2 articles
Architecture
3 articles
Platform architecture
How M2 Visibility separates the public experience, authenticated application, Enterprise control planes, operational data, integrations and audit evidence.
Measurement lifecycle
From prompt to insight: states, jobs, completeness, calculation, evidence and the criteria that make a MeasurementRun interpretable.
Model and provider governance
How models are enabled, associated with capabilities, used in methodologies and treated as mutable dependencies of the experiment.
Reference
1 articles