5_1_1 - Reproducible Laboratory Apparatus: SmartupOS on NixOS #25

New issue

Open

opened 2026-07-15 10:30:48 +00:00 by Engelbot · 0 comments

Engelbot commented

2026-07-15 10:30:48 +00:00

Owner

Team Objective

Eliminate the single largest barrier to independent replication of the Smartup Zero experiment: the complex, manual deployment of the SmartupOS laboratory apparatus. This objective funds the creation of production‑ready NixOS modules and comprehensive documentation so that any mission‑driven community—or external research team—can deploy the full SmartupOS stack (Forgejo, Matrix/Synapse, Element, Engelbot, MkDocs) on EU‑sovereign infrastructure with minimal technical expertise.

Why: The Timeline0 research programme makes a core scientific commitment: the Smartup Hypothesis must be independently replicable. Other communities must be able to run the same experiment with the same apparatus and generate comparable telemetry. Today, that commitment is unmet. Deploying SmartupOS requires a skilled operator who understands reverse proxies, PostgreSQL, systemd, and the integration points between four distinct services. This is a barrier to replication that undermines the scientific validity of the entire programme.

If the experiment cannot be independently replicated, the evidence it generates remains anecdotal—a single observation by the team that built the tools. Making the apparatus trivially deployable is not a convenience. It is methodological infrastructure, as essential as the pre‑registered metrics or the public ledger.

This objective also serves the broader mission of the research programme. By making SmartupOS accessible to non‑specialist communities, we lower the barrier for future Smartups to join the research programme, increasing the number of experiments and the statistical power of the evidence we can generate.

How: We will fund two dedicated Science Team contributors—a NixOS Engineer and a Technical Writer—through the NGI Fediversity grant, with oversight from the Leadership Team.

NixOS Engineer:

Develop declarative NixOS modules for each SmartupOS component: Forgejo (with append‑only ledger configuration and SHA‑based locking), Matrix/Synapse (defederated, with token‑gated registration and auto‑joined spaces), Element (web client, pre‑configured for the homeserver), Engelbot (Node.js service with Matrix authentication), and MkDocs (static site generation with auto‑rebuild on ledger changes).
Write integration tests that validate the full stack behaves correctly, including the constitutional write order (Markdown → CSV → audit trail) and the 409 conflict retry mechanism.
Upstream all modules to the NixOS community under an open‑source licence (EUPL or AGPL‑3.0).

Technical Writer:

Produce a complete deployment guide aimed at non‑specialist community organisers, covering: VPS provisioning, DNS configuration, NixOS installation, running the SmartupOS configuration, and post‑deployment verification.
Write tutorial‑style documentation with worked examples, troubleshooting sections, and a clear upgrade path.
Ensure all documentation is versioned alongside the NixOS modules in the Forgejo repository.

Leadership Team oversight (Robbert Schep):

Define technical requirements based on the existing production deployment.
Review module design, documentation drafts, and integration test results.
Ensure alignment with the research programme's methodology and reproducibility commitments.

The modules will be tested against the live SmartupOS production environment on Hetzner and Clever Cloud, ensuring they reflect real‑world operational constraints, not assumptions.

What: - Production‑ready NixOS modules for Forgejo, Matrix/Synapse, Element, Engelbot, and MkDocs, publicly available in a Forgejo repository and upstreamed to the NixOS community.

A single declarative configuration file that defines the entire SmartupOS stack, enabling a one‑command deployment on any NixOS‑compatible VPS.
A comprehensive deployment guide, written for a non‑specialist audience, covering provisioning, configuration, verification, and maintenance.
Integration tests that validate the full stack, including the constitutional write order and the defederated Matrix workspace.
A public reference implementation listed in the Smartup Registry on timeline0.org.
All outputs published under an open‑source licence.

📊 Details

Phase: validation
Parent Objective: 5_1

🎯 ADM Structure

⚔️ Attacker: 3_6 (responsible for execution)
🛡️ Defender: 3_1 (responsible for quality/oversight)
🤖 Midfielder: Engelbot (coordination)

