v0.3 · 2026-09-22
| Author | Cody Rose, AIFluency |
|---|---|
| Version | v0.3 |
| Date | 2026-09-22 |
| Instrument | 15-item AI Fluency Rubric, 3 items across each of 5 dimensions |
The author set every level assignment in section 3. None of the 15 items has been independently keyed. See section 5.
3 items per dimension, 15 in total. This is a fixed design constraint, not an outcome of how much content happened to be written: every dimension carries exactly the same number of items, so each contributes equally to the unweighted composite. Equal item count does not establish equal measurement precision.
| Dimension | Items | Item ids |
|---|---|---|
| Awareness | 3 | awareness-6, awareness-7, awareness-5 |
| Instruction | 3 | instruction-5, instruction-6, instruction-7 |
| Verification | 3 | verification-6, verification-9, verification-7 |
| Governance | 3 | governance-4, governance-7, governance-8 |
| Integration | 3 | integration-7, integration-8, integration-10 |
| Total | 15 |
Resolution. A dimension score is the mean of its items. With one item per dimension a score can only take 4 values — 1, 2, 3, 4 — so every person sits exactly on a band and a 3.0 cannot be told from a 3.3. With 3 items it takes 10 distinct values, which is the resolution the product's own copy depends on when it distinguishes a dimension that is nearly Applied from one that has just arrived there.
A majority reading. Three is the smallest odd number greater than one, so two answers agreeing constitutes a majority. Two items can only agree or split, and a split leaves the dimension on a midpoint with nothing to break it.
The boundary is never landed on exactly. With 3 items a dimension score is a multiple of one third, and the composite is a multiple of one fifteenth. A band boundary sits at 1.5, 2.5 and 3.5, and none of them is reachable by either a dimension score or a composite. The rounding rule in section 4 therefore never has to resolve a tie. This is a property of the arithmetic, not a claim about behaviour.
What three costs. Fifteen items rather than five is roughly three times the demand on the respondent. That is the trade being made, and it is the reason the count is not higher.
Withheld from this copy. The level assigned to each option of each item is not printed here. Publishing it openly would make the instrument gameable by anyone who read the page — a score chosen rather than measured — and the whole claim of the product is that the number came from a measurement.
Available to reviewers on request. If you are evaluating the method — a buyer, an advisor, a practitioner asked to key the items, or anyone who needs to check the mapping before trusting a result — write to cody@aifluency.ai and the full key will be sent to you. It is also visible in this document when signed in to an organization account with a leadership role.
What is not withheld: how many items there are and how they are distributed (section 2), how an answer becomes a score and a band (section 4), who has checked the mapping and when (section 5), what the score may be used for (section 6), and every psychometric property that has not been established (section 8). The key is the one part whose publication would change the measurement, and it is the one part that is held back.
Two properties of the key are worth stating without printing it. Every item offers exactly one option at each of the four levels, so no item is weighted differently from another. And the presentation order is deliberately scrambled with respect to level: authoring an item best-answer-first and never shuffling is the most common way a multiple-choice instrument becomes guessable, and it happened here once already. An automated check runs on every build and fails it if any content-free strategy — always pick the first option, always pick the longest — scores above 3.0 on either form.
A dimension score is the arithmetic mean of the levels of the 3 answers given for that dimension. The composite index is the unweighted mean of the five dimension scores, equivalently the mean of all 15 answers. Neither is weighted and neither is transformed.
A band is the word attached to a score. It is assigned by rounding the score to the nearest whole level:
| Score is | Level | Band |
|---|---|---|
| 1.0 to below 1.5 | 1 | Unaware |
| 1.5 to below 2.5 | 2 | Exploring |
| 2.5 to below 3.5 | 3 | Applied |
| 3.5 and above | 4 | Fluent |
A score of exactly 2.5 rounds up, to level 3, Applied. The same applies at 1.5 and 3.5. This is stated because a boundary rule that is left implicit is a rule nobody can check, and because it decides which side of a band a person falls on.
For an individual, the rule is never invoked. No reachable dimension score or composite index is exactly 1.5, 2.5 or 3.5: a dimension score is a multiple of one third and a composite is a multiple of one fifteenth, and no half-integer is either.
This does not extend to aggregates. A department or organization figure is a mean across people, not a mean across items, so it can land anywhere — including exactly on a boundary. Where an aggregate is shown, the band word is derived from the figure as printed rather than from the underlying value, so the number on the screen and the word beside it always agree. Two departments showing the same figure will always carry the same word.
If any single dimension rounds to level 1, Unaware, the band printed beside the composite is held at level 2, Exploring, however high the composite mean is. The numeric score is never altered. Only the word is.
The reason is that a mean hides its worst component. Someone at level 4 on four dimensions and level 1 on Verification averages 3.4 and would otherwise be labelled Applied — reading as broadly competent while being unable to tell whether AI output is true. The rule is deliberately narrow: it triggers only at Unaware, and it holds at Exploring rather than dropping to the floor, because the strength elsewhere is real and the number still shows it.
Where the rule fires, the result page and the report both state that it has fired and name the dimension responsible. A held band is never shown without its reason.
Three further rules withhold a figure rather than print a weak one. No percentile is shown at all: there is no defined reference population (the norm base in the table of what is not yet established), and a percentile against whoever happened to take the assessment would describe early adopters, not a population. Leadership sees no individual’s result at all, and a group — a department, or any future cut by team, role or location — shows its results only once 5 of its people have been measured, on screen and in the evidence pack alike. A larger group is also withheld when showing it would let a smaller one be worked out from the totals. Two measurement rounds are compared only when each has at least 5 responses on the same version of the assessment; a round holding more than one version is marked and never compared. A department shows round-over-round movement only with at least 8 people measured in both rounds, and an organization figure needs 20. No movement smaller than 0.2 is drawn at all.
The floor for reporting a mean is deliberately lower than the floor for reporting movement, because they are different claims. The movement floor is sized for the error on a difference of two means, which is roughly √2 times the error on either one; using it for a single mean withholds a figure that is better estimated than the movement the same rule would draw. The evidence pack made exactly that mistake and withheld three departments the dashboard reported confidently off the same rows.
Neither floor is derived. The standard deviation of this instrument is not established — see section 8 — so nobody can compute the point at which a mean becomes stable. They are conventions, set where a claim stops being obviously unsupportable, and they should be revisited the moment reliability exists.
0 of 15 items have been reviewed independently. Every level assignment in section 3 is the author’s own, and no item has been keyed by anyone else.
An earlier version of this document reported five items as reviewed, on the strength of a note in the source describing the five original questions that way. That note carried no reviewer, no date and no record of a review taking place, and it was incorrect. It has been removed at the source rather than annotated here.
| Item | Dimension | Status | Reviewer | Date |
|---|---|---|---|---|
| awareness-6 | Awareness | Not reviewed | ||
| awareness-7 | Awareness | Not reviewed | ||
| awareness-5 | Awareness | Not reviewed | ||
| instruction-5 | Instruction | Not reviewed | ||
| instruction-6 | Instruction | Not reviewed | ||
| instruction-7 | Instruction | Not reviewed | ||
| verification-6 | Verification | Not reviewed | ||
| verification-9 | Verification | Not reviewed | ||
| verification-7 | Verification | Not reviewed | ||
| governance-4 | Governance | Not reviewed | ||
| governance-7 | Governance | Not reviewed | ||
| governance-8 | Governance | Not reviewed | ||
| integration-7 | Integration | Not reviewed | ||
| integration-8 | Integration | Not reviewed | ||
| integration-10 | Integration | Not reviewed |
26 items were withdrawn across four dates — four on 2026-08-19, two on 2026-08-25, 15 on 2026-09-22 and five on 2026-09-26 — after an outside reading of the bank. They are not administered and are not counted in the 15 above. They are listed because a withdrawal is a break in comparability rather than a tidy-up: a mean for Awareness, Instruction, Verification, Governance or Integration from before those dates is an average over different items than one from after, and any movement claim spanning either date has to say so.
| Item | Dimension | Withdrawn | Answers held | Why |
|---|---|---|---|---|
| awareness-4 | Awareness | 2026-09-26 | 0 | Review found an option keyed as Applied rested on a premise that does not hold: that access to a source proves the answers drawn from it. Replaced by awareness-7. |
| verification-8 | Verification | 2026-09-26 | 0 | Its best answer confirmed that the paper existed, not that it reported the figure being cited. Replaced by verification-9. |
| governance-5 | Governance | 2026-09-26 | 0 | Its Applied answer, protecting one's own chat, could reasonably be the whole right answer, because the stem did not say anyone else was exposed. Replaced by governance-7, whose stem says so. |
| governance-6 | Governance | 2026-09-26 | 0 | Its best answer said pasted data "cannot be pulled back", an absolute the facts do not support. Replaced by governance-8. |
| integration-9 | Integration | 2026-09-26 | 0 | Its two highest options differed only in what they measured, and both measures are sensible. Replaced by integration-10. |
| verification-2 | Verification | 2026-09-22 | 47 | Its level-2 option, softening the claim to "studies suggest", described no behaviour at any level of rubric 2026.09.3. Replaced by verification-8, identical except for that option. |
| awareness-1 | Awareness | 2026-09-22 | 53 | The stem did not say whether the tool was available to try, which a reasonable answer needs to know. Replaced by awareness-6, which says so. |
| awareness-2 | Awareness | 2026-09-22 | 47 | Keyed on an assumption about what the tool could reach that the framing screen explicitly declines to make, so a taker who took the framing at its word could reason to a different answer. Replaced by awareness-4, which makes the tool's reach the question rather than an assumption. |
| awareness-3 | Awareness | 2026-09-22 | 47 | Its intended best answer reasoned from the consequences of an error, which rubric 2026.09.3 places under Governance rather than Awareness, and the stem did not say whether the fraud flag decided claims or routed them to a person. Replaced by awareness-5. |
| instruction-1 | Instruction | 2026-09-22 | 53 | The stem did not say whether the failures had already been examined, and the two readings inverted the item; its intended best answer also included a remedy rubric 2026.09.3 no longer describes. Replaced by instruction-5. |
| instruction-4 | Instruction | 2026-09-22 | 39 | Its intended best answer was certain only if the tool could not reach the figures, which the framing screen declines to assume, and one option described how the tool should behave rather than how to instruct it. Replaced by instruction-6. |
| instruction-3 | Instruction | 2026-09-22 | 47 | The stem did not say how the forty summaries would be used, and the options are judged against that. Replaced by instruction-7. |
| verification-1 | Verification | 2026-09-22 | 53 | The stem did not say who the slide was for, and the intended ordering depended on the stakes. One option was also scored as the weakest for declining to use the output, which rubric 2026.09.3 no longer treats as a verification failure. Replaced by verification-6. |
| verification-5 | Verification | 2026-09-22 | 31 | Measured against rubric 2026.09.3, its intended best answer described the Applied level and a lower-scored option read closer to Fluent. Replaced by verification-7. |
| governance-1 | Governance | 2026-09-22 | 53 | Its intended best answer was to get a policy written, which rubric 2026.09.3 no longer places at Fluent, and the stem left open what data was involved and what standing the taker had. Replaced by governance-4. |
| governance-2 | Governance | 2026-09-22 | 47 | The stem did not say whether any rule covered the tool, and under rubric 2026.09.3 that decides which level the best answer sits at; one option also rested on a false belief about what makes a record identifiable. Replaced by governance-5. |
| governance-3 | Governance | 2026-09-22 | 47 | The stem left the industry and the meaning of exposure open, and one option supplied a contract term the stem never stated. Replaced by governance-6. |
| integration-6 | Integration | 2026-09-22 | 31 | The stem never said the workflow would save the others time, so a taker told to go only on what a scenario states could not tell whether their not using it was a failure; its intended best answer also rested on a principle rubric 2026.09.3 dropped. Replaced by integration-7. |
| integration-2 | Integration | 2026-09-22 | 47 | Its intended best answer rested on handing the tool to someone else, a principle rubric 2026.09.3 dropped, and the stem did not say anyone else took these notes. Replaced by integration-8. |
| integration-5 | Integration | 2026-09-22 | 39 | Its intended best answer was a single-person dependency, which no level of rubric 2026.09.3 describes, and the team's size and reliance on the workflow were unstated. Replaced by integration-9. |
| integration-1 | Integration | 2026-08-25 | 22 | The stem never established that the workflow was relevant to anyone else's work, that anyone had been asked to use it, or that anyone had tried it — while the keyed level-4 option said "fix what broke", presupposing a failure the stem did not license. If the workflow simply did not fit the others' jobs, the correct answer was to stop maintaining it, and no option offered that at any level, so a taker who reasoned correctly had to pick an option they believed was wrong. Reported by an outside reader who took the assessment. Replaced by integration-6, which supplies relevance, invitation, attempt and evidence that non-adoption was not the right call, while still not saying why they stopped. |
| verification-4 | Verification | 2026-08-25 | 11 | Two defects. The stem said only that a report had been summarised, so the keyed option's "nothing in it measures strain" was ambiguous between the summary and the unseen report, and would have been false had the report contained a workload measure. Separately, the level-3 option asserted "it reports averages" when the artifact never said averages — an option resting on a fact the text did not supply. Replaced by verification-5, whose stem bounds the report's contents and whose artifact says "Average claims processing time", making the level-3 option a legitimate and harder distractor. |
| instruction-2 | Instruction | 2026-08-19 | 8 | The prompt withheld two things at once — the audience and the figures — so the item tested two independent failures and scored one above the other on the author's judgment alone. An outside reading found both defensible. Replaced by instruction-4, whose prompt supplies the audience so only the missing evidence is tested. |
| integration-4 | Integration | 2026-08-19 | 3 | Its level-3 option — wiring in this quarter's file names and column headings — reads as plausibly a bigger failure than the single-person restart dependency keyed above it, so an outside reader still could not choose between them. Replaced by integration-5, whose level-3 option is visibly recoverable friction. Retired the same day it shipped, after a second reading. |
| verification-3 | Verification | 2026-08-19 | 5 | The artifact carried two independent errors — an unsupported conclusion about strain, and a causal attribution to the new system — so "nothing in it measures strain" and "it assumes the new system caused the drop" were both defensible criticisms of the same sentence. Nothing principled put one above the other, so the item could not be keyed blind. Replaced by verification-4. |
| integration-3 | Integration | 2026-08-19 | 5 | The level-4 option — routing data through a tool nobody has vetted — is a Governance answer, and at level 4 it made the Integration ceiling reachable only by governance reasoning. It also read as more serious than the single-person restart dependency the item was built around, which is the judgment actually being tested. Replaced by integration-4. |
“Answers held” counts stored answers to that item from counted results only — the same population section 8 reports. Answers given by demonstration and pilot rows are excluded here for the same reason they are excluded there. Withdrawing an item does not delete what was already answered; the rows stay attached to the retired id and still resolve.
What this means for a result. The scores this instrument produces rest entirely on level assignments that one person made and nobody has checked. Until that changes, no individual result should be used to make a claim about a person, and no figure here — individual or aggregated — should be described as a validated measure of AI fluency.
What a score reports is how someone answered these fifteen scenarios, against a scoring key that is withheld from the public (section 3 says who can see it). Aggregating those answers across a department is arithmetic on the same evidence: it inherits every limitation above and adds none of its own. The limitation is in what the number means, not in whether it may be summed. Section 8 sets out what an independent keying would take.
This instrument was not developed or validated for, and is not intended for use in, selection, promotion, compensation, or termination decisions. It should not be used, alone or in combination with other information, to make or support an employment decision about an individual.
It is not a credential. Completing it certifies nothing, confers no qualification, and does not establish competence to any external standard. The level names — Unaware, Exploring, Applied, Fluent — are descriptions of a position on this rubric and carry no meaning outside it.
It is supplementary only. Where it is used at all in a workforce context, it is one input among others, for deciding what to develop and where a team is thin. It has no established predictive validity for job performance, and no evidence is offered here that it has any.
It is a self-assessment. Respondents choose how they would act in a described situation. Nothing here observes what they actually do, and a respondent who wishes to present well can do so.
Adverse impact has not been studied. No analysis of score differences across protected groups has been conducted, because no demographic data is collected and the sample would not support it. The absence of a finding is not evidence of the absence of an effect.
| Path | Stored | Identified |
|---|---|---|
| Public assessment | First name, last name and email address, all required before the first question. The five dimension scores, the self-rating, the option chosen for each item, a timestamp, any organization name the respondent adds, and, for about 48 hours, a one-way code made from their network address. | Yes. The name is stored on the result and the email on the contact record linked to it. The result page’s title, which link previews also show, carries the name and overall score, so anyone with the result link sees both. The full result and report open only in the browser that took it. |
| Report unlock (results from before 27 September 2026 only) | A name and email address, which a respondent who took the assessment before names were required may add later. | Yes, and it links that person to their result from that point on. |
| Workforce assessment | The same scores and per-item answers, plus the account they were taken under and its department. | Yes. Name and email are held on the account. |
There is no retention period. What the account owner sets is a retention REVIEW period — 12, 24 or 36 months, or unset. The distinction is not pedantic. A retention period is a promise that data is deleted when it expires, and nothing in this system deletes anything. Setting 24 months retains nothing for 24 months: it flags what is older than that and waits.
Records past the period are flagged for deletion and nothing is deleted without approval. There is no scheduled job. The dashboard counts the assessments older than the period and offers the account owner one deliberate, confirmed action that deletes those assessments and every answer in them permanently. Accounts are not deleted — this removes measurements, not people.
Unset is the honest default and is shown as unset rather than silently treated as a number nobody chose. Every organization created before this existed has no period until someone picks one.
An organization with a real retention obligation is not covered by this. Enforcement — automatic deletion or anonymisation at expiry, with an audit log of what was removed and when — does not exist, and a review trigger is not a substitute for it. Do not represent this control as meeting a statutory or contractual retention requirement.
Contacts from the public path are outside this. A public result has no organization and no retention owner. The name and email are asked for on the entry screen, before the first question, and are kept until the person asks for them to be deleted.
A workforce respondent is told what leadership can see, and the acknowledgment is recorded before their first assessment. The notice appears twice: on the join screen, before they enter an organization code, and again as a gate that replaces the assessment itself the first time they open it. It names what is visible — their name, department and whether they have completed it, and their results only inside group figures for groups of 5 or more — and what is not, which is their own scores and their answer to any individual question. The gate cannot be scrolled past; the timestamp is written only on an explicit, unticked acknowledgment.
The wording of all three surfaces comes from one place, and each acknowledgment stores the version of the notice that was on screen when it was given. So what a person read and what the record says they acknowledged cannot drift apart, and a change to the wording re-asks everyone holding the older version rather than inheriting their agreement.
Members who predate this have a null timestamp and see the gate on their next assessment. Nothing was backfilled: a consent that was never given is not evidenced by writing a date into a column.
The public path does not show this gate. A public taker has no organization and no leader, so a notice about what leadership can see does not apply to them. Their name and email are held on the result and its contact record, and anyone with their result link sees their name and overall score.
What this still does not do. It does not obtain consent on an employer’s behalf for any purpose beyond this measurement, does not establish a lawful basis under any particular regime, and does not delete anything on a schedule. An organization with its own retention or consent obligation still has to satisfy it; what changed is that this system now records what it was told and when, rather than leaving the whole question to the buyer.
The appendix lists each registered person by name, with their department and whether they have completed the assessment. It carries no one’s results. It is a record of participation: who took part and who has not yet. Every figure elsewhere in the pack is over a group of 5 or more. That is what makes it useful to someone demonstrating that a workforce activity took place — under the EU AI Act, the AI literacy obligation of Article 4.
Coverage is against registered people, and says so in the figure. The pack headlines coverage as “65 of 66 registered” rather than as a bare percentage, because the denominator is the whole meaning of the number and it used to sit in the small print while “98.5%” sat in the table. A share of a self-selected registered subset, headlined without its denominator in a document filed as evidence, is the claim that comes apart the first time somebody checks it against a headcount.
Coverage of the workforce is not established. No organization here records a total headcount that could serve as a denominator — department headcount labels are free text — so the pack claims no share of the workforce at all. Registration is the only population it can count, and a department that registered eight of thirty-seven people will read as fully covered on a basis that says so.
What it is not: it is not a performance record, not an evaluation and not a ranking. It carries the same scope-of-use limits as section 6, and the fact that it is formatted for a compliance file does not extend what its numbers may be used for.
The participation list is personal data: names, departments and whether each person took part. Handle the pack as such — it is generated on request rather than stored, and it should not be circulated more widely than the obligation it answers.
Everything in this section is absent. None of it is estimated, modelled or inferred below, because each has a conventional estimator that would happily return a number from the data on hand and that number would not mean anything.
What it would tell you. Whether the three items in a dimension are measuring the same thing, usually reported as Cronbach's alpha or McDonald's omega.
Why it is absent. No dimension has enough completed item-level responses to estimate it, and an alpha computed on a three-item scale from a small sample is unstable enough to be misleading in either direction.
What would establish it. Item-level responses from a minimum of 200 respondents who completed all fifteen items, computed per dimension over the stored RubricResponse rows.
What it would tell you. How much a single person's score would be expected to move on repeat measurement, and therefore how far apart two scores must be before the difference means anything.
Why it is absent. It is derived from the reliability coefficient and the observed standard deviation. The first does not exist yet, so neither does this.
What would establish it. Internal consistency established first, then the observed standard deviation of the same sample.
What it would tell you. Whether a difference between two rounds reflects a change in judgment rather than recall of the answers the first round disclosed.
Why it is absent. It cannot be separated with the current design. Re-measurement uses the same fifteen items, and the result page shows the taker the strongest answer, and the reasoning for it, on at least one dimension — the weakest one, which is also among the dimensions the included training then targets. So the two effects push in the same direction on the same items. This is a property of the design, not a gap in the data: no amount of collection resolves it while the second sitting reuses the first sitting's items. It is also self-worsening, in that better feedback teaches the keyed response more effectively and makes the change score mean less.
What would establish it. Alternate forms — a second set of items covering the same dimensions at the same levels, administered on the following round — plus evidence that the two forms are equivalent. Absent that, a change score is a change on these fifteen items and should be described as one.
What it would tell you. Whether the same person scores about the same two to four weeks later, with no intervening training.
Why it is absent. It has not been computed for the public assessment. Public results have carried a name and email only since 27 September 2026, and an address typed at entry is not verified, so two results under one address are not certainly the same person. The enterprise path does link results to a user, but no organization has yet been measured twice on the fifteen-item instrument.
What would establish it. A stable respondent identifier, a deliberate retest at a two-to-four-week interval, and a minimum of 50 people completing both sittings.
What it would tell you. Whether independent practitioners, keying the items blind, assign the same levels to the same options as the published key.
Why it is absent. No blind keying exercise has been run, and no item has been reviewed by anyone other than its author. Zero of the fifteen have been independently keyed.
What would establish it. Three to five practitioners keying all fifteen items independently and blind to the published key, then percentage agreement and a chance-corrected statistic over the sixty option-level assignments, with disagreements reconciled on the record.
What it would tell you. What a given score means relative to a defined population, which is what turns a number into a percentile.
Why it is absent. There is no reference population for the fifteen-item instrument. The counts printed in this document are the whole of it.
What would establish it. A defined target population, a sampling method that does not select on interest in AI, and enough completed sittings to report percentiles. Until a defined reference population exists, the product shows no percentile at all.
Counted at the time this page was generated. Only results from people who chose to take the public assessment are included; demonstration and pilot data are excluded by construction.
| Results from real respondents | 63 |
|---|---|
| Of those, carrying a self-rating | 61 |
| Of those, who answered the current 15-item instrument | 9 |
| Item-level answers available for analysis | 870 |
| Organizations holding real workforce data | 0 |
| Demonstration organizations, excluded from all figures | 1 |
The third row is the one that governs everything above it. Earlier results were recorded against a five-item bank or an earlier version of this one, and are not evidence about it. Every property in this section stays absent until this number supports the samples described above.
Result-page feedback discloses the keyed answer for at least one dimension. Re-measurement using the same items cannot distinguish improved judgment from recall of a previously disclosed answer. Alternate forms are in development.
This instrument is not validated for hiring selection, promotion, compensation, or termination decisions.