#terminlogy being used:
---

**0_timeline**  
The public-facing, static website and primary transparency layer for the Smartup Zero experiment. Automatically updates from the project’s code and content repository to show the latest progress, business plan, team structure, open roles, and project documentation.

---

**1_general_forum**  
The “General Forum”—the digital public square for all Smartup owners (workers and watchers). This is where deliberation, voting, oversight, and key discussions occur. It’s the central arena for governance, transparency, and measuring the organization’s overall health.

---

**2_workplace**  
The central, private hub for all active “workers” within the Smartup. This is where work happens, teams assemble, and objectives are executed. Only those with a Work License may participate; the Workplace is the engine room of creation and productivity.

---

**3_teams**  
Skill-based groups within the Workplace, such as Development, Design, Media, Business, Operations, or Science. Teams focus on implementing specific aspects of the project. Each team is led by a Team Captain and organizes its own Roles and Objectives.

---

**4_roles**  
Function-specific assignments within a Team (e.g., UX Designer, Backend Developer, Copywriter). Each Role has requirements, compensation logic, and defines what kind of tasks the member can claim or be assigned.

---

**5_objectives**  
Distinct missions, project deliverables, or “sprints” that drive the Smartup forward. Each Objective is attached to a Team, can contain multiple Tasks, and is led by a Mission Leader responsible for coordination and quality.

---

**6_tasks**  
The atomic units of work in Smartup Zero. Tasks are clearly defined, trackable, and billable work items that contribute directly to achieving Objectives. Each Task has an assigned Worker (attacker), an Assistant (defender), and is supported by bots or automation (midfielder).

---

*(The rest below is alphabetical, for completeness and consistency in all documentation):*

---

**ADM Triangle**  
Attacker–Defender–Midfielder: The operational triad present in every group within the Smartup. The attacker initiates work or proposals, the defender reviews and provides oversight, and the midfielder (often a bot or automation) facilitates transparency and communication between roles.

---

**Advisory Vote / Binding Vote**  
Advisory votes are used for team-level or ambiguous decisions; binding votes are required for major milestones, phase transitions, or conflict resolution. Binding votes require a majority in the General Forum.

---

**Book of Owners**  
The transparent registry listing all official Smartup owners and their rights and privileges.

---

**Business Team**  
The group responsible for developing a solid business proposition, marketing strategies, financial planning, and ensuring the product or service is ready for market. In charge of the business and financial side of the Smartup, and of updating the Official Smartup Business Plan (OSBP).

---

**Collective Craftsmanship**  
A core Smartup value. Emphasizes that meaningful work and reward are distributed among all members based on contribution and merit, not hierarchy or tenure.

---

**Collective Governance**  
Democratic and transparent oversight of all Smartup operations, with formal processes for deliberation, voting, dispute resolution, and adaptation.

---

**Collective IQ**  
The enhanced problem-solving capability created when a group collaborates with transparency and shared purpose.

---

**Collective Ownership**  
Equal and inclusive ownership of the Smartup organization. Ownership is based on participation and willingness to contribute, not financial investment or seniority.

---

**Crowdfunding Phases**  
Funding rounds aligned with each major phase of Smartup creation. Each phase cannot progress to the next without meeting its designated funding target.

---

**Design Team**  
The group handling all design-related activities such as user experience (UX), interface, branding, wireframing, and prototyping. Responsible for the Design Blueprint and close cooperation with the Development Team and Science Team.

---

**Development Team**  
The technical heart of the Smartup. Builds and tests the core product or service, covering frontend, backend, security, architecture, and QA. Coordinates with Design, Science, and Operational Teams, and manages code versioning and repositories.

---

**Isolated Human Doctrine**  
A term describing the prevailing system in which technology platforms reinforce individualism and passive consumption, undermining collective action and responsibility.

---

**Karma Points / Smartup Credits (SC)**  
Karma Points are awarded for positive and constructive participation, teamwork, or peer review; these may be convertible to payouts. Smartup Credits (SC) are a tokenized internal currency (1 SC = 1 EUR claim on treasury funds), earned through completing tasks.

---

