Tag: information-management
19 items with this tag.
AI infrastructure for academics: how earlier work makes later requests simple
I gave an AI agent two YouTube links and one sentence, and it returned two catalogued conference talks with slides, transcripts, and appraisal notes attached in Zotero. The request was short because months of earlier work sat behind it, including a fix from March and a tool from September. This post describes that session and an earlier one, and what they show about the difference between using AI to finish a task and using it in a way that leaves your system more capable than before.
Obsidian
Obsidian is a note-taking application that keeps every note as a plain markdown file in an ordinary folder on your own computer, and lets you link notes to one another. Because the notes are just files, they outlast the application, and any AI agent that can read files can read them without an export or a special connection.
Zotero
Zotero is a free, open source reference manager that stores the sources you collect with their citation details, PDFs, and notes. It also offers programming interfaces that let an AI agent search the library, read from it, and add to it, which turns a reference library into something an agent can check a draft against.
YAML
YAML is a human-readable format for storing structured data as plain text. In knowledge management and publishing workflows, it appears most commonly as the frontmatter block at the top of markdown files, where it holds metadata — title, author, date, tags — that tools can read without parsing the document itself.
Distributed version control
Distributed version control tracks changes to files so that every contributor holds a complete copy of the project and its full history, with no central server to depend on. It allows offline work, parallel development, and recovery from any copy, and it lets partners who share a document, such as a practice assessment document, each keep the whole record of how it changed.
Git
Git is a distributed version control system that tracks changes to files over time. It records who changed what and when, allows you to move between earlier and later states of a project, and lets multiple people work on the same files without overwriting each other's contributions.
How I review a week of reading notes with AI
Every week I annotate articles in Zotero, highlights in Reader, and podcasts in Snipd, all of which is synced to Obsidian. By Friday I have a week's worth of material, tagged and structured, but unreviewed. This post describes the weekly review command I built to surface what matters and create a reason to engage with it.
Harness engineering
Harness engineering is the practice of building the full architectural scaffolding within which AI agents operate — structured documentation they can reason with, constraints that enforce invariants, and feedback loops that let them know when they've succeeded. It is distinct from prompt engineering, which shapes individual tasks, and from oversight, which monitors outputs after the fact. The harness is the infrastructure that makes delegation coherent at scale.
AI agent governance in higher education: Building the institutional harness
The previous posts described what makes agentic workflows coherent at the individual level: a plan, documentation as infrastructure, and domain expertise that can evaluate outputs. Together, these form an informal harness; the conditions within which delegation stays accountable. At institutional scale, a personal harness is not enough: multiple people directing agents without shared constraints produce compounding drift that no amount of human oversight can track. This post examines what AI agent governance in higher education actually requires, and why a harness, not better oversight, may be the right frame.
Seven principle for collaborating with AI
Seven principles for extended AI collaboration, distilled from a week-long project to restructure a large note collection using Claude Code. The principles cover goal-setting, understanding what AI can and cannot contribute, investing in planning conversations, adaptive planning, safety infrastructure, treating AI output as drafts, and expecting to learn something about your own thinking. Offered not as rules to follow but as patterns to recognise.
Building an AI-ready knowledge base
A detailed account of a week-long project to restructure 5,819 Obsidian notes using AI as a working partner. The project involved building a 23-category taxonomy, migrating thousands of legacy notes to a consistent metadata structure, and generating AI-written descriptions for every note in the collection. The piece describes not just what was done, but how extended planning conversations, external project documentation, and careful human review at each phase made the work tractable. The most unexpected outcome was that building infrastructure for a note collection required articulating, for the first time, precisely how I think about my academic field.
How can we develop transformative tools for thought?
Source details Matuschak, A., & Nielsen, M. (2019). How can we develop transformative tools for thought? numinous.productions/ttft .
Querying the Zotero database with AI
What happens when you query Zotero with AI and treat your whole reference library as context, instead of searching it one document at a time? This field note describes a proof of concept in which Claude Code reads the Zotero database file directly. The approach works, and what breaks shows how much your metadata practices matter. It also sets out the privacy trade-off of sending query results to a cloud-based model.
Documentation debt
The accumulated cost of outdated, ambiguous, or poorly structured institutional knowledge — long paid invisibly by readers who work around the gaps, and exposed when AI agents read the same documents literally.
Plain text
Files made only of readable characters, with no formatting locked inside them. The format every tool can open, and the one that will still open in thirty years.
Organising your notes for AI: why retrieval isn't enough
Most advice on organising notes for AI treats it as a retrieval problem, as if the AI only needs to find the right documents. The harder problem is translation, making the relationships in your thinking machine-readable without losing what makes them yours. This post explains why search and retrieval fall short, shows what a typed link between two notes looks like, and suggests one small way to start.
Building an AI workflow for academics with structured documentation
Most advice on building an AI workflow for academics concentrates on writing better prompts. After several weeks of restructuring years of scholarly output with Claude Code, I've found the leverage lies in the structured context around the model — documentation that works as external memory, a cycle of testing rules and locking in the ones that hold, and the discipline of making implicit connections explicit. The same applies to institutions, where AI tools are only as reliable as the information architecture they're given.
Contextual interoperability
Contextual interoperability is what lets you use your own notes, frameworks, and commitments with any AI model, local or hosted. It has two halves: the context has to be legible, with relationships a model can follow, and portable, held by you instead of inside one provider's system. With a curriculum mapping example from a pharmacy programme.
Context sovereignty
What is context sovereignty? The idea that people should own and author the context they bring to AI (their values, commitments, and ways of making sense of things) so that AI adapts to their thinking. How it differs from data sovereignty and model memory, its three principles, and what it means for students and educators.