Created via Engelbot by @robbert

## Team Objective Eliminate the single largest barrier to independent replication of the Smartup Zero experiment: the complex, manual deployment of the SmartupOS laboratory apparatus. This objective funds the creation of production‑ready NixOS modules and comprehensive documentation so that any mission‑driven community—or external research team—can deploy the full SmartupOS stack (Forgejo, Matrix/Synapse, Element, Engelbot, MkDocs) on EU‑sovereign infrastructure with minimal technical expertise. **Why:** The Timeline0 research programme makes a core scientific commitment: the Smartup Hypothesis must be independently replicable. Other communities must be able to run the same experiment with the same apparatus and generate comparable telemetry. Today, that commitment is unmet. Deploying SmartupOS requires a skilled operator who understands reverse proxies, PostgreSQL, systemd, and the integration points between four distinct services. This is a barrier to replication that undermines the scientific validity of the entire programme. If the experiment cannot be independently replicated, the evidence it generates remains anecdotal—a single observation by the team that built the tools. Making the apparatus trivially deployable is not a convenience. It is methodological infrastructure, as essential as the pre‑registered metrics or the public ledger. This objective also serves the broader mission of the research programme. By making SmartupOS accessible to non‑specialist communities, we lower the barrier for future Smartups to join the research programme, increasing the number of experiments and the statistical power of the evidence we can generate. **How:** We will fund two dedicated Science Team contributors—a NixOS Engineer and a Technical Writer—through the NGI Fediversity grant, with oversight from the Leadership Team. **NixOS Engineer:** - Develop declarative NixOS modules for each SmartupOS component: Forgejo (with append‑only ledger configuration and SHA‑based locking), Matrix/Synapse (defederated, with token‑gated registration and auto‑joined spaces), Element (web client, pre‑configured for the homeserver), Engelbot (Node.js service with Matrix authentication), and MkDocs (static site generation with auto‑rebuild on ledger changes). - Write integration tests that validate the full stack behaves correctly, including the constitutional write order (Markdown → CSV → audit trail) and the 409 conflict retry mechanism. - Upstream all modules to the NixOS community under an open‑source licence (EUPL or AGPL‑3.0). **Technical Writer:** - Produce a complete deployment guide aimed at non‑specialist community organisers, covering: VPS provisioning, DNS configuration, NixOS installation, running the SmartupOS configuration, and post‑deployment verification. - Write tutorial‑style documentation with worked examples, troubleshooting sections, and a clear upgrade path. - Ensure all documentation is versioned alongside the NixOS modules in the Forgejo repository. **Leadership Team oversight (Robbert Schep):** - Define technical requirements based on the existing production deployment. - Review module design, documentation drafts, and integration test results. - Ensure alignment with the research programme's methodology and reproducibility commitments. The modules will be tested against the live SmartupOS production environment on Hetzner and Clever Cloud, ensuring they reflect real‑world operational constraints, not assumptions. **What:** - Production‑ready NixOS modules for Forgejo, Matrix/Synapse, Element, Engelbot, and MkDocs, publicly available in a Forgejo repository and upstreamed to the NixOS community. - A single declarative configuration file that defines the entire SmartupOS stack, enabling a one‑command deployment on any NixOS‑compatible VPS. - A comprehensive deployment guide, written for a non‑specialist audience, covering provisioning, configuration, verification, and maintenance. - Integration tests that validate the full stack, including the constitutional write order and the defederated Matrix workspace. - A public reference implementation listed in the Smartup Registry on timeline0.org. - All outputs published under an open‑source licence. --- ## 📊 Details - **Phase:** validation - **Parent Objective:** 5_1 --- ## 🎯 ADM Structure - **⚔️ Attacker:** 3_6 (responsible for execution) - **🛡️ Defender:** 3_1 (responsible for quality/oversight) - **🤖 Midfielder:** Engelbot (coordination) --- *Created via Engelbot by @robbert*