Smartup_Zero/1_general_forum
Smartup_Zero/1_general_forum
2
0
Fork 0
Code Issues 2 Pull requests Projects 1 Releases Packages Wiki Activity
Page: slog_experiment_2025 10 02_robbert
Pages
1_general_forum 2_workplace 3_teams 4_roles 5_objectives 6_3_2_0_design_forgejo_api_write_layer_for_ledger 6_4_2_0_implement_forgejo_apipy_module 6_5_2_0_refactor_team_captain_scripts_to_forgejo_api 6_8_6_0_emergency_session_for_write_issue_in_master_event 6_tasks Book_of_Owners Home Leaderboard SLOGS how_to_write_a_readmemd sessionlog_task6_8_6_0 slog_ethos slog_ethos_2025 10 01_robbert slog_ethos_2025 10 08_robbert slog_experiment slog_experiment_2025 10 02_robbert slog_governance slog_meta slog_meta_2025 10 04_robbert task_management_system
1 slog_experiment_2025 10 02_robbert
robbert_founder edited this page 2025-10-04 12:57:05 +02:00
Unescape Escape
Table of Contents
This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

author role team topic public title date
robbert 4_1_1 3_1_leadership_team experiment true Wiki structre and Slog Session 2025-10-02

Wiki structre and Slog Session

Description of Change

In this work session, we collaboratively designed, codified, and implemented the canonical wiki + slogging system (SLOG) for SmartupOS. The primary aim was to solve Forgejo UI limitations (folders not showing), enforce wiki-wide consistency, and implement the first working role-anchored logbook system.

We moved from raw pseudo-code drafts to fully aligned policies (wiki_policies.yml v2.4), a rewritten bootstrap_wiki.py, and a working MVP of start_slog.py capable of generating role/team anchored SLOG entries reproducibly.

Why

  • For SmartupOS to function as a socio-technical organism, it requires not only ledger memory (what) but also human voices (why).
  • Existing Forgejo wiki UX is flat — folders invisible → risk of entropy and broken UX.
  • Needed a constitutionally enforced structure: dashboards as numbered pages, slog system as structured subpages, everything script-driven.

How

  • Clarified wiki rules:

    1. home.md always master index.
    2. Pages prefixed 1_…6_ and SLOGS.md are always main pages.
    3. All others are immediate subpages (max one level down).
    4. First numbered page = dashboard (live metrics).
    5. No manual edits via Forgejo UI — only script-driven.

  • Rewrote wiki_policies.yml v2.4

    • Flattened schema: no folders, only .md.
    • Added slog_ethos.md, slog_experiment.md, slog_governance.md, slog_meta.md as subpages of SLOGS.md.
    • Defined navigation rules: show mainpages + one subpage layer.

  • Rewrote bootstrap_wiki.py → now:

    • Creates home.md and all main pages + slog category subpages.
    • Auto-indexes home.md with links to mainpages + subpages.
    • Logs into master-events.csv.

  • Built start_slog.py (MVP) → robust and works:

    • CLI + bot mode.
    • Resolves team based on role:
      • 4_x_x → logs in team repo.
      • No role → logs in 2_workplace.
    • If public: true → duplicates slog into 1_general_forum.wiki.
    • Appends entry link to relevant category index (slog_experiment.md, etc).
    • Logs event row into ledger.
    • Solved regex bug in slugify → now generates clean file names.

  • Tested successfully by robbert (4_1_1) → created first ethos slog.

What

  • Canonical wiki scaffolding system delivered.
  • SLOG pipeline delivered.
  • Both functioning in alignment with Smartup Constitution.
  • MVP ready for further build:
    • next generate_public_pages.py update → publish feeds on timeline0.org.

Insights

  • Flat wiki model was the right move: Forgejo simply won’t show nested dirs.
  • Dividing factual memory (ledger → dashboards) vs. voice memory (slogs → category pages) makes SmartupOS novel vs. DAOs/coops.
  • Debugging live with regex errors + repo placement confirmed importance of constitutional rules (no ambiguity).
  • Public duplication into Forum wiki → solves transparency elegantly (no scraping all repos individually).

Next Steps

  1. Extend generate_public_pages.py to gather public SLOGs from 1_general_forum.wiki and render feeds (global/team/topic) → publish on timeline0.org.
  2. Implement SK bonuses (award_slog_sk.py) for weekly / public slogging.
  3. Future: Engelbot !slog_new interactive flow → prompt → call start_slog.py in bot mode.
  4. Longer-term: data mining of slog frequency/diversity as vital metric of organizational health.