The Autonomous Master Archive: A Low-Dependency Ecosystem
Concept, intuitive prompt engineering, and testing: Ana Maria Micu
Code: Gemini 3, under a Google AI Pro subscription
License: GNU GPL v3
Date: April 2026
Click to download Autonomous_Archive_v1.0.0_2026-04.zip 15.2 MB
This package is designed for the long-term administration of extensive artwork databases, such as a catalogue raisonné comprising hundreds of records. It is highly applicable if you are solely responsible for managing diverse communication formats regarding these works, including editable text-and-image documents, static web deployments, and automatically generated PDFs.
Conceived as an autonomous architectural framework, the kit is distributed independently of its software dependencies, requiring active integration by the user. Optimized for a Windows environment, the system relies on a precise constellation of free, open-source, and proprietary freeware tools: Chromium (or Google Chrome) to execute the local JavaScript compiler, LibreOffice to manage the data matrices and render native OpenDocument formats, and the Java Runtime Environment to process the underlying XML architecture. To achieve the artwork’s conceptual goal of absolute portability and hardware resilience, the entire ecosystem is designed to be housed on an external drive alongside localized, portable iterations of these applications, ensuring the archive remains permanently self-contained and ready for execution across distinct machines.
Distributed as an explanatory scaffold, the architecture requires deliberate reconfiguration to become operational. The user must manually redefine the absolute file paths, marked in red, within the primary .ods matrix to map onto their specific local hardware. The initial directory setup and placeholder assets serve strictly as a structural blueprint, designed to be entirely overwritten and populated by the user’s personal archival records and localized media.
Functioning simultaneously as a digital artwork and a survival protocol, this framework is an autonomous, zero-dependency ecosystem built for archival longevity. By operating entirely offline and rejecting cloud servers, relational databases, and subscription models, the system achieves permanent immunity to software obsolescence. The underlying architecture relies exclusively on raw web standards (HTML, CSS, JavaScript) and native OpenDocument XML (.fodt), structurally separating public web deployment from private studio management through mathematically strict CSV data matrices. The distribution contains two primary processing modules: a local, serverless Web Deployment Compiler that reads authorized data tags to generate a fully linked, static HTML website while automating local media extraction, and a Private Editor utility that bypasses privacy locks to facilitate studio management, visual verification, and the generation of unredacted physical printouts or LibreOffice documents.
Because the system operates mathematically on flat files, it demands absolute structural discipline. Execution requires Chromium or Google Chrome, strict UTF-8 .csv formatting, and precise nomenclature using absolute file paths to properly map visual assets; any deviation in syntax will result in system failure. Integrating failsafes such as a localized Python execution protocol against future operating system restrictions, the architecture is distributed as-is. It serves as an open-source foundation for other artists and researchers to study, dismantle, modify, and rebuild for their own long-term data retention needs.
Concept, intuitive prompt engineering, and testing: Ana Maria Micu
Code: Gemini 3, under a Google AI Pro subscription
License: GNU GPL v3
Date: April 2026
Click to download Autonomous_Archive_v1.0.0_2026-04.zip 15.2 MB
This package is designed for the long-term administration of extensive artwork databases, such as a catalogue raisonné comprising hundreds of records. It is highly applicable if you are solely responsible for managing diverse communication formats regarding these works, including editable text-and-image documents, static web deployments, and automatically generated PDFs.
Conceived as an autonomous architectural framework, the kit is distributed independently of its software dependencies, requiring active integration by the user. Optimized for a Windows environment, the system relies on a precise constellation of free, open-source, and proprietary freeware tools: Chromium (or Google Chrome) to execute the local JavaScript compiler, LibreOffice to manage the data matrices and render native OpenDocument formats, and the Java Runtime Environment to process the underlying XML architecture. To achieve the artwork’s conceptual goal of absolute portability and hardware resilience, the entire ecosystem is designed to be housed on an external drive alongside localized, portable iterations of these applications, ensuring the archive remains permanently self-contained and ready for execution across distinct machines.
Distributed as an explanatory scaffold, the architecture requires deliberate reconfiguration to become operational. The user must manually redefine the absolute file paths, marked in red, within the primary .ods matrix to map onto their specific local hardware. The initial directory setup and placeholder assets serve strictly as a structural blueprint, designed to be entirely overwritten and populated by the user’s personal archival records and localized media.
Functioning simultaneously as a digital artwork and a survival protocol, this framework is an autonomous, zero-dependency ecosystem built for archival longevity. By operating entirely offline and rejecting cloud servers, relational databases, and subscription models, the system achieves permanent immunity to software obsolescence. The underlying architecture relies exclusively on raw web standards (HTML, CSS, JavaScript) and native OpenDocument XML (.fodt), structurally separating public web deployment from private studio management through mathematically strict CSV data matrices. The distribution contains two primary processing modules: a local, serverless Web Deployment Compiler that reads authorized data tags to generate a fully linked, static HTML website while automating local media extraction, and a Private Editor utility that bypasses privacy locks to facilitate studio management, visual verification, and the generation of unredacted physical printouts or LibreOffice documents.
Because the system operates mathematically on flat files, it demands absolute structural discipline. Execution requires Chromium or Google Chrome, strict UTF-8 .csv formatting, and precise nomenclature using absolute file paths to properly map visual assets; any deviation in syntax will result in system failure. Integrating failsafes such as a localized Python execution protocol against future operating system restrictions, the architecture is distributed as-is. It serves as an open-source foundation for other artists and researchers to study, dismantle, modify, and rebuild for their own long-term data retention needs.