**Leadership Team**  
The decision-making and strategic core of a Smartup during creation phases, composed of all team captains and the initiating entrepreneur. This team orchestrates budgets, objectives, and major decisions while being accountable to the full community.

---

**Media Team**  
Ensures communication flows both inside the Smartup (internal reporting, progress updates) and outside (public relations, social media, storytelling). Produces engaging content to keep the community and backers informed.

---

**Mission Leader**  
A senior member appointed to maintain progress and oversight within a specific objective, assign tasks, and ensure quality of work.

---

**Objectives**  
Defined missions, focus areas, or sprints within the Teams structure; objectives break the organizational vision into actionable missions.

---

**Observation**  
The analytical foundation for Smartup Zero: the world is off track for the SDGs because collective action and problem-solving are obstructed by broken digital and organizational systems.

---

**Official Smartup Business Plan (OSBP)**  
A “living document” that records strategy, key decisions, research, assessments, and design throughout all phases; accessible to all owners.

---

**ONLIFE**  
The first pilot project of Smartup Zero: a decentralized, emergency citizen mesh network prototype.

---

**Operational Team**  
Focuses on monitoring and improving processes between teams. Handles incident management, compliance, documentation, learning, and overall coordination, especially crucial for the first Smartup where learning is key.

---

**Organization (Phase Four)**  
The final phase of Smartup creation, in which the executive/operational structure is finalized, the business proposition is solidified, and the product or service is prepared for market launch.

---

**Phases of Creation**  
The four required stages for building a Smartup and its product or service:  
1. **Validation** – Organize support, prove viability, reach the first funding target, and form coherent teams.  
2. **Design** – Co-create blueprints and user experiences with scientific peer review and collective input.  
3. **Production** – Build MVP/product, run beta tests, and refine based on review and feedback.  
4. **Organization** – Establish operational structure, complete the final business plan, and prepare for launch.

---

**Production (Phase Three)**  
The phase in which the product or service is built, tested, and improved based on feedback and scientific review.

---

**Roles**  
Specific functional positions (e.g., Frontend Developer, UX Designer, Copywriter) within Teams; define both skill requirements and compensation rates.

---

**Science Team**  
Group responsible for independent scientific oversight and review, ensuring that all processes and outcomes align with sustainability best practices, evidence, and scalability. Holds power to request additional research or halt advancement if standards are not met.

---

**Sociotechnical System (STS)**  
An integrated approach to organizational design that balances social (human) and technical (infrastructural) factors for optimal collective performance and quality of life.

---

**Smartup**  
A new organizational model (the subject of Smartup Zero) designed to maximize democratic, scientific, and community-driven collaboration in creating technology for social and planetary benefit.

---

**Smartup Constitution**  
A codified document of learnings, rules, and governance logic, iteratively developed from the Smartup Zero experiment, designed to be adapted by future Smartups.

---

**Smartup Credits (SC)**  
Internal, auditable digital tokens or ledger entries, representing claimable value for contributors (1 SC = 1 EUR when funds are available in the treasury).

---

**Smartup Metabolism**  
Metaphor for the system of processes—decision-making, feedback, payout, onboarding, and documentation—that enable the Smartup to adapt, sustain itself, and grow.

---

**Smartup Organism**  
Metaphorical framing for the entire Smartup structure as a multi-layer, living system whose “organs” work together toward collective vitality and resilience.

---

**Task**  
The atomic unit of productive work. Clearly defined, assigned, and logged; completion triggers SC payouts and structured peer/advisor review.

---

**Team**  
A focused group of workers with a shared skillset, responsible for a domain such as Development, Design, Media, Business, Operations, or Science. Each team is led by a Team Captain and contains multiple Roles and Objectives.

---

**Team Captain**  
Elected leader within a given Team; manages roles, budgets, tasks, performance, and represents the team in the Leadership Team.

---

**Validation (Phase One)**  
The initial phase of building a Smartup: validating the concept, building community, securing funding, and operationalizing the vision.

---

**Watch License / Work License**  
A Watch License grants governance and observation rights within the Smartup, but not paid assignments. A Work License grants the full right to work, vote, and earn Smartup Credits.

---

**Workplace**  
The centralized collaborative production environment for all workers, where concurrent teamwork and objectives are managed.

---

