*[0_timeline]: The public-facing, static website and primary transparency layer for the Smartup Zero experiment. Shows latest progress, business plan, team structure, roles, and documentation.
*[1_general_forum]: The “General Forum”—the digital public square for all Smartup owners (workers and watchers). Center for governance, deliberation, voting, and oversight.
*[2_workplace]: The private hub for active workers. Where work happens, teams assemble, and objectives are executed. Requires a Work License.
*[3_teams]: Skill-based groups within the Workplace, like Development, Design, Media, Business, Operations, or Science. Each team has a Team Captain.
*[4_roles]: Function-specific assignments within a Team (e.g., UX Designer, Backend Developer). Define tasks, requirements, and compensation logic.
*[5_objectives]: Distinct missions or project deliverables that drive Smartup forward. Each has a Mission Leader and can contain multiple tasks.
*[6_tasks]: The atomic units of work in Smartup Zero. Each task has an Attacker (Worker), Defender (Assistant), and often a Midfielder (bot/automation).
*[ADM Triangle]: Attacker–Defender–Midfielder triad. Ensures initiation, review, and automation are always present in work processes.
*[Advisory Vote]: A non-binding team-level vote for ambiguous decisions.
*[Binding Vote]: A formal, binding vote for major milestones or conflicts. Requires a majority in the General Forum.
*[Book of Owners]: Transparent registry listing all official Smartup owners and their rights.
*[Book of Owners]: Transparent registry listing all official Smartup owners and their rights.
*[Buddy System]: A peer partnership model borrowed from military operations where each task or decision involves two people—an Attacker and a Defender—to guarantee accountability, quality, and on-the-job learning.
*[Book of Owners]: Transparent registry listing all official Smartup owners and their rights.
*[Dual-Currency Model]: The combined economic system using Smartup Credits (SC) for task-based value and Social Karma (SK) for reputation-based influence, ensuring both work output and community contributions are valued.
*[Engelbot]: The custom Smartup bot acting as the Midfielder in the ADM Triangle. Automates notifications, bridges Forgejo and Matrix, parses structured commands, and logs key events.
*[External Subsystem]: The framework that defines how Smartups operate beyond national boundaries—planetary governance, borderless participation, equal pay, and a path to global recognition.
*[Four License System]: The revenue model where community members purchase one of four license tiers (Campaign, Watch, Work, Organizational), each granting one equal vote but varying participation rights.
*[Forgejo]: The self-hosted Git forge (ethical fork of Gitea) used for code, project boards, issue tracking, Smartup Credits ledger, and CI/CD automation.
*[Isolated Human Doctrine]: Critique of current digital systems that reinforce individualism and undermine collective action.
*[Liquid Delegative Voting]: A planned governance feature allowing owners to delegate their voting power to trusted representatives, blending direct democracy with scalable representation.
*[Matrix/Element]: The decentralized, encrypted chat and collaboration platform (Matrix protocol with the Element client) used for governance, team coordination, and bot integration.
*[Mesh Network]: A peer-to-peer network topology where each device relays data for others, enabling communication even when central infrastructure is down.
*[Micro-Pilot]: Phase 0 of the Smartup lifecycle—a one-month, invite-only pilot that validates onboarding, role assignment, task execution, SC minting, and voting workflows on a small scale.
*[Objectives]: Defined missions or sprints within Teams, breaking vision into actionable deliverables.
*[Official Smartup Business Plan (OSBP)]: A living, version-controlled document recording strategy, team assessments, design blueprints, and validation metrics. It serves as the collective constitution of a Smartup.
*[ONLIFE]: First pilot project of the Smartup model (Smartup Zero) —an open-source emergency mesh network protocol for smartphones that functions when all other networks fail to help citizens during all kinds of disasters or cyberattacks.
*[Open Collective EU]: The transparent fiscal host for Smartup Zero, managing crowdfunding, budgets, and payouts. All transactions are publicly visible.
*[Smartup Administration Index]: A unified numbering convention (1_general_forum through 6_tasks) that labels every governance channel, team, role, objective, and task—enabling clarity, consistency, and automation across platforms.
*[Smartup Constitution]: Evolving documentation of rules, decisions, and learnings from the Smartup Zero experiment, intended for reuse by future Smartups.
*[Smartup Metabolism]: The set of processes—onboarding, task execution, payouts, voting—that sustain and grow a Smartup as a living system.
*[Smartup Organism]: Metaphor for the Smartup as a multi-layered, living system where roles and processes interlock to produce collective intelligence.
*[Task]: Atomic unit of productive work. Defined in Forgejo, claimed by a Worker (Attacker), reviewed by a Defender, and logged for SC minting.
*[Team Captain]: Elected leader of a Team. Manages roles, approves tasks, allocates budget, and represents the Team in the Leadership Team.
*[Validation (Phase One)]: Phase that proves demand through funding, community growth, and initial prototype validation.
*[Watch License]: Grants governance participation (vote, forum access) but not access to paid tasks.
*[Work License]: Grants the right to claim tasks, earn Smartup Credits, and full workplace access.
*[Workplace]: The office of the smartup. Here we are collegues and we work in teams on our common mission: building tech for sdg progress.
*[4 Phases of Creation]: The five lifecycle stages for a Smartup (Phase 0 Micro-Pilot → Phase 1 Validation → Phase 2 Design → Phase 3 Production → Phase 4 Organization), each gated by funding, deliverables, review, and a binding community vote.
*[Phase 0: Micro-Pilot]: A one-month, invite-only trial with 15–20 contributors to test onboarding, role assignment, task execution, SC minting, and voting workflows.
*[Phase 1: Validation]: Community proves demand through crowdfunding, forms teams, drafts the OSBP v1.0, and holds a binding vote to proceed.
*[Phase 2: Design]: Contributors deliver blueprints, complete scientific peer review, and vote to advance, ensuring technical and social soundness.
*[Phase 3: Production]: The community builds and beta-tests the MVP, conducts market assessment, and votes to move toward formal organization.
*[Phase 4: Organization]: Final phase where executive roles are elected, legal and governance structures are solidified, and the Smartup readies for market launch.
*[6 Groups of Productivity]: The nested Smartup anatomy—General Forum, Workplace, Teams, Roles, Objectives, Tasks—each layer overseeing the next.
*[Technical Subsystem]: The suite of technological tools, processes, and economic models that enable collaborative production in a Smartup. Includes the dual-currency economy (Smartup Credits and Smartup Karma), the Four License System, the EU-sovereign open-source stack (Matrix/Element, Forgejo, Open Collective), the Smartup Administration Index for semantic numbering, and automation via Engelbot and CI/CD workflows.
*[External Subsystem]: The framework that defines how Smartups operate as planetary organizations beyond national boundaries and political cycles. Emphasizes borderless digital participation, equal pay regardless of location, defocusing from partisan politics, resilience to regulatory volatility, and a roadmap to formal recognition as new organizational entities under global jurisdiction.
*[Ack message]: A message that is used in order to acknowledge something.
*[AP or Access point]: A device that is used to connect clients to a network.
*[AP interface]: The network interface responsible for providing access point capabilities.
*[Child node]: The node that is directly connected to the parent node. A child node and parent node are always relative to each other.
*[Client network]: The network that is set up by each distribution node to serve data to clients.
*[Data Manifest]: The data manifest is a table used to store UUIDs and IP addresses of network accessible content.
*[Distribution network]: The network that links the distribution nodes together and provides connectivity to the entire mesh network.
*[Local data Manifest]: The local data manifest is a table used to provide NAT capabilities to the distribution node by coupling UUIDs to the NAT identifiers.
*[NAT]: Network address translation, a method used to serve multiple network devices using a single publicly facing IP address.
*[Network plane]: A single layer within the topology model.
*[Nodes]: Network capable devices that are part of the network.
*[Parent node]: A node that is acting as the connection point for the node directly connected to it below it, called the child node.
*[Root plane]: The topmost layer of the topology model.
*[RSSI]: A metric to describe the connection strength of a Wi--Fi network.
*[STA/AP concurrency]: AP/STA is a mode where a Wi-Fi capable device can simultaneously connect to an access point and be an access point at the same time.
*[STA interface]: The station interface is the network interface responsible for connecting to a Wi-Fi network.
*[SSID]: The broadcasted network name with which it can be identified.
*[Throughput]: The amount of data a network can handle over a given time.
*[TTL]: Time to live, a predefined amount of time in which a message or node is deemed valid or active.
*[UDP]: User Datagram Protocol.
*[UUID]: Universally unique identifier an identifier used to create a unique name for identification.
*[OSBP]: A living, version-controlled document recording strategy, team assessments, design blueprints, and validation metrics. It serves as the collective constitution of a Smartup.
