This synthetic analytics exercise combines copying similarity, revision, verification, delayed recall, and confidence change into an inspectable offloading proxy. It exposes the chosen weights and tests alternative weighting scenarios. Because scores are normalized within each cohort and the bands are heuristic, the results support sensitivity analysis rather than diagnosing individual dependence on AI.
Review scope: The existing suite requires unavailable dependencies; no full-suite pass is claimed. The bundled demonstration executed successfully in this review.
Category: AI in Education A transparent benchmark for detecting possible cognitive offloading in AI-assisted learning.
Research prototype. All bundled data and results are synthetic demonstrations. Nothing in this repository should be interpreted as evidence about real learners, teachers, or institutions.
Generative AI can support learning, but it can also make it easy to outsource the thinking that should remain with the learner. This repo turns that concern into measurable, testable behavioral hypotheses without pretending that a single score can read a learner’s mind.
The scoring pipeline keeps each behavioral proxy visible, including copy similarity, revision, verification, recall, and confidence change. Researchers can therefore examine how each assumption affects the final offloading signal rather than treating the score as a diagnosis.
- Which observable behaviors are consistent with heavy answer substitution?
- Can verification and revision behaviors counterbalance superficial similarity signals?
- How stable are risk bands under different feature weightings and thresholds?
The reference pipeline follows five stages:
- Interaction traces
- Behavior features
- Transparent scoring
- Sensitivity analysis
- Risk-band reporting
The baseline is intentionally conservative and inspectable before any longitudinal learner data or richer behavioral models are introduced.
copy_similarityrevision_ratioverification_ratedelayed_recallconfidence_shiftoffloading_score
The dashboard above is generated from synthetic data and is included only to show what the analysis surface looks like. It is not a reported empirical result.
python -m venv .venv
source .venv/bin/activate # Windows: .venv\Scripts\activate
pip install -e .[dev]
python examples/demo.py
pytest -qYou can also use Docker:
docker build -t cognitive_offloading_analytics .
docker run --rm cognitive_offloading_analyticscognitive_offloading_analytics/
├── src/cognitive_offloading_analytics/ # core implementation and synthetic-data generator
├── examples/demo.py # end-to-end reproducible demo
├── tests/ # executable unit tests
├── docs/ # research design, data dictionary, references
│ └── images/ # original project diagrams and demo visualisations
├── results/ # synthetic demo outputs only
├── config/default.yaml
├── Dockerfile
├── Makefile
└── pyproject.toml
The fuller design rationale is in docs/research_design.md, including constructs, assumptions, validation steps, and a proposed empirical extension.
- Synthetic generation uses a fixed random seed.
- The core metrics are implemented as small, testable functions.
- The demo writes machine-readable results into
results/. - CI runs the tests on every push and pull request.
- No API keys, proprietary datasets, or external model calls are required for the baseline.
- Behavioral proxies cannot establish cognitive state on their own.
- Similarity is not plagiarism detection and should never be used as a disciplinary signal.
- Thresholds are illustrative and must be validated for each learning context.
- Estimate uncertainty for each learner-level score.
- Compare behavioral proxies with think-aloud or stimulated-recall data.
- Model longitudinal changes to distinguish temporary assistance from persistent answer substitution.
See docs/references.md. The references are there to locate the project in current AIED, learning-analytics, human-centered AI, and instructional-design research. They do not imply endorsement or affiliation.
If you build on this research prototype, use the metadata in CITATION.cff.
MIT for the code in this repository. Research data from future studies should use a separate data-governance and consent process.