Core Curves (ASS-1)

The dashboard was green, but Mara Chen did not trust it. The team had finished faster with AI, yet nobody could say whether they had learned more, understood less, or simply moved the verification work somewhere the dashboard could not see.

Mara Chen, a operations director in Sydney, had been asked to decide whether Core Curves (ASS-1) belonged in a real programme or in another folder of attractive ideas. The immediate problem was practical: Current approaches to core curves (ass-1) are fragmented, poorly calibrated or insufficiently measured, making it difficult to distinguish real benefit from substitution, novelty or surveillance effects. 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, Mara Chen put the research question on the wall: “Which regions of the assistance intensity curve maximise combined performance, learning and autonomy?” 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: Performance will follow an inverted-U curve with the optimum varying by expertise and task novelty. 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 Demand–Capacity–Assistance–Performance–Recovery model applied to Core Curves. 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. Mara Chen 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: Statistically and practically meaningful improvement; preserved or improved human skill and agency; acceptable burden; no disproportionate subgroup harm; reproducible performance; effective handback, correction and recovery. The failure gate was explicit too: No meaningful benefit; gains mask reduced understanding or skill; dependency, fatigue, stress or exclusion exceeds benefit; effects fail to transfer or persist; user control is ineffective; correction or handback fails.

By the end of the workshop, Mara Chen had no miracle result to announce. That was the point. The evidence state was recorded as “PARTIAL — named empirical backbone recovered; source dataset, protocol and analysis 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: Bind the canonical ASS-1 protocol, dataset, participant records, analysis code, results and claim IDs; reconcile the Core Curves seed to the recovered study without duplicating the object.

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 enterprise operations. 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, Mara Chen 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 Core Curves (ASS-1), 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.