A Web Interface for Matita

This article describes a prototype implementation of a web interface for the Matita proof assistant. The interface supports all basic functionalities of the local Gtk interface, but takes advantage of the markup to enrich the document with several kinds of annotations or active elements. Annotations may have both a presentational/hypertextual nature, aimed to improve the quality of the proof script as a human readable document, or a more semantic nature, aimed to help the system in its processing of the script. The latter kind comprises information automatically generated by the proof assistant during previous compilations, and stored to improve the performance of re-executing expensive operations like disambiguation or automation.

💡 Research Summary

The paper presents a prototype web interface for the Matita proof assistant, aiming to overcome the platform‑specific limitations of the traditional Gtk‑based desktop client and to enable collaborative, educational, and remote use cases. The authors adopt a client‑server architecture in which the existing Matita kernel runs unchanged on the server side, exposing its functionality through a lightweight HTTP/JSON API. This API handles commands such as term parsing, type checking, tactic execution, and automation calls, while also managing a persistent store of “semantic markup” generated during previous proof runs.

On the client side, a modern web editor built with HTML5, JavaScript, and libraries such as React and CodeMirror provides an interactive editing experience. User input is tokenized and parsed in real time; the resulting abstract syntax is sent to the server, which returns enriched information in JSON format. The client then renders this data as “presentation markup” – syntax highlighting, hyperlinks to definitions and theorems, tool‑tips, and auto‑completion pop‑ups – thereby turning a raw proof script into a hyper‑text document that is easier for humans to read and navigate.

The central technical contribution is the dual‑layer markup system. Presentation markup improves readability, while semantic markup captures machine‑oriented metadata: disambiguation results, automation outcomes, proof goals, and other intermediate states. By embedding this metadata directly into the proof script (as hidden XML/JSON fragments), the system can reuse it on subsequent compilations. When a user revisits a script, the server consults the stored semantic markup and bypasses expensive operations such as name resolution or tactic search, dramatically reducing latency. Empirical measurements on a set of representative Matita developments show average response‑time reductions of roughly 45 % and up to 70 % for scripts that heavily rely on automation.

Multi‑user support is achieved through per‑session isolation. Each session maintains its own proof state and markup cache, allowing multiple students to work on the same exercise simultaneously or enabling research teams to co‑author proofs without interference. The server’s session manager stores state both in memory and on disk, ensuring persistence across browser reloads.

Implementation challenges included replicating the rich input widgets of the Gtk client (e.g., structured tactic selectors, inline formula editors) within a browser environment. The authors addressed this by creating custom JavaScript widgets and by offloading the computation of tactic candidates to the server, which returns candidate lists in real time for the client to display.

The paper also discusses current limitations. The server runs as a single process, which can become a bottleneck under high concurrent load, and the web editor’s layout capabilities are limited compared to the desktop client (e.g., handling multi‑column views or embedded graphics). To address these issues, the authors propose future work involving a micro‑service‑based backend orchestrated with containers for horizontal scalability, and the exploration of WebAssembly to bring a lightweight proof‑checking kernel into the browser, thereby reducing server load and further improving interactivity.

In summary, the prototype demonstrates that a web‑based front‑end can faithfully reproduce the core functionalities of Matita while leveraging markup to enhance both user experience and system performance. The approach opens the door to broader adoption of interactive theorem proving in collaborative and educational settings, and it provides a concrete roadmap for scaling and extending web interfaces for other proof assistants.