5_9_0 Canonical Progress Dashboard #15

New issue

Open

opened 2026-01-22 03:29:19 +00:00 by robbert_founder · 0 comments

robbert_founder commented

2026-01-22 03:29:19 +00:00

Owner

5_9_0 - Canonical Progress Dashboard

Objective Overview

ID: 5_9_0
Type: team
Phase: pre-validation
Parent: 5_0
Status: active
Created By: robbert on 2026-01-22T03:30:50.105492Z
Forgejo: #15

Governance (ADM)

Attacker: 3_1
Defender: 3_7
Midfielder: Engelbot

Description

Summary

Establish a single canonical Markdown body structure for all Objectives (5_) and Tasks (6_), so progress can be computed from the ledger and rendered consistently in Forgejo projects/issues and via Engelbot commands.

Why

We cannot scale Smartup Zero with inconsistent descriptions and ad-hoc formatting. Without a standard:

Forgejo checklists and progress bars become unreliable.
Non-coders cannot read progress (they’ll rely on Engelbot).
Automation (sync scripts) risks overwriting important human context.
A canonical structure makes progress legible, auditable, and automatable.

How

We standardize all objective and task bodies into a shared template:

Summary → Why → How → What → Definition of Success → Definition of Done

Additionally:

The ledger remains the one source of truth for state (status, assignments, credits).
The wiki markdown files are canonical for content (Index–Content architecture).
Forgejo issue bodies and project boards mirror wiki + ledger.
Objectives contain an autogenerated Definition of Done checklist that is updated by scripts (not by humans), using fenced markers so automation never clobbers human-written sections.

What

Deliverables:

Canonical Markdown templates for:
- Objectives (5_*)
- Tasks (6_*)
Update create/update flows so all new/edited entities conform automatically:
- create_task.py
- update_task.py
- create_objective.py
- update_objective.py
Implement a “sync progress” flow:
- Computes objective progress from ledger states (cancelled excluded)
- Updates objective DoD checklist blocks
- Mirrors status/labels/links into Forgejo issues + project boards

✅ Definition of Success

This objective is successful when:

Every objective and task has a readable body with the canonical structure.
Objective progress can be computed automatically from ledger state and is visible:
- in Forgejo (checklist progress + correct board column)
- via Engelbot (e.g., !show 5_X_Y shows progress and child tasks)
Humans can edit narrative sections safely, while scripts only update marked autogenerated blocks.

✅ Definition of Done (Autogenerated)

Progress (Autogenerated)

Progress: 100% (5/5 tasks complete)

Status	Count
✅ Complete	5

Last Activity: 2026-02-18 by @robbert

Health: 🔴 Inactive

# 5_9_0 - Canonical Progress Dashboard ## Objective Overview - **ID:** 5_9_0 - **Type:** team - **Phase:** pre-validation - **Parent:** 5_0 - **Status:** active - **Created By:** robbert on 2026-01-22T03:30:50.105492Z - **Forgejo:** https://forge.timeline0.org/Smartup_Zero/2_workplace/issues/15 ## Governance (ADM) - **Attacker:** 3_1 - **Defender:** 3_7 - **Midfielder:** Engelbot ## Description ## Summary Establish a single canonical Markdown body structure for all Objectives (5_*) and Tasks (6_*), so progress can be computed from the ledger and rendered consistently in Forgejo projects/issues and via Engelbot commands. ## Why We cannot scale Smartup Zero with inconsistent descriptions and ad-hoc formatting. Without a standard: - Forgejo checklists and progress bars become unreliable. - Non-coders cannot read progress (they’ll rely on Engelbot). - Automation (sync scripts) risks overwriting important human context. A canonical structure makes progress legible, auditable, and automatable. ## How We standardize all objective and task bodies into a shared template: **Summary → Why → How → What → Definition of Success → Definition of Done** Additionally: - The **ledger remains the one source of truth** for state (status, assignments, credits). - The **wiki markdown files are canonical for content** (Index–Content architecture). - Forgejo issue bodies and project boards **mirror** wiki + ledger. - Objectives contain an **autogenerated Definition of Done checklist** that is updated by scripts (not by humans), using fenced markers so automation never clobbers human-written sections. ## What Deliverables: 1. Canonical Markdown templates for: - Objectives (5_*) - Tasks (6_*) 2. Update create/update flows so all new/edited entities conform automatically: - create_task.py - update_task.py - create_objective.py - update_objective.py 3. Implement a “sync progress” flow: - Computes objective progress from ledger states (cancelled excluded) - Updates objective DoD checklist blocks - Mirrors status/labels/links into Forgejo issues + project boards ## ✅ Definition of Success This objective is successful when: - Every objective and task has a readable body with the canonical structure. - Objective progress can be computed automatically from ledger state and is visible: - in Forgejo (checklist progress + correct board column) - via Engelbot (e.g., `!show 5_X_Y` shows progress and child tasks) - Humans can edit narrative sections safely, while scripts only update marked autogenerated blocks. ## ✅ Definition of Done (Autogenerated)  - [x] [6_1_9_0 - Update create_task.py to canonical body + objective DoD autogen](https://forge.timeline0.org/Smartup_Zero/3_1_leadership_team/issues/70) - [x] [6_2_9_0 - Update update_task.py to sync Objective DoD checklist (title + cancel)](https://forge.timeline0.org/Smartup_Zero/3_1_leadership_team/issues/71) - [x] [6_3_9_0 - Refactor create_objective for Canonical Progress Dashboard](https://forge.timeline0.org/Smartup_Zero/3_1_leadership_team/issues/72) - [x] [6_4_9_0 - Implement sync_progress.py for Progress Dashboard](https://forge.timeline0.org/Smartup_Zero/3_1_leadership_team/issues/73) - [x] [6_5_9_0 - Standardize Task Status Flow and Column Mapping](https://forge.timeline0.org/Smartup_Zero/3_1_leadership_team/issues/74)  ## Progress (Autogenerated)  **Progress: 100%** (5/5 tasks complete) | Status | Count | |--------|-------| | ✅ Complete | 5 | **Last Activity:** 2026-02-18 by @robbert **Health:** 🔴 Inactive  ---