System register
Not every experiment should be presented as a product. This register states what is operational, what is an artwork, what is being tested and what remains research.
Maintained
Software that has moved beyond a one-off exhibition or study and is maintained as infrastructure.
Open-source maritime awareness and search-and-rescue research platform. It normalizes reports into canonical incidents, keeps source and coordinate provenance, runs drift trajectories, separates operational and public data, and publishes a privacy-filtered Live surface.
The current codebase includes an authenticated console, API and workers, a Cloudflare Public Live edge, AIS and environmental integrations, source monitoring, case workflows and regression-tested publication rules.
A long-running cartographic and institutional research environment. Republic is used to test how borders, routes, legal fictions and infrastructure become visible through maps, interfaces and public encounters.
Works / prototypes
These projects are judged as artworks first. Their technical systems are documented because the engineering is part of the work, not because every prototype is meant to become a service.
A drifting environmental node and simulation study around position, movement and partial observation at sea. Hardware, transmission and modelling remain part of the artistic proposition.
Project →A conversational work about initiative, responsibility and the authority granted to a machine that speaks first. The web prototype exposes session boundaries and is being tested as a governed, temporary agent rather than a persistent assistant.
Project →A mobile embassy built as both sculpture and field device. Locomotion, camera, radio, power and institutional fiction are intentionally visible in the same object.
Project →A work built around automated market observation and rule-based decision states. Its interest lies in how a computational treasury declares, records and revises its own actions.
Project →Reading
The public documentation records architecture, data flow, tests and limits. Historical audits and future plans remain in their source repositories instead of being mixed with current system claims.