add operational blueprint, updated social-subsystem, exerpiment overview with transparancy design chapter
Robbert Schep
parent
07361672c4
commit
d4690d48e6
|
|
@ -802,3 +802,202 @@ The OSBP naturally identifies leaders through work:
|
|||
|
||||
!!! quote "The Document That Binds Us"
|
||||
"The OSBP isn't what we pitch to investors—we don't have any. It's what we promise each other and the world. It's our collective memory, our shared vision, and our operational reality all in one living document."
|
||||
|
||||
|
||||
## Progressive Transparency Architecture
|
||||
|
||||
!!! info "The Information Democracy"
|
||||
This section defines how Smartup Zero balances radical transparency with strategic protection through a three-tier access system. Unlike traditional organizations that operate on extremes (total secrecy vs. naive openness), Smartups pioneer **Progressive Transparency**—where access to information is earned through demonstrated commitment, while governance remains democratically open to all.
|
||||
|
||||
#### The Transparency Paradox Solution
|
||||
|
||||
<div class="grid cards" markdown>
|
||||
|
||||
- :material-eye-outline: **Traditional Binary Problem**
|
||||
|
||||
---
|
||||
|
||||
Either everything is secret (corporate model) or everything is public (naive open source)
|
||||
|
||||
- :material-lightbulb-on: **Smartup Innovation**
|
||||
|
||||
---
|
||||
|
||||
**Process transparency + Strategic discretion**: *How* we work is visible, *what* we build is revealed progressively
|
||||
|
||||
</div>
|
||||
|
||||
---
|
||||
|
||||
### The Three-Tier Information System
|
||||
|
||||
#### :material-earth: Tier 1: Universal Access (`1_general_forum`)
|
||||
|
||||
**Repository**: `1_general_forum` → **timeline0.org**
|
||||
**Access**: Open to the entire world
|
||||
**Purpose**: Democratic accountability and community building
|
||||
|
||||
!!! success "Public Contents"
|
||||
- Complete OSBP (external blueprints from all teams)
|
||||
- Book of Owners and governance records
|
||||
- All voting processes and outcomes
|
||||
- Weekly progress updates and challenge reports
|
||||
- Currency ledger (complete SC/Karma transaction history)
|
||||
- Community discussions and decision rationales
|
||||
|
||||
!!! quote "Philosophy"
|
||||
*"Democracy requires transparency. Every citizen should see how decisions are made, how money flows, and how the collective progresses."*
|
||||
|
||||
#### :material-account-group: Tier 2: Licensed Contributor Access (`2_workplace` and below)
|
||||
|
||||
**Repositories**: `2_workplace`, `3_X_teams`, `4_X_roles`
|
||||
**Access**: Work License holders and above
|
||||
**Purpose**: Protecting collective investment while enabling meaningful collaboration
|
||||
|
||||
!!! warning "Protected Contents"
|
||||
- ONLIFE implementation code and technical specifications
|
||||
- Internal blueprint versions with full implementation details
|
||||
- Active development workflows and team coordination
|
||||
- Work-in-progress features and experimental approaches
|
||||
- Strategic planning documents and competitive analysis
|
||||
|
||||
!!! quote "Philosophy"
|
||||
*"Our collective work deserves protection from free-riders. Those who contribute to building should have access to the tools and knowledge needed to build well."*
|
||||
|
||||
#### :material-shield-account: Tier 3: Organizational Governance
|
||||
|
||||
**Access**: Team Captains and Organizational License holders
|
||||
**Purpose**: Strategic coordination without compromising democratic principles
|
||||
|
||||
!!! danger "Sensitive Contents"
|
||||
- Cross-team coordination and resource allocation
|
||||
- Sensitive partnership negotiations
|
||||
- Legal and compliance documentation
|
||||
- Crisis management and conflict resolution processes
|
||||
|
||||
---
|
||||
|
||||
### The License Progression: Earning Trust Through Demonstration
|
||||
|
||||
| License Level | Access Tier | Purpose | How to Obtain | Key Rights |
|
||||
|---------------|-------------|---------|---------------|------------|
|
||||
| **Campaign** | Tier 1 only | Enable evaluation | Declare interest via Open Collective | Observe, discuss publicly |
|
||||
| **Watch** | Tier 1 + limited Tier 2 | Serious evaluation | Demonstrate sustained interest | Read-only internal docs, community calls |
|
||||
| **Work** | Full Tier 2 | Enable contribution | Complete onboarding, prove competence | Claim tasks, earn SC, access dev resources |
|
||||
| **Organizational** | All tiers | Enable leadership | Community election after sustained contribution | Team Captain roles, strategic access |
|
||||
|
||||
!!! tip "The Trust-Building Mechanism"
|
||||
**Progressive Transparency** creates a virtuous cycle:
|
||||
|
||||
1. **Curiosity** → Public docs attract interested people
|
||||
2. **Evaluation** → Campaign/Watch licenses allow assessment
|
||||
3. **Commitment** → Work License requires real investment
|
||||
4. **Contribution** → Meaningful work builds capability
|
||||
5. **Leadership** → Organizational License recognizes excellence
|
||||
6. **Innovation** → Experienced members improve systems
|
||||
|
||||
---
|
||||
|
||||
### The Weekly Sync: Internal Innovation, External Accountability
|
||||
|
||||
Every team operates a **dual blueprint system** with democratic oversight:
|
||||
|
||||
#### :material-file-document-edit: Internal Blueprints (Tier 2)
|
||||
<div class="grid cards" markdown>
|
||||
|
||||
- :material-code-tags: **Technical Details**
|
||||
|
||||
---
|
||||
|
||||
Complete specifications and implementation details
|
||||
|
||||
- :material-chart-line: **Live Progress**
|
||||
|
||||
---
|
||||
|
||||
Real-time tracking and issue identification
|
||||
|
||||
- :material-strategy: **Strategic Planning**
|
||||
|
||||
---
|
||||
|
||||
Competitive analysis and resource allocation
|
||||
|
||||
- :material-school: **Learning Documentation**
|
||||
|
||||
---
|
||||
|
||||
Experimental approaches and failed attempts
|
||||
|
||||
</div>
|
||||
|
||||
#### :material-web: External Blueprints (Tier 1 → timeline0.org)
|
||||
|
||||
!!! note "Updated every Friday through democratic review"
|
||||
- Progress summaries with measurable achievements
|
||||
- Challenge identification and resource needs
|
||||
- Community recruitment and skill requirements
|
||||
- Strategic direction without implementation details
|
||||
- Success metrics and phase advancement status
|
||||
|
||||
#### The Friday-Sunday Sync Process
|
||||
|
||||
```mermaid
|
||||
graph LR
|
||||
A[Friday: Team Captains Submit] --> B[48h Community Review]
|
||||
B --> C{Sunday 10pm Decision}
|
||||
C -->|≤3 Issues| D[Auto-merge & Publish]
|
||||
C -->|>3 Issues or Veto| E[Postpone Publication]
|
||||
D --> F[timeline0.org Updates]
|
||||
```
|
||||
|
||||
!!! warning "Democratic Safeguards"
|
||||
- **Lazy Consensus**: All owners can participate in review
|
||||
- **Issue Threshold**: >3 unresolved issues postpones publication
|
||||
- **Leadership Veto**: 2+ Leadership Team members can block publication
|
||||
- **Template Compliance**: Operational Team standards enforced
|
||||
|
||||
---
|
||||
|
||||
### Why This Architecture Serves Collective Ownership
|
||||
|
||||
<div class="grid cards" markdown>
|
||||
|
||||
- :material-shield-check: **Protects Collective Investment**
|
||||
|
||||
---
|
||||
|
||||
Prevents extractive actors from taking collective work without contributing. Traditional "open source" often means "free labor for corporate profit"—we invert this.
|
||||
|
||||
- :material-medal: **Makes Licenses Meaningful**
|
||||
|
||||
---
|
||||
|
||||
Each license level provides genuine value and responsibility. Progression reflects demonstrated commitment and proven collaboration competence.
|
||||
|
||||
- :material-vote: **Maintains Democratic Legitimacy**
|
||||
|
||||
---
|
||||
|
||||
All governance remains public. License holders get access to tools, never special voting rights. Every decision is visible to the world.
|
||||
|
||||
- :material-clock-outline: **Enables Strategic Timing**
|
||||
|
||||
---
|
||||
|
||||
Develop innovations collectively while choosing optimal release timing for maximum impact and partner protection.
|
||||
|
||||
</div>
|
||||
|
||||
!!! success "The Resolution"
|
||||
**Smartup Innovation**: **Process transparency + Strategic discretion**
|
||||
|
||||
- *How* we work is always visible (governance, decision-making, progress)
|
||||
- *What* we're building is revealed progressively as people demonstrate commitment
|
||||
- *Who* makes decisions is always public and democratic
|
||||
- *When* we release innovations is chosen collectively for maximum impact
|
||||
|
||||
This architecture embodies the core Smartup principle: **Technology should serve collective human needs, built by and for the communities that use it, with full democratic accountability but protection from extraction.**
|
||||
|
||||
The result is an organization that is both **radically transparent** in its governance and **strategically intelligent** in its operations—capable of competing with traditional startups while remaining true to collective ownership principles.
|
||||
|
||||
|
|
|
|||
|
|
@ -10,20 +10,20 @@
|
|||
|
||||
Building on our core hypothesis, Smartup Zero tests three system tweaks:
|
||||
|
||||
- :material-account-group: Social Subsystem
|
||||
From fragmented “users” to democratic citizens—transparent governance, peer workflows, and collective ownership.
|
||||
- :material-account-group: **Social Subsystem**
|
||||
From fragmented "users" to democratic citizens—transparent governance, peer workflows, collective ownership, and progressive transparency architecture.
|
||||
|
||||
- :material-server: Technical Subsystem
|
||||
From isolated tools to group-first design—dual-currency economy, license model, sovereign open-source stack, and automated administration.
|
||||
- :material-server: **Technical Subsystem**
|
||||
From isolated tools to group-first design—dual-currency economy, sovereign open-source stack, and automated administration.
|
||||
|
||||
- :material-earth: External Subsystem
|
||||
- :material-earth: **External Subsystem**
|
||||
From national silos to planetary organizations—borderless operations, equal pay, and a roadmap to global recognition.
|
||||
|
||||
---
|
||||
|
||||
!!! warning "Don't Be Overwhelmed"
|
||||
A Smartup is a new species of organization with many novel tools, processes, and workflows.
|
||||
You won’t master it all at once—learn by doing in the live experiment!
|
||||
You won't master it all at once—learn by doing in the live experiment!
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -33,32 +33,44 @@ We frame each subsystem by its defining elements. Click through to explore detai
|
|||
|
||||
=== ":material-account-group: Social Subsystem"
|
||||
|
||||
**Architecture**
|
||||
- Rocket model: foundation (Science, Democracy, Collective IQ) + 3 pillars + military execution.
|
||||
- :material-cube-outline: Four Phases (0→Validation→Design→Production→Organization).
|
||||
- :material-layers-triple: Six Groups of Productivity (Forum, Workplace, Teams, Roles, Objectives, Tasks).
|
||||
- :material-triangle: ADM Triangle + Buddy System for quality, learning, and accountability.
|
||||
- :material-book-open: Official Smartup Business Plan (OSBP) as living constitution.
|
||||
- :material-coin: Smartup Credits (SC) for transparent contribution tracking.
|
||||
**Organizational Architecture**
|
||||
- :material-rocket-launch: Rocket model: foundation (Science, Democracy, Collective IQ) + 3 pillars + military execution
|
||||
- :material-cube-outline: Four Phases (0→Validation→Design→Production→Organization)
|
||||
- :material-layers-triple: Six Groups of Productivity (Forum, Workplace, Teams, Roles, Objectives, Tasks)
|
||||
|
||||
**Democratic Governance**
|
||||
- :material-triangle: ADM Triangle + Buddy System for quality, learning, and accountability
|
||||
- :material-book-open: Official Smartup Business Plan (OSBP) as living constitution
|
||||
- :material-vote: Binding vs. Advisory voting for different decision types
|
||||
|
||||
**Progressive Transparency Architecture** :material-new-box:
|
||||
- :material-earth: Tier 1: Universal access (governance, progress, currency ledger)
|
||||
- :material-account-group: Tier 2: Licensed contributor access (implementation, development)
|
||||
- :material-shield-account: Tier 3: Organizational governance (strategic coordination)
|
||||
- :material-license: Four License System (Campaign → Watch → Work → Organizational)
|
||||
- :material-calendar-sync: Weekly blueprint sync (internal → external transparency)
|
||||
|
||||
=== ":material-server: Technical Subsystem"
|
||||
|
||||
**Economy & Access**
|
||||
- :material-currency-eur: Dual-Currency Model (SC + Social Karma).
|
||||
- :material-license: Four License System (Campaign → Watch → Work → Organizational).
|
||||
**Dual-Currency Economy**
|
||||
- :material-coin: Smartup Credits (SC): 1 SC = €1 treasury claim for completed work
|
||||
- :material-heart: Social Karma: Non-transferable reputation for community contribution
|
||||
- :material-git: Git-native ledger system with immutable transaction history
|
||||
|
||||
**Infrastructure & Automation**
|
||||
- :material-server: EU-sovereign, open-source stack (Matrix/Element, Forgejo, Open Collective).
|
||||
- :material-layers-triple: Smartup Administration Index (semantic numbering & workflows).
|
||||
- :material-robot: Engelbot & CI for automated task routing, voting, and SC minting.
|
||||
- :material-server: EU-sovereign, open-source stack (Matrix/Element, Forgejo, Open Collective)
|
||||
- :material-layers-triple: Smartup Administration Index (semantic numbering & workflows)
|
||||
- :material-robot: Engelbot & CI for automated task routing, voting, and SC minting
|
||||
- :material-group: Group-centric design (ONLIFE mesh protocol for collective action)
|
||||
|
||||
=== ":material-earth: External Subsystem"
|
||||
|
||||
**Planetary Scope**
|
||||
- :material-earth-box: Digital-first, no HQ, operates under Internet jurisdiction.
|
||||
- :material-account-heart: Borderless participation & equal pay worldwide.
|
||||
- :material-scale-balance: Defocused from politics; focused on SDGs & scientific reality.
|
||||
- :material-numeric-3-circle: Roadmap to UN/global recognition as a new org “species.”
|
||||
- :material-earth-box: Digital-first, no HQ, operates under Internet jurisdiction
|
||||
- :material-account-heart: Borderless participation & equal pay worldwide
|
||||
- :material-scale-balance: Defocused from politics; focused on SDGs & scientific reality
|
||||
- :material-numeric-3-circle: Roadmap to UN/global recognition as a new org "species"
|
||||
- :material-shield-lock: Immunity from political volatility through decentralized structure
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -80,79 +92,110 @@ We frame each subsystem by its defining elements. Click through to explore detai
|
|||
|
||||
</div>
|
||||
|
||||
|
||||
---
|
||||
|
||||
A high end overview of the lifecylce of a Smartup:
|
||||
## The Democratic Phase Transition Process
|
||||
|
||||
```mermaid
|
||||
flowchart TD
|
||||
%% Start
|
||||
Start(["START HERE | Entrepreneur/Organization with an Idea"])
|
||||
subgraph Validation["🔬 Validation Phase"]
|
||||
V1["Financial Target Reached?"]
|
||||
V2["Teams Organized & Staffed?"]
|
||||
V3["OSBP v0.1 → v1.0 Ready?"]
|
||||
V4{"Majority Vote Ready?"}
|
||||
V5{"Science Team Veto?"}
|
||||
V6["✅ Advance to Design"]
|
||||
end
|
||||
subgraph Design["🎨 Design Phase"]
|
||||
D1["Financial Target Reached?"]
|
||||
D2["Teams Organized & Staffed?"]
|
||||
D3["OSBP v1.0 → v2.0 Ready?"]
|
||||
D4{"Majority Vote Ready?"}
|
||||
D5{"Science Team Veto?"}
|
||||
D6["✅ Advance to Production"]
|
||||
end
|
||||
subgraph Production["⚙️ Production Phase"]
|
||||
P1["Financial Target Reached?"]
|
||||
P2["Teams Organized & Staffed?"]
|
||||
P3["OSBP v2.0 → v3.0 Ready?"]
|
||||
P4{"Majority Vote Ready?"}
|
||||
P5{"Science Team Veto?"}
|
||||
P6["✅ Advance to Organization"]
|
||||
end
|
||||
subgraph Organization["🌍 Organization Phase"]
|
||||
O1["Financial Target Reached?"]
|
||||
O2["Teams Organized & Staffed?"]
|
||||
O3["OSBP v3.0 → v4.0 Ready?"]
|
||||
O4{"Majority Vote Ready?"}
|
||||
O5{"Science Team Veto?"}
|
||||
O6["🚀 Launch to Market"]
|
||||
end
|
||||
V1 --> V2
|
||||
V2 --> V3
|
||||
V3 --> V4
|
||||
V4 -- Pass --> V5
|
||||
V4 -- Fail --> V1
|
||||
V5 -- Approved --> V6
|
||||
V5 -- Veto --> V1
|
||||
V6 --> D1
|
||||
D1 --> D2
|
||||
D2 --> D3
|
||||
D3 --> D4
|
||||
D4 -- Pass --> D5
|
||||
D4 -- Fail --> D1
|
||||
D5 -- Approved --> D6
|
||||
D5 -- Veto --> D1
|
||||
D6 --> P1
|
||||
P1 --> P2
|
||||
P2 --> P3
|
||||
P3 --> P4
|
||||
P4 -- Pass --> P5
|
||||
P4 -- Fail --> P1
|
||||
P5 -- Approved --> P6
|
||||
P5 -- Veto --> P1
|
||||
P6 --> O1
|
||||
O1 --> O2
|
||||
O2 --> O3
|
||||
O3 --> O4
|
||||
O4 -- Pass --> O5
|
||||
O4 -- Fail --> O1
|
||||
O5 -- Approved --> O6
|
||||
O5 -- Veto --> O1
|
||||
Start(["Entrepreneur with Idea"]) --> Validation
|
||||
|
||||
%% Validation Phase
|
||||
subgraph Validation["Validation Phase"]
|
||||
OSBP["the official smartup business plan"]
|
||||
DevTeam1["Development Team"]
|
||||
DesignTeam1["Design Team"]
|
||||
ScienceTeam1["Science Team"]
|
||||
ProjectLeaders["Project Leaders Team"]
|
||||
Crowdfunding["Crowdfunding"]
|
||||
|
||||
OSBP --> Crowdfunding
|
||||
Crowdfunding -->
|
||||
DevTeam1 --> ProjectLeaders
|
||||
DesignTeam1 --> ProjectLeaders
|
||||
ScienceTeam1 --> ProjectLeaders
|
||||
|
||||
ProjectLeaders --> ForumValidation["General Forum"]
|
||||
ForumValidation --> VoteValidation["VOTE"]
|
||||
VoteValidation --> StratPlanValidation["Official Strategic Plan | Prototyping Ready"]
|
||||
end
|
||||
|
||||
%% Design Phase
|
||||
subgraph Design["Design Phase"]
|
||||
DesignTeam2["Design Team | Design Blueprint"]
|
||||
ScienceTeam2["Science Team | Scientific Review"]
|
||||
|
||||
StratPlanValidation --> DesignTeam2
|
||||
DesignTeam2 --> ScienceTeam2
|
||||
ScienceTeam2 --> ForumDesign["General Forum"]
|
||||
ForumDesign --> VoteDesign["VOTE"]
|
||||
VoteDesign --> StratPlanDesign["Approved Design Blueprint"]
|
||||
end
|
||||
|
||||
%% Production Phase
|
||||
subgraph Production["Production Phase"]
|
||||
DevTeam2["Development Team | Beta Testing"]
|
||||
ScienceTeam3["Science Team | Scientific Review"]
|
||||
|
||||
StratPlanDesign --> DevTeam2
|
||||
DevTeam2 --> ScienceTeam3
|
||||
ScienceTeam3 --> ForumProd["General Forum"]
|
||||
ForumProd --> VoteProd["VOTE"]
|
||||
VoteProd --> StratPlanProd["Official Strategic Plan | Production Ready"]
|
||||
end
|
||||
|
||||
%% Organization Phase
|
||||
subgraph Organization["Organization Phase"]
|
||||
ExecTeam["Elected Executive Team"]
|
||||
BusinessTeam["Business Team | Final Market Assessment"]
|
||||
|
||||
StratPlanProd --> ExecTeam
|
||||
ExecTeam --> ForumOrg["General Forum"]
|
||||
ForumOrg --> VoteOrg["VOTE"]
|
||||
VoteOrg --> BusinessTeam
|
||||
BusinessTeam --> MarketReady["Official Strategic Plan | Market Ready"]
|
||||
end
|
||||
|
||||
%% End
|
||||
MarketReady --> End(["TO MARKET! | END HERE!"])
|
||||
|
||||
%% Connections
|
||||
Start --> OSBP
|
||||
|
||||
%% Styling (optional but valid syntax)
|
||||
classDef startEnd fill:#FFD600,stroke:#FFD600,color:#000,font-weight:bold
|
||||
class Start,End startEnd
|
||||
V4:::majorityVote
|
||||
V5:::scienceVeto
|
||||
V6:::success
|
||||
D4:::majorityVote
|
||||
D5:::scienceVeto
|
||||
D6:::success
|
||||
P4:::majorityVote
|
||||
P5:::scienceVeto
|
||||
P6:::success
|
||||
O4:::majorityVote
|
||||
O5:::scienceVeto
|
||||
O6:::success
|
||||
classDef majorityVote fill:#f9d,stroke:#333,stroke-width:2px
|
||||
classDef scienceVeto fill:#e74c3c,stroke:#333,stroke-width:2px
|
||||
classDef success fill:#27ae60,stroke:#333,stroke-width:2px
|
||||
style V4 color:#2962FF
|
||||
style D4 color:#2962FF
|
||||
style P4 color:#2962FF
|
||||
style O4 color:#2962FF
|
||||
```
|
||||
|
||||
!!! warning "Science Team: The Final Gatekeepers"
|
||||
Special Veto Power: Even if the majority votes "ready," the Science Team can halt progression if the solution:
|
||||
- Doesn't meet SDG compliance standards
|
||||
- Lacks sustainability (e.g., server emissions too high)
|
||||
- Isn't peer-reviewable or scientifically sound
|
||||
- Could solve one problem but create others
|
||||
*Think of them as auditors ensuring we don't release tools that cause unintended harm.*
|
||||
|
||||
!!! tip "Consistent 4-Threshold Structure"
|
||||
Every phase follows the same validation pattern:
|
||||
1. **Financial**: Crowdfunding/revenue targets met
|
||||
2. **Organizational**: Teams properly staffed and functioning
|
||||
3. **Documentation**: OSBP evolved to next version standard
|
||||
4. **Democratic**: Community majority approval + Science Team sign-off
|
||||
|
||||
|
|
|
|||
|
|
@ -1,32 +1,48 @@
|
|||
<form class="contact-form" action="https://api.staticforms.xyz/submit" method="post">
|
||||
<!-- REQUIRED: Replace this with your StaticForms access key -->
|
||||
<input type="hidden" name="accessKey" value=sf_ha7960c038fb88i3hbgf0d81>
|
||||
<!-- Complete form with reCAPTCHA and custom fields -->
|
||||
<form action="https://api.staticforms.xyz/submit" method="POST">
|
||||
<!-- Required: Your Static Forms API key -->
|
||||
<input type="hidden" name="apiKey" value=sf_ha7960c038fb88i3hbgf0d81>
|
||||
|
||||
<!-- Makes the "Reply-To" email address the one the user submitted -->
|
||||
<input type="hidden" name="replyTo" value="@">
|
||||
<!-- Enable reply-to functionality -->
|
||||
<input type="hidden" name="replyTo" value="@">
|
||||
|
||||
<!-- Sets the subject of the email you will receive -->
|
||||
<input type="hidden" name="subject" value="Contact Form Submission - Smartup Zero">
|
||||
<!-- Anti-spam honeypot field -->
|
||||
<input
|
||||
type="text"
|
||||
name="honeypot"
|
||||
style="display: none"
|
||||
tabindex="-1"
|
||||
autocomplete="off"
|
||||
>
|
||||
|
||||
<!-- Redirects user to a thank you page after submission -->
|
||||
<input type="hidden" name="redirectTo" value="https://timeline0.org/0_timeline/thank-you/">
|
||||
|
||||
<!-- Anti-spam honeypot field. Do not change. -->
|
||||
<input type="text" name="honeypot" style="display: none" tabindex="-1" autocomplete="off">
|
||||
|
||||
<!-- Form Fields -->
|
||||
<!-- Form fields -->
|
||||
<div class="form-group">
|
||||
<label for="name">Name:</label>
|
||||
<input type="text" id="name" name="name" required>
|
||||
</div>
|
||||
|
||||
<div class="form-group">
|
||||
<label for="email">Email:</label>
|
||||
<input type="email" id="email" name="email" required>
|
||||
</div>
|
||||
|
||||
<!-- Custom field with $ prefix -->
|
||||
<div class="form-group">
|
||||
<label for="company">Company:</label>
|
||||
<input type="text" id="company" name="$company">
|
||||
</div>
|
||||
|
||||
<div class="form-group">
|
||||
<label for="message">Message:</label>
|
||||
<textarea id="message" name="message" rows="8" required></textarea>
|
||||
<textarea id="message" name="message" required></textarea>
|
||||
</div>
|
||||
|
||||
<div class="g-recaptcha" data-sitekey=6LcXVZcrAAAAAErKk03ysIccvSose25YnkeiBP-b></div>
|
||||
<script src="https://www.google.com/recaptcha/api.js" async defer></script>
|
||||
<!-- reCAPTCHA integration -->
|
||||
<div class="g-recaptcha" data-sitekey=6LcXVZcrAAAAAErKk03ysIccvSose25YnkeiBP-b></div>
|
||||
<script src="https://www.google.com/recaptcha/api.js" async defer></script>
|
||||
|
||||
<button type="submit">Send Message</button>
|
||||
<!-- Optional redirect URLs -->
|
||||
<input type="hidden" name="redirectTo" value="https://example.com/success">
|
||||
|
||||
<button type="submit">Send Message</button>
|
||||
</form>
|
||||
|
||||
|
|
|
|||
|
|
@ -0,0 +1,170 @@
|
|||
# :material-cog-outline: 7. Operational Blueprint
|
||||
|
||||
!!! info "What is this section?"
|
||||
This document is the official **Operational Blueprint** for Smartup Zero. It defines the internal workflows, processes, and operational systems that enable all teams to function effectively within the Smartup model. Think of this team as the "office managers" and process architects of the organization. It is the primary responsibility of the **`3_7_operational_team`**.
|
||||
|
||||
- **Attacker (A):** The members of the `3_7_operational_team` are the "attackers" who design, test, and refine our internal operational systems.
|
||||
- **Defender (D):** The `4_1_7_tc_operational_team` (the Team Captain) is the "defender," responsible for ensuring process quality and cross-team coordination.
|
||||
- **Midfielder (M):** The `Engelbot` automates process enforcement, deadline tracking, and workflow integration across all teams.
|
||||
|
||||
## 1. Mission Summary
|
||||
|
||||
Our mission is to design, implement, and continuously optimize the operational infrastructure that makes collective ownership and democratic governance actually work at scale. We are the architects of Smartup Zero's internal operating system—ensuring that radical transparency, peer accountability, and efficient execution can coexist harmoniously.
|
||||
|
||||
---
|
||||
|
||||
## **Part 1: The Weekly Blueprint Sync System**
|
||||
|
||||
This section defines our signature process: how teams maintain radical transparency while protecting strategic development.
|
||||
|
||||
### 2.1. The Two-Layer Information Architecture
|
||||
Every team maintains dual blueprints to balance openness with operational security:
|
||||
|
||||
**Internal Blueprints** (Team Repositories - Licensed Access):<br>
|
||||
- Full implementation details and sensitive technical specifications<br>
|
||||
- Work-in-progress sections and internal coordination<br>
|
||||
- Budget breakdowns and strategic planning details<br>
|
||||
- Team-specific workflows and quality standards<br>
|
||||
|
||||
**External Blueprints** (1_general_forum → timeline0.org):<br>
|
||||
- Public progress updates and milestone status<br>
|
||||
- Challenge identification and community recruitment needs
|
||||
- High-level strategic direction and methodology insights<br>
|
||||
- Democratic accountability through measurable outcomes<br>
|
||||
|
||||
### 2.2. The Friday-Sunday Governance Cycle
|
||||
Our weekly sync process embodies democratic oversight with operational efficiency:
|
||||
|
||||
#### **Friday: Submission & Review Kickoff**
|
||||
- **Team Captains** submit external blueprint updates using our standardized templates<br>
|
||||
- **Lazy Consensus** review period begins (all owners participate)<br>
|
||||
- **Template compliance** automatically verified against operational standards<br>
|
||||
|
||||
#### **Friday-Sunday: Democratic Review Period**
|
||||
- **48-hour window** for community discussion and issue identification<br>
|
||||
- **Leadership Team** monitors for strategic alignment and quality concerns<br>
|
||||
- **Unresolved issues** tracked through structured GitHub issue workflow<br>
|
||||
|
||||
#### **Sunday 10pm: Decision Point**
|
||||
- **Auto-merge** if ≤3 unresolved issues (initial threshold, subject to optimization)<br>
|
||||
- **Publication postponed** if >3 unresolved issues or 2+ Leadership Team objections<br>
|
||||
- **timeline0.org** automatically updates from merged external blueprints<br>
|
||||
|
||||
### 2.3. External Blueprint Templates
|
||||
We maintain standardized templates ensuring consistency across all team communications:
|
||||
|
||||
**Required Sections:**<br>
|
||||
- Progress Summary (measurable achievements since last update)<br>
|
||||
- Current Challenges (obstacles and resource needs)<br>
|
||||
- Next Week Goals (specific, verifiable commitments)<br>
|
||||
- Community Recruitment (open roles and skill needs)<br>
|
||||
- Phase Advancement Status (metrics toward next phase criteria)<br>
|
||||
|
||||
---
|
||||
|
||||
## **Part 2: The ADM Triangle Implementation**
|
||||
|
||||
This section defines how we embed peer accountability into every aspect of Smartup operations.
|
||||
|
||||
### 3.1. Universal ADM Architecture
|
||||
Every operational unit in Smartup Zero implements the Attacker-Defender-Midfielder structure:
|
||||
|
||||
**Attacker (A):** The initiator who proposes, creates, or executes<br>
|
||||
**Defender (D):** The reviewer who validates, challenges, and ensures quality
|
||||
**Midfielder (M):** The facilitator (often Engelbot) who ensures transparency and communication<br>
|
||||
|
||||
### 3.2. ADM Implementation Across the 6 Groups of Productivity
|
||||
|
||||
#### **1_general_forum (Governance Level)**
|
||||
- **A:** Community members proposing votes/discussions<br>
|
||||
- **D:** Leadership Team ensuring process compliance<br>
|
||||
- **M:** Engelbot managing voting mechanics and record-keeping<br>
|
||||
|
||||
#### **2_workplace (Coordination Level)**
|
||||
- **A:** Team Captains coordinating objectives<br>
|
||||
- **D:** Operational Team ensuring cross-team alignment<br>
|
||||
- **M:** Engelbot tracking deliverables and dependencies<br>
|
||||
|
||||
#### **3_teams (Execution Level)**
|
||||
- **A:** Team members executing specialized work<br>
|
||||
- **D:** Team Captains ensuring quality and mission alignment<br>
|
||||
- **M:** Team-specific automation and reporting tools<br>
|
||||
|
||||
#### **4_roles (Individual Level)**
|
||||
- **A:** Role holders claiming and completing tasks<br>
|
||||
- **D:** Buddy System partners providing peer review<br>
|
||||
- **M:** Engelbot tracking SC awards and performance metrics<br>
|
||||
|
||||
#### **5_objectives (Project Level)**
|
||||
- **A:** Mission Leaders driving objective completion<br>
|
||||
- **D:** Science Team validating technical soundness<br>
|
||||
- **M:** Automated milestone tracking and progress reporting<br>
|
||||
|
||||
#### **6_tasks (Action Level)**
|
||||
- **A:** Task assignees executing specific deliverables<br>
|
||||
- **D:** Peer reviewers ensuring quality standards<br>
|
||||
- **M:** Automated task routing and completion verification<br>
|
||||
|
||||
---
|
||||
|
||||
## **Part 3: The 4 Phases of Creation Management**
|
||||
|
||||
This section defines how we orchestrate phase transitions through democratic validation.
|
||||
|
||||
### 4.1. Phase Transition Governance
|
||||
Each phase advancement requires both technical milestones and community validation:
|
||||
|
||||
**Validation → Design Phase:**<br>
|
||||
- Technical: Crowdfunding target met, founding team assembled<br>
|
||||
- Democratic: Binding vote by all owners on advancement readiness<br>
|
||||
- Operational: Team structure formalized, OSBP approved<br>
|
||||
|
||||
**Design → Production Phase:**<br>
|
||||
- Technical: All blueprints completed, prototype validated<br>
|
||||
- Democratic: Science Team peer review approval, community confidence vote<br>
|
||||
- Operational: Production infrastructure ready, quality standards defined<br>
|
||||
|
||||
**Production → Organization Phase:**<br>
|
||||
- Technical: MVP launched, user feedback integrated<br>
|
||||
- Democratic: Sustainability metrics met, community growth targets achieved<br>
|
||||
- Operational: Governance systems proven, leadership succession planned<br>
|
||||
|
||||
### 4.2. Phase Health Monitoring
|
||||
We maintain continuous oversight of organizational health across phases:
|
||||
|
||||
- **Community Metrics:** Owner growth, participation rates, vote turnout<br>
|
||||
- **Financial Health:** Treasury balance, SC redemption capacity, revenue pipeline<br>
|
||||
- **Technical Progress:** Milestone completion, quality metrics, bug rates <br>
|
||||
- **Democratic Legitimacy:** Conflict resolution success, consensus achievement<br>
|
||||
|
||||
---
|
||||
|
||||
## 4. Submissions: The Operational Roadmap
|
||||
|
||||
| Objective ID | Submission Title | Core Goal | Status |
|
||||
| :--- | :--- | :--- | :--- |
|
||||
| `5_1_7_1...` | **Blueprint Template System** | Create standardized templates for external blueprint updates ensuring consistency and completeness | :material-calendar: Planned |
|
||||
| `5_2_7_2...` | **ADM Implementation Guide** | Document specific ADM triangle implementations for each team and operational level | :material-calendar: Planned |
|
||||
| `5_3_7_3...` | **Phase Transition Automation** | Build Engelbot workflows for automated phase health monitoring and transition management | :material-calendar: Planned |
|
||||
| `5_4_7_4...` | **Conflict Resolution Protocols** | Establish clear procedures for handling disputes and unresolved issues in democratic processes | :material-calendar: Planned |
|
||||
|
||||
## 5. Role Management: Call for Contributions
|
||||
|
||||
To build a smoothly functioning operational system, we need process-oriented and systems-thinking contributors.
|
||||
|
||||
| Role ID | Role Title | Your Mission If You Join |
|
||||
| :--- | :--- | :--- |
|
||||
| `4_1_7` | **Process Architect** | You will design and refine the operational workflows that make democratic governance efficient and transparent. |
|
||||
| `4_2_7` | **Quality Standards Lead** | You will establish and maintain quality benchmarks across all teams, ensuring professional excellence at scale. |
|
||||
| `4_3_7` | **Community Health Monitor** | You will track and analyze community engagement metrics, identifying early warning signs and optimization opportunities. |
|
||||
| `4_4_7` | **Automation Specialist** | You will work with Development Team to build Engelbot workflows that reduce administrative overhead and increase transparency. |
|
||||
|
||||
## 6. Team Budget
|
||||
|
||||
| Item | Value (SC) | Status |
|
||||
| :--- | :--- | :--- |
|
||||
| **Total Phase 1 Budget:** | 0 | Awaiting initial crowdfunding |
|
||||
| **SC Minted to Date:** | 0 | - |
|
||||
| **Template Development:** | 150 SC | Priority allocation for blueprint standardization |
|
||||
| **Process Documentation:** | 200 SC | Critical for onboarding and scaling |
|
||||
| **Remaining Budget:** | 0 | Process optimization scales with community growth |
|
||||
Loading…
Reference in New Issue