This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

title	author	role	date	parent	wiki	public
Task Management System	robbert	4_1_1	2025-10-04	2_workplace	1_general_forum	true

Task Management System

🎯 Smartup Zero Task Management System

Version: 1.0
Status: Operational
Location: This document describes how Smartup Zero organizes work using Forgejo's native issue tracking, integrated with the Smartup ledger and ADM governance model.

---

🧠 Philosophy: ADM at Every Scale

The Attacker-Defender-Midfielder (ADM) model isn't just for individual tasks - it's our governance architecture at every organizational level:

Level	Attacker (Executes)	Defender (Oversees)	Midfielder (Orchestrates)
Organization (5_X)	2_workplace (all workers)	1_general_forum (all owners)	Engelbot
Teams (5_X_Y)	3_1_leadership_team (founders)	2_workplace (workers)	Engelbot
Tasks (6_X_Y_Z)	4_2_X (senior role)	4_3_X (junior role)	Engelbot

Why this matters:
At each level, the Attacker has execution responsibility, the Defender provides democratic oversight and accountability, and the Midfielder (Engelbot) ensures coordination and transparency.

This creates nested accountability: power flows down (attackers drive work), but oversight flows up (defenders can challenge, vote, block).

---

🏗️ Structure: Three-Tier Hierarchy

Smartup Zero uses Forgejo's native features (repos, issues, projects, labels, dependencies) to mirror the organizational structure defined in the ledger.

Tier 1: 1_general_forum (Public Governance)

Purpose: Democratic oversight of the entire Smartup.

Feature	Usage
Projects	4 Phases of Creation (Validation → Design → Production → Organization)
Issues	5_X - Organization-wide objectives
Labels	AD: 2_workplace (Attacker), 1_general_forum (Defender)
Assignee	@engelbot (Midfielder)

Example Issue:
5_1 - "Complete Validation Phase: Prove ONLIFE solves emergency communication"

---

Tier 2: 2_workplace (Operational Hub)

Purpose: Coordinate cross-team work and hold leadership accountable.

Feature	Usage
Projects	5_X - Mirrors org objectives (with URL link to 1_GF issue)
Issues	5_X_Y - Team-specific objectives
Labels	AD: 3_1_leadership_team (Attacker), 2_workplace (Defender)
Assignee	@engelbot (Midfielder)

Example Issue:
5_1_3 - "Develop mesh network cryptographic protocol" (under org objective 5_1)

Link: Issue description contains URL to parent 5_1 in 1_general_forum.

---

Tier 3: 3_X_team (Execution Level)

Purpose: Seven specialized teams execute tasks.

Feature	Usage
Projects	5_X_Y - Mirrors team objectives (with URL link to 2_WP issue)
Issues	6_X_Y_Z - Individual tasks (actual work)
Labels	4_X - Team-specific roles (can be Attacker or Defender)
Assignee	@engelbot (Midfielder)
Dependencies	Links to parent issues in 2_workplace and 1_general_forum

Example Issue:
6_1_3_2 - "Implement DHT peer discovery algorithm"

• Parent: 5_1_3 (team objective in 2_workplace)
• Root: 5_1 (org objective in 1_general_forum)
• Labels: 4_2_3_developer_senior (Attacker), 4_3_3_developer_junior (Defender)

---

📊 Visual Hierarchy

graph TD
    subgraph 1_GF["🏛️ 1_general_forum (All Owners)"]
        PHASE["📋 Project: Validation Phase"]
        OBJ_ORG["📌 Issue 5_1: Complete Validation\n🏷️ AD: 2_workplace (A) / 1_general_forum (D)\n<><6E> @engelbot"]
    end

    subgraph 2_WP["🏢 2_workplace (All Workers)"]
        PROJ_ORG["📋 Project: 5_1 (mirrors 1_GF issue)"]
        OBJ_TEAM["📌 Issue 5_1_3: Build mesh protocol\n🏷️ AD: 3_1_leadership (A) / 2_workplace (D)\n👤 @engelbot"]
    end

    subgraph 3_3["💻 3_3_developer_team"]
        PROJ_TEAM["📋 Project: 5_1_3 (mirrors 2_WP issue)"]
        TASK["📌 Issue 6_1_3_2: Implement DHT\n🏷️ 4_2_3_senior (A) / 4_3_3_junior (D)\n👤 @engelbot\n🔗 Dependencies: 5_1_3, 5_1"]
    end

    PHASE --> OBJ_ORG
    OBJ_ORG -->|"URL in description"| PROJ_ORG
    PROJ_ORG --> OBJ_TEAM
    OBJ_TEAM -->|"URL in description"| PROJ_TEAM
    PROJ_TEAM --> TASK
    TASK -.->|"Forgejo dependency"| OBJ_TEAM
    TASK -.->|"Forgejo dependency"| OBJ_ORG

    style OBJ_ORG fill:#e1f5ff
    style OBJ_TEAM fill:#fff4e1
    style TASK fill:#e8f5e9

