Skip to content

Smartup OS — Architecture Overview

What is this?

A shared architectural map of Smartup OS for co-founders: how the pieces connect, why they matter, and how we bootstrap trust organically.


Vision

Smartup OS is our institutional operating system—a transparent, forensic, and scalable framework for collective creation and systemic trust.
We start with the essentials: identity, governance, and execution—and layer in automation as the system matures and proves itself.


System Architecture (Top-Level)

flowchart TB
  subgraph Front["🌐 Front-Office"]
    M[Matrix / Element<br>Governance & Chat]
    T[timeline0.org<br>Public Transparency]
  end

  subgraph Back["🏗 Back-Office"]
    F[Forgejo<br>Repos & Wikis]
    L[Ledger<br>Ownership · Roles · Tasks · SC/SK]
  end

  subgraph Middleware["🤖 Middleware"]
    E[Engelbot<br>Orchestration & Sync]
  end

  subgraph External["💶 External Systems"]
    OC[Open Collective EU<br>Licenses & Funding]
  end

  OC -->|License → Identity| E
  E -->|Onboarding & Sync| L
  E -->|Orchestration| F
  E -->|Commands| M

  M -->|Chat, Governance, Roles| L
  F -->|Documents & Logbooks| L

  L -->|Public Export| T

Six Groups of Productivity

mindmap
  root((Smartup OS))
    Founders & Owners
      Matrix / Element
    Workplace
      Ledger / SC Tools
    Teams
      Forgejo Repos
    Roles
      Team Captains
    Objectives
      Mission Blueprints
    Tasks
      Issue-level Execution

Each “group” is both a social unit and a technical node, mirrored perfectly in Matrix rooms, Forgejo repos, and ledger hierarchy.


Component Breakdown

Layer Components / Tools
Front-Office Matrix/Element (chat, voting), timeline0.org (public mirror)
Back-Office Forgejo (repos, wikis) & Ledger (0_timeline → 6_tasks: ownership, SC/SK, roles)
Middleware Engelbot (script & AI automation, future license-onboarding)
External Open Collective (licenses = entry point → identity & ledger sync)

📒 the ledger & toolbox: the operational backbone

flowchart TD
    subgraph Public[1_general_forum]
        Timeline0[🌍 0Timeline - Public Site & Matrix Room]
    end

    subgraph Workplace[2_workplace]
        Ledger[(📒 Ledger)]
    end

    subgraph LeadershipTeam[3_1_leadership_team]
        Toolbox[[🧰 Toolbox Scripts]]
    end

    subgraph OperationalTeam[3_7_operational_team]
        Engelbot[[🤖 Engelbot]]
    end

    %% Flows
    Toolbox -->|reads/writes| Ledger
    Engelbot -->|executes| Toolbox
    Engelbot -->|queries & enforces| Ledger
    Engelbot -->|publishes updates| Timeline0
    Ledger -->|truth visible to| Timeline0

The ledger in detail:

flowchart TD

%% === DATA LAYER ===
subgraph D[📂 Data Layer]
    L[ledger.csv<br/>Transactions]
    O[owners.csv<br/>Owners & Roles]
    P[policies.csv<br/>Rules & Policies]
    Y[links.yml<br/>Org Structure Links]
end

%% === PROCESSING LAYER ===
subgraph P1[🐍 Processing Layer - Scripts]
    V[Validation Scripts<br/> - consistency, balances]
    G[generate-public-pages.py<br/> Book of Owners, Transparency]
    U[Update Scripts<br/> - add task, grant SK, log entries]
    R[Reporting Scripts]
end

%% === PUBLISHING LAYER ===
subgraph PUB[🌍 Publishing Layer]
    M[docs/ → MkDocs Site]
    T[timeline0.org<br/>Public Book of Owners & Transparency]
end

%% === ORCHESTRATION ===
subgraph BOT[🤖 Future Engelbot Integration]
    C[Commands<br/>- log task, grant SK]
    TR[Trigger Scripts<br/>via CLI / API]
    FEED[Post Outputs<br/>to Matrix / Forgejo / Timeline0]
end

%% === CONNECTIONS ===
L --> V
O --> V
P --> V
Y --> V

L --> U
O --> U
P --> U
Y --> U

U --> L
U --> O

D --> G
G --> M --> T

%% Engelbot links
C --> TR --> U
TR --> G
TR --> R
FEED --> BOT

%% Feedback loop
BOT --> D

Scripts up and running

  • Bootstrap tools

  • create_forgejo_repo.sh

  • deploy_forgejo_wiki_install.sh
  • logbook_template.md

  • Operational toolbox

  • add_logbook_entry.py

  • Ledger tools (generate-public-pages.py, generate-reports.py)
  • Task/process automation tools

  • Engelbot roadmap

  • v0.2: broad repo → room event orchestration

  • v0.3: ledger links.yml integration (trust spine)
  • v0.4+: license onboarding + AI command layer (RASA + Mistral)

Trust & Governance Protocols

Trust First, Automation Later

- Onboarding starts manual, but every action is logged in the ledger.
- Team Captains assign roles in Matrix rooms—all recorded.
- Votes, tasks, SC minting—all flows are transparent, traceable in ≤ 2 clicks.

  • SC = Smartup Credits;
  • SK = Smartup Karma;
  • ADM model (Attacker–Defender–Midfielder) underscores peer-learning and quality control.

Roadmap Towards Launch

Phase Milestone
Ledger Shell (v0.9 → v1.0) Build links.yml, integrate scripts, generate ledger structure
Public Integration Auto-publish OSBP, Book of Owners, Financial Health to timeline0.org
Middleware Sync Engelbot understands links.yml, orchestrates smoothly
Trust Launch First pilot (invite-only): manual onboarding, fully logged system

Why This Matters

Smartup OS is more than infrastructure—it’s a provable institutional experiment. It delivers:

  • Trust in creation
  • Scalable autonomy
  • Scientific auditability

We're not just designing a tool—we're designing the next generation of institutions.


Next Steps

  • Finalize the high-level diagram with new co-founders.
  • Run through a dry demo: onboarding, SC assignment, public mirror update.
  • Schedule the Ledger Shell scripting sprint next.