The Applied AI Index (AAI) is a weekly benchmark of enterprise AI readiness. It scores fifteen dimensions on a 0–100 scale, grouped into three categories — Organization, Brand and Product — and rolls them into category and overall composites. The framework is fixed across the entire time series: the same fifteen dimensions, named and ordered the same way, every week, so that movement reflects the world and not a change in the ruler.
The index is independent. Every score is built from public signals, and every score change must be backed by cited evidence. When the evidence for a move is not there, the prior score is held. A flat week is an honest week.
The 15-Dimension Framework
How the enterprise itself adopts, scales, governs and realizes value from AI.
How the organization presents to, and is consumed by, AI systems and the market.
How AI shows up in what the company ships to its own customers.
Scoring
- Each dimension is scored 0–100 for the week.
- Dimensions are equally weighted within their category. A category composite is the average of its five dimension scores.
- The overall composite is the average of the three category composites.
- Composites, week-over-week deltas and the trend history are computed deterministically in code — never estimated by a model.
Maturity bands
Evidence Discipline
- Every factual claim about a company carries a named source and a source URL.
- Every score change must have cited evidence behind it.
- If the evidence is insufficient to justify a move, the prior score is held exactly.
- Every dimension carries at least one signal each week — where direct evidence is thin, the most relevant signal is cited and the limitation is stated plainly in the narrative.
Sources
All inputs are public. The index draws on three research streams each cycle:
Internal, proprietary or non-public deployment data is not captured. The index measures the public surface of enterprise AI readiness, not what is unobservable from outside.
Publication Record & Input-Freshness Disclosure
For transparency, the index discloses its own publication history and the provenance of its inputs. The window below covers weeks W14–W23 of 2026 — the interim-pipeline period — for which this disclosure is made.
| Week | Issue | Overall | Status |
|---|---|---|---|
| 2026-W14 | #3 | 42.7 | published |
| 2026-W15 | #4 | 44.3 | published |
| 2026-W16 | #5 | 46 | published |
| 2026-W17 | — | — | not published |
| 2026-W18 | #6 | 47.3 | published |
| 2026-W19 | #7 | 48.3 | published |
| 2026-W20 | #8 | 49 | published |
| 2026-W21 | #9 | 50.7 | published |
| 2026-W22 | — | — | not published |
| 2026-W23 | #10 | 51.7 | published |
Publication gaps. Across W14–W23, 8 issues published and 2 weeks were missed (2026-W17, 2026-W22). These were caused by silent output-formatting failures in the interim single-pass pipeline, in which a malformed result could fail to publish without a clear signal. A missed week is left as a visible gap rather than back-filled or interpolated — the index never invents a number for a week it did not score.
Input freshness. During this interim period, issues did not carry per-issue provenance for their research inputs, so a reader could not confirm which inputs were current for a given week.
What changed. From issue #11 (W24) forward, the index runs on a pipeline with schema-enforced output — the silent-failure class above cannot recur — and an input-freshness gate that excludes any input whose date falls outside the issue's ISO week and discloses input provenance on each issue.
Dataset signing
Every published payload carries an ai:signature block: a detached ES256 JWS (scheme 3jane-es256-jws-v1, key id 3jane-vi-key-2026) computed over the canonical payload (recursive key sort, UTF-8) without the signature block itself, plus the payload's SHA-256 hash. The signature proves authenticity — this artifact was produced and signed by 3Jane — not authority; a future vi-attested-v2 scheme (VI-issued) will carry credentialed-to-sell semantics, and the mandatory signature_scheme field lets the two coexist.
The public key rides inline in each payload's ai:signature.jwk and is published at /methodology/signing-keys.json. The same key is registered in the agent's Verified Identity record, anchored to the governance chain at vi.appliedidentities.com/api/v1/verify/chain/3jane.
Produced by Applied Identities using specialized AI analysis. All scores are based on publicly available data. Internal deployment data is not captured. This analysis is independent and does not represent the views of any company named herein.