---

🔄 The Cascade: How Work Flows

1. Strategic Direction (General Forum)

Founders/owners vote on organization-wide objectives (5_X) in 1_general_forum.
These define what the Smartup must achieve.

2. Tactical Breakdown (Workplace)

Leadership breaks org objectives into team objectives (5_X_Y) in 2_workplace.
Each team gets clear sub-goals.

3. Execution (Teams)

Team Captains create tasks (6_X_Y_Z) in team repos.
Workers claim, complete, and get assessed.

4. Accountability Flows Up

• Workers (2_workplace) can challenge team objectives if leadership is off-track.
• All owners (1_general_forum) can challenge org objectives if the Smartup is losing focus.
• Defenders at each level have veto power via voting.

---

🤖 Engelbot Integration

Engelbot is the Midfielder at every level, ensuring coordination between Forgejo (task tracking) and the Ledger (currency, ownership, audit trail).

Key Commands (Planned)

Command	Effect	Writes To
!create_objective --level org --title "..."	Creates issue in 1_general_forum + project in 2_workplace	ledger/objectives/registry.csv
!create_objective --level team --parent 5_1 --title "..."	Creates issue in 2_workplace + project in 3_X_team	ledger/objectives/registry.csv
!create_task --objective 5_1_3 --title "..."	Creates issue in team repo with dependencies	ledger/task-management/task-budgets.csv
!assign_task 6_1_3_2 --attacker alice --defender bob	Sets AD labels, updates issue	ledger/task-management/task_claimed.csv

All commands log to master-events.csv for auditability.

---

🎯 Why This Design?

✅ Respects Forgejo's Constraints

• No cross-repo projects → we use "mirror projects" with URL links
• Native dependency system → tasks automatically link to parent objectives
• Labels are local → each repo has team-specific role labels

✅ Embeds Governance

• AD labels signal accountability at every level
• Defenders can see all work their attackers are responsible for
• Engelbot assignee = system-managed (not personal ownership)

✅ Creates Audit Trail

• Forgejo dependencies show lineage (task → team obj → org obj)
• Issue history shows who changed what, when
• Combined with master-events.csv, we have forensic transparency

✅ Scales Democratically

• 1 founder can bootstrap
• 7 team captains can operate independently
• 100+ workers can self-organize into ADM pairs
• All owners retain oversight via defender role

---

🚧 Known Limitations (MVP)

1. URL Links Are Brittle

If you delete/recreate an issue, links break.
Mitigation: Don't delete issues; close and archive instead.

2. Cross-Repo Queries Are Manual

Forgejo doesn't aggregate issues across repos well.
Mitigation: Engelbot provides unified views (!tasks --all, !objectives --cascade).

3. No Milestones Yet

We haven't found a use case.
Future: Consider for phase gates or budget cycles.

4. Learning Curve

New captains find the tier system confusing at first.
Mitigation: This document + captain onboarding checklist.

---

🔮 Future Enhancements

• Auto-sync projects: Engelbot creates mirror projects automatically when objectives are created
• Dependency validation: Check that tasks properly link to parent objectives
• Burndown reports: Generate phase progress dashboards from Forgejo data
• Voting integration: Defenders can trigger votes directly from issue comments

---

📚 Related Documentation

• Smartup Model - Organizational philosophy
• ADM System - Detailed explanation of Attacker-Defender-Midfielder
• [Ledger Structure](../../2