The technical pathway concerns automation, information architecture, and formalisation. The focus is on connecting system inputs, the work performed, and evidence of the result.
01
Automation and data
Identifiable inputs, traceable transformations.
Read more+
Python and shell support repeatable imports, checks, and reports. Manifests and registers distinguish originals from normalised data and generated artifacts while retaining their source connection.
02
Documents and interfaces
LaTeX, web, and a readable result.
Read more+
LaTeX/PDF documents and TypeScript interfaces need different checks: compilation and rendered pages for the former, navigation, accessibility, and behaviour for the latter. Public data retains a distinct boundary from protected data.
03
Isabelle/HOL
A formalisation direction to verify.
Read more+
Syntax, free variables, and symbol transformations form part of the preparatory work. General translations, semantics, and proof obligations need specific verification: this page presents the method without attributing machine-verified mathematical results.
04
Verification and delivery
Making the result inspectable.
Read more+
Tests, dependency inventories, and artifact checks make the work traceable. Code presence, a passing test, and a service ready for use answer different questions and need separate documentation.
The four curriculum variants need updating and publication review. Downloads will be available after the content, documents, and destinations have been reviewed.
Diplomas, transcripts, correspondence, and personal materials remain in protected channels. Public examples will be selected separately.