The thinking behind the work.
Design notes, arguments and project records. These explain the method and its limits; they are not published outcome studies.
Local-first study systems for high-friction academic material
Why MnemoNexus is being shaped around local evidence, narrow workflows, and explicit document lineage instead of generic AI productivity claims.
Evidence before generation
A short argument for grounding study outputs in explicit source evidence before allowing the system to package those outputs as teaching material.
Why MnemoNexus should have both a website and an app surface
The site is for trust, explanation, and onboarding. The app is for doing the work. Mixing both into one ambiguous surface usually makes both worse.
Building a research software project in public
A short framing piece on using the public site as an archive of design decisions, experiments, and constraints instead of only a launch page.
The Master Document pipeline: a design record
The intended path from lecture evidence to readable teaching material, and the checks that make each step inspectable.