Tech4Humanity AtlasGround ZeroCurrent ThemesFuture ResearchGalleryLive Q&ASearch

Ground Zero / AI Sweet Spots

GZ-STORY-018

ASS-2 — Extended/Multi-Site Validation

The meeting began with a number everyone liked and a question nobody could answer. Output had risen. Complaints had fallen. But Dr Arun Bose asked what had happened to judgement, agency and the ability to continue when the system was unavailable.

Dr Arun Bose, a multi-site principal investigator in Sydney, had been asked to decide whether ASS-2 — Extended/Multi-Site Validation belonged in a real programme or in another folder of attractive ideas. The immediate problem was practical: ASS-2 — Extended/Multi-Site Validation was missing or only implied at the taxonomy-subtopic level, obscuring its identity, maturity, evidence and relationship to other research. People affected by the decision could feel the consequences, but the organisation lacked a defensible way to separate benefit from novelty, substitution or hidden burden.

Instead of beginning with a product demonstration, Dr Arun Bose put the research question on the wall: “Do AI Sweet Spots effects replicate across sites, populations, tasks, medication states and cultural contexts?” That changed the room. The question did not assume the technology worked. It asked where, for whom and under what conditions it might work. The proposed hypothesis was equally testable: Calibrated assistance effects will replicate directionally across sites, while optimum intensity and risk boundaries will vary materially by neurotype, expertise, medication state, culture and task. Around it, the team marked assumptions in amber and evidence in blue. Almost everything was amber.

The first trial was designed as a scenario, not reported as a completed experiment. Participants would move through a baseline condition, an active comparison, a calibrated AI condition and a user-controlled condition. They would also face a failure or handback moment, because a system that works only when nothing goes wrong is not a safe system. The organising lens was the Identity → Hypothesis → Protocol → Experiment → Evidence → Analysis → Result → Claim → Translation → Review. Measures would cover immediate performance, understanding, confidence calibration, retained capability, burden, equity and the ability to recover without the tool.

In the scenario, the most revealing moment came after the apparent success. A participant completed the task quickly, then could not explain why the answer was sound. Another worked more slowly but spotted a subtle error and corrected it without assistance. Dr Arun Bose refused to call either result decisive. The contrast showed why the study needed repeated measures, subgroup analysis, delayed follow-up and participant debriefing rather than a single productivity score. It also exposed the risk of measurement intrusion, which could make a polished outcome look more trustworthy than it was.

The team then tested the human boundary. Participants could reduce assistance, inspect sources, challenge recommendations and withdraw. People using non-dominant formats, different languages or accessibility settings were not treated as exceptions to be averaged away. Their experience was part of construct validity. The success gate remained demanding: Canonical identity confirmed; protocol and dataset bound; analysis reproducible; results and limitations verified; claims traceable; governance and ethics satisfied. The failure gate was explicit too: Object remains ambiguous or duplicated; evidence provenance is absent; data cannot be reconciled; analysis is not reproducible; claims exceed evidence.

By the end of the workshop, Dr Arun Bose had no miracle result to announce. That was the point. The evidence state was recorded as “PARTIAL — named validation study recovered; multi-site dataset, recruitment and analysis assets require binding”. The story could therefore demonstrate the decision pressure and the proposed research design, but it could not claim efficacy, causation or generalisability. The next legitimate step was clear: Recover and bind the ASS-2 multi-site protocol, recruitment records, site register, dataset, analysis plan, results and medication/cultural extensions.

A commercial pathway still emerged, but in the right order. If the research survives pre-registration, ethical review, comparative testing and replication, core curves (ass-1) assessment module could become a useful module for human performance research. Services could include assessment, implementation support, training, certification and assurance. Policy makers could use the resulting measures to ask for evidence of agency, equity, handback and retained skill rather than accepting output uplift alone.

Later, Dr Arun Bose returned to the original dashboard. It still showed green. Now the team understood that green was not a finding; it was an invitation to investigate. For ASS-2 — Extended/Multi-Site Validation, progress would mean building a traceable chain from question to protocol, participant experience, raw data, analysis, limitation and decision. The strongest closing lesson was simple: human capability must remain visible even when the machine makes performance look effortless.

Reflection

What did we learn?

Apparent improvement in ASS-2 — Extended/Multi-Site Validation must be separated from retained capability, agency, verification burden and recovery.

Why does this matter?

Without a first-class study or programme record, evidence, claims, datasets and outputs cannot be reliably reconciled, audited or regenerated.

What research does this connect to?

AI Sweet Spots → Multi-Site Validation; related register: AI Sweet Spots and Multi-Site Validation taxonomy objects; exact mappings require reconciliation.

What should happen next?

Recover and bind the ASS-2 multi-site protocol, recruitment records, site register, dataset, analysis plan, results and medication/cultural extensions.

Ground Zero scenario narrative — not an empirical finding.