A dissertation becomes a living, interactive, AI-native web application.

three paths

Where are you starting from?

Every dissertation begins somewhere — a question you cannot shake, a folder of half-thought out ideas or chapters, an R package or collection of R scripts you have been refining for years. The framework adapts. Pick the entry point that matches where you are.

Idea-first

Start with a question; end with a platform.

New project? A short interview about your question, methods, and sources builds a scaffolded knowledge base, a Quarto writing environment, and an optional computational layer.

Begin

Content-first

Bring what you have; get the structure.

Have chapters, sources, or transcripts? Upload them; AI-assisted ingestion seeds your wiki and scaffolds Quarto chapters around your writing.

Begin

Package-first

An R package as the methodological core.

Writing around an existing R package? Paste a GitHub URL or CRAN name; introspection drafts your wiki, and the framework adds the interpretive layer that makes it legible.

Begin

past → future

What your dissertation becomes

The same scholarship, no longer sealed in a single static file — a living system, rendered wherever your readers, their tools, and future collaborators need it.

thesis.pdfwas / is
  • Humanreads it
  • Machinenot machine-readable
  • AIopaque to agents
static · a single reader
living appcan be
  • Humanread · search · cite
  • MachineAPI · queryable
  • AIsynthesizable corpus
living · serves everyone

AI-native creation

Many surfaces, one source
You and an AI collaborator shape one set of source files. From them, a typeset PDF thesis, a navigable web edition, and a searchable knowledge base are generated together — never out of sync.
Built to connect
That same co-creation keeps the work API-addressable — so people cite it, tools query it, and AI agents synthesize from it, joining the web of knowledge rather than sitting apart from it.