Smartup_Zero/2_workplace
Smartup_Zero/2_workplace
2
0
Fork 0
Code Issues 25 Pull requests Projects 3 Releases Packages Wiki Activity

5_10_0 Social Karma System for Validation Phase #17

New issue
Open
opened 2026-02-21 10:24:35 +00:00 by robbert_founder · 0 comments
robbert_founder commented 2026-02-21 10:24:35 +00:00
Owner
Copy link

5_10_0 - Social Karma System for Validation Phase

Summary

Implement the Social Karma (SK) infrastructure: peer recognition, captain awards,
activity-based engagement tracking, monthly decay, governance action framework,
and Engelbot room scoping — giving all owners the tools to earn reputation through
stewardship and enabling progressive governance privileges.

Why

SC rewards craftsmanship. SK rewards stewardship. Without SK tooling:

  1. No path to leadership. The constitution requires 100 SK to run for captain,
    200 SK for mission leader, 500 SK for leadership team. Without earning mechanisms,
    external contributors are permanently locked out of governance — violating
    "Separate Wealth from Power."

  2. No accountability signal. Captains currently have authority without measurable
    community trust. SK makes trust visible and current (10% monthly decay means
    yesterday's hero must keep contributing).

  3. No engagement incentive. Watch license holders and new Work contributors
    have no reward for governance participation — reading, commenting, reviewing,
    voting. SK bridges the gap between "observer" and "active citizen."

  4. No governance tooling. The constitution defines votes, proposals, and
    deliberation, but there's no infrastructure to run them. Contributors can't
    exercise their ownership responsibilities without tools.

  5. Experiment validity at risk. The hypothesis is that collective ownership
    works. If we launch validation without SK, we're testing collective ownership
    with only individual reward mechanisms (SC). That's half the experiment.

Before Experiment Launch, external contributors need to see a clear path:
contribute → earn trust → gain influence → shape the organization. SK is that path.

How

Three SK earning mechanisms, one decay mechanism, one query system,
and one infrastructure prerequisite:

Mechanism 1: Peer Recognition (!kudos)

Any owner nominates another for SK with a reason and category.
Captain batch-reviews weekly. Nominator earns 2 SK for recognizing others.
Low friction, high visibility, encourages peer appreciation.

Mechanism 2: Captain Direct Award (!award_sk)

Captains award SK directly within a weekly budget of 50 SK.
Concentration flag triggers if >20% (10 SK) goes to one person in a week —
doesn't block, but creates a public audit record requiring justification.
Enables fast recognition of governance contributions captains observe directly.

Mechanism 3: Activity Engagement (automated)

Engelbot silently tracks presence across rooms (binary per dimension,
not volume). Weekly score calculated from: team room presence, workplace
presence, forum presence, Engelbot usage, thread responses, timely replies.
Max 3 SK/week. Run monthly, captain confirms. Opt-out available.

Decay: Monthly 10%

Automated script reduces all SK balances by 10% monthly.
Prevents founder privilege, rewards active contribution, makes room
for new leaders. 30-day grace period for new members.

Governance Action Framework

Extensible pattern for structured governance: deliberation, voting,
focus groups, reviews. Each follows INVOKE → PREPARE → PARTICIPATE →
CONCLUDE → REWARD lifecycle. Validation phase implements deliberation
and voting. Framework supports future tools without new architecture.

Engelbot Room Scoping (prerequisite)

Configure which commands work in which rooms. DM = full access.
Team rooms = team-relevant only. Captain rooms = captain operations.
Unscoped commands redirect to DM with helpful message. Prevents
command wizard noise in public rooms.

What

Core Infrastructure

  1. governance-actions.csv — Ledger for all governance actions
    (kudos, deliberations, votes, focus groups, reviews) with unified schema
  2. activity-log.csv — Weekly binary activity tracking per owner
  3. engelbot-room-config.yml — Room-to-command permission mapping
  4. Engelbot room scoping — Check room type before executing commands,
    redirect disallowed commands to DM

Scripts (Python)

Script Folder Purpose
kudos.py workers/ Create SK nomination (any active owner)
review_kudos.py teamcaptain/ Batch review pending nominations
award_sk.py teamcaptain/ Direct captain SK award (50/week budget, 20% flag)
start_deliberation.py teamcaptain/ Open structured discussion with timeline
conclude_deliberation.py teamcaptain/ Close deliberation, distribute participation SK
propose_vote.py workers/ Create formal vote (requires 50+ SK)
cast_vote.py workers/ Cast vote with reason
conclude_vote.py teamcaptain/ Tally results, distribute voter SK
track_activity.py teamcaptain/ Calculate weekly activity scores from log
calculate_activity_sk.py teamcaptain/ Monthly activity → SK proposals, captain confirms
decay_sk.py teamcaptain/ Apply monthly 10% decay to all owners
show_sk.py queries/ SK balance, history, leaderboard

Engelbot Handlers (TypeScript)

Command Permission Room Scope
!kudos @alias amount category "reason" Any owner team, workplace
!review_kudos Captain/Founder captain_room, dm
!approve_kudos 047 048 Captain/Founder captain_room, dm
!reject_kudos 048 "reason" Captain/Founder captain_room, dm
!award_sk @alias amount category "reason" Captain/Founder captain_room, dm
!deliberation start/conclude Captain/Founder workplace, team
!vote propose/cast/conclude 50+ SK / Any owner / Captain forum, workplace
!sk or !my_sk Any owner all rooms
!sk_board Any owner all rooms
!activity_optout / !activity_optin Any owner dm

Toolbox API Routes

Route Method Maps To
/api/kudos POST kudos.py
/api/review_kudos POST review_kudos.py
/api/award_sk POST award_sk.py
/api/start_deliberation POST start_deliberation.py
/api/conclude_deliberation POST conclude_deliberation.py
/api/propose_vote POST propose_vote.py
/api/cast_vote POST cast_vote.py
/api/conclude_vote POST conclude_vote.py
/api/calculate_activity_sk POST calculate_activity_sk.py
/api/decay_sk POST decay_sk.py
/api/show_sk GET show_sk.py

Policy Updates

  • karma-rules.yml — Update with captain budget (50/week), concentration flag (20%),
    activity scoring algorithm, opt-out mechanism
  • portfolio-policy.yml — Add governor.md integration spec
  • Update update_portfolio.py governor.md section once governance data flows

✅ Definition of Success

  1. Any owner can run !kudos in a team room and the nomination appears publicly,
    gets batch-reviewed by captain, and SK lands in the nominee's balance within 7 days.

  2. Captains can run !award_sk in their captain room, staying within 50 SK/week budget,
    with automatic concentration flags visible in master-events.csv.

  3. Activity SK is calculated monthly from silent engagement tracking.
    Scores and awards are published transparently. Any owner can opt out.

  4. SK decay runs monthly, reducing all balances by 10%.
    book-of-owners.csv reflects current SK. Portfolio governor.md shows history.

  5. !deliberation enables a captain to open a time-boxed structured discussion,
    track participants, and distribute SK on conclusion.

  6. !vote enables formal proposals, voting with SK-weighted tallies,
    and automated conclusion with quorum checks.

  7. Engelbot room scoping prevents command noise —
    wizard flows only appear where appropriate, everything else redirects to DM.

  8. A new contributor joining during validation can see a clear path:
    be present (activity SK) → recognize peers (kudos) → participate in governance
    (deliberation/vote SK) → reach 100 SK → run for captain.
    This path is visible on timeline0.org.

  9. All SK transactions are logged to social-karma/transactions.csv,
    all governance actions to governance-actions.csv,
    all mutations to master-events.csv. Full auditability.

  10. The litmus test: If someone asks "how do I become a captain?"
    Engelbot can answer with a concrete, measurable path that doesn't
    require money or knowing the right people.

✅ Definition of Done (Autogenerated)

Progress (Autogenerated)

Progress: 0% (0/6 tasks complete)

Status Count
🔄 In Progress 1
📌 Assigned 1
📂 Open 4

Last Activity: 2026-03-04 by @robbert

Health: 🔴 Inactive

Objective Information

  • ID: 5_10_0
  • Type: team
  • Phase: pre-validation
  • Parent: 5_0
  • Status: active
  • Created By: robbert on 2026-02-21T10:25:23.732974Z
  • Forgejo: #17

Governance (ADM)

  • Attacker: 3_1
  • Defender: 3_7
  • Midfielder: Engelbot
# 5_10_0 - Social Karma System for Validation Phase ## Summary Implement the Social Karma (SK) infrastructure: peer recognition, captain awards, activity-based engagement tracking, monthly decay, governance action framework, and Engelbot room scoping — giving all owners the tools to earn reputation through stewardship and enabling progressive governance privileges. ## Why SC rewards craftsmanship. SK rewards stewardship. Without SK tooling: 1. **No path to leadership.** The constitution requires 100 SK to run for captain, 200 SK for mission leader, 500 SK for leadership team. Without earning mechanisms, external contributors are permanently locked out of governance — violating "Separate Wealth from Power." 2. **No accountability signal.** Captains currently have authority without measurable community trust. SK makes trust visible and current (10% monthly decay means yesterday's hero must keep contributing). 3. **No engagement incentive.** Watch license holders and new Work contributors have no reward for governance participation — reading, commenting, reviewing, voting. SK bridges the gap between "observer" and "active citizen." 4. **No governance tooling.** The constitution defines votes, proposals, and deliberation, but there's no infrastructure to run them. Contributors can't exercise their ownership responsibilities without tools. 5. **Experiment validity at risk.** The hypothesis is that collective ownership works. If we launch validation without SK, we're testing collective ownership with only individual reward mechanisms (SC). That's half the experiment. Before Experiment Launch, external contributors need to see a clear path: contribute → earn trust → gain influence → shape the organization. SK is that path. ## How Three SK earning mechanisms, one decay mechanism, one query system, and one infrastructure prerequisite: ### Mechanism 1: Peer Recognition (`!kudos`) Any owner nominates another for SK with a reason and category. Captain batch-reviews weekly. Nominator earns 2 SK for recognizing others. Low friction, high visibility, encourages peer appreciation. ### Mechanism 2: Captain Direct Award (`!award_sk`) Captains award SK directly within a weekly budget of 50 SK. Concentration flag triggers if >20% (10 SK) goes to one person in a week — doesn't block, but creates a public audit record requiring justification. Enables fast recognition of governance contributions captains observe directly. ### Mechanism 3: Activity Engagement (automated) Engelbot silently tracks presence across rooms (binary per dimension, not volume). Weekly score calculated from: team room presence, workplace presence, forum presence, Engelbot usage, thread responses, timely replies. Max 3 SK/week. Run monthly, captain confirms. Opt-out available. ### Decay: Monthly 10% Automated script reduces all SK balances by 10% monthly. Prevents founder privilege, rewards active contribution, makes room for new leaders. 30-day grace period for new members. ### Governance Action Framework Extensible pattern for structured governance: deliberation, voting, focus groups, reviews. Each follows INVOKE → PREPARE → PARTICIPATE → CONCLUDE → REWARD lifecycle. Validation phase implements deliberation and voting. Framework supports future tools without new architecture. ### Engelbot Room Scoping (prerequisite) Configure which commands work in which rooms. DM = full access. Team rooms = team-relevant only. Captain rooms = captain operations. Unscoped commands redirect to DM with helpful message. Prevents command wizard noise in public rooms. ## What ### Core Infrastructure 1. **`governance-actions.csv`** — Ledger for all governance actions (kudos, deliberations, votes, focus groups, reviews) with unified schema 2. **`activity-log.csv`** — Weekly binary activity tracking per owner 3. **`engelbot-room-config.yml`** — Room-to-command permission mapping 4. **Engelbot room scoping** — Check room type before executing commands, redirect disallowed commands to DM ### Scripts (Python) | Script | Folder | Purpose | |--------|--------|---------| | `kudos.py` | workers/ | Create SK nomination (any active owner) | | `review_kudos.py` | teamcaptain/ | Batch review pending nominations | | `award_sk.py` | teamcaptain/ | Direct captain SK award (50/week budget, 20% flag) | | `start_deliberation.py` | teamcaptain/ | Open structured discussion with timeline | | `conclude_deliberation.py` | teamcaptain/ | Close deliberation, distribute participation SK | | `propose_vote.py` | workers/ | Create formal vote (requires 50+ SK) | | `cast_vote.py` | workers/ | Cast vote with reason | | `conclude_vote.py` | teamcaptain/ | Tally results, distribute voter SK | | `track_activity.py` | teamcaptain/ | Calculate weekly activity scores from log | | `calculate_activity_sk.py` | teamcaptain/ | Monthly activity → SK proposals, captain confirms | | `decay_sk.py` | teamcaptain/ | Apply monthly 10% decay to all owners | | `show_sk.py` | queries/ | SK balance, history, leaderboard | ### Engelbot Handlers (TypeScript) | Command | Permission | Room Scope | |---------|------------|------------| | `!kudos @alias amount category "reason"` | Any owner | team, workplace | | `!review_kudos` | Captain/Founder | captain_room, dm | | `!approve_kudos 047 048` | Captain/Founder | captain_room, dm | | `!reject_kudos 048 "reason"` | Captain/Founder | captain_room, dm | | `!award_sk @alias amount category "reason"` | Captain/Founder | captain_room, dm | | `!deliberation start/conclude` | Captain/Founder | workplace, team | | `!vote propose/cast/conclude` | 50+ SK / Any owner / Captain | forum, workplace | | `!sk` or `!my_sk` | Any owner | all rooms | | `!sk_board` | Any owner | all rooms | | `!activity_optout` / `!activity_optin` | Any owner | dm | ### Toolbox API Routes | Route | Method | Maps To | |-------|--------|---------| | `/api/kudos` | POST | kudos.py | | `/api/review_kudos` | POST | review_kudos.py | | `/api/award_sk` | POST | award_sk.py | | `/api/start_deliberation` | POST | start_deliberation.py | | `/api/conclude_deliberation` | POST | conclude_deliberation.py | | `/api/propose_vote` | POST | propose_vote.py | | `/api/cast_vote` | POST | cast_vote.py | | `/api/conclude_vote` | POST | conclude_vote.py | | `/api/calculate_activity_sk` | POST | calculate_activity_sk.py | | `/api/decay_sk` | POST | decay_sk.py | | `/api/show_sk` | GET | show_sk.py | ### Policy Updates - `karma-rules.yml` — Update with captain budget (50/week), concentration flag (20%), activity scoring algorithm, opt-out mechanism - `portfolio-policy.yml` — Add governor.md integration spec - Update `update_portfolio.py` governor.md section once governance data flows ## ✅ Definition of Success 1. **Any owner** can run `!kudos` in a team room and the nomination appears publicly, gets batch-reviewed by captain, and SK lands in the nominee's balance within 7 days. 2. **Captains** can run `!award_sk` in their captain room, staying within 50 SK/week budget, with automatic concentration flags visible in master-events.csv. 3. **Activity SK** is calculated monthly from silent engagement tracking. Scores and awards are published transparently. Any owner can opt out. 4. **SK decay** runs monthly, reducing all balances by 10%. `book-of-owners.csv` reflects current SK. Portfolio governor.md shows history. 5. **`!deliberation`** enables a captain to open a time-boxed structured discussion, track participants, and distribute SK on conclusion. 6. **`!vote`** enables formal proposals, voting with SK-weighted tallies, and automated conclusion with quorum checks. 7. **Engelbot room scoping** prevents command noise — wizard flows only appear where appropriate, everything else redirects to DM. 8. **A new contributor** joining during validation can see a clear path: be present (activity SK) → recognize peers (kudos) → participate in governance (deliberation/vote SK) → reach 100 SK → run for captain. This path is visible on timeline0.org. 9. **All SK transactions** are logged to `social-karma/transactions.csv`, all governance actions to `governance-actions.csv`, all mutations to `master-events.csv`. Full auditability. 10. **The litmus test:** If someone asks "how do I become a captain?" Engelbot can answer with a concrete, measurable path that doesn't require money or knowing the right people. ## ✅ Definition of Done (Autogenerated) <!-- SMARTUPOS:AUTOGEN:DOD:BEGIN --> - [ ] [6_1_10_0 - SK Framework: governance-actions.csv + award/decay core](https://forge.timeline0.org/Smartup_Zero/3_1_leadership_team/issues/79) - [ ] [6_2_10_0 - Implement kudos.py + review_kudos.py](https://forge.timeline0.org/Smartup_Zero/3_1_leadership_team/issues/80) - [ ] [6_3_10_0 - Implement award_sk.py (captain direct)](https://forge.timeline0.org/Smartup_Zero/3_1_leadership_team/issues/81) - [ ] [6_4_10_0 - Implement deliberation.py (start/conclude)](https://forge.timeline0.org/Smartup_Zero/3_1_leadership_team/issues/82) - [ ] [6_5_10_0 - Implement vote.py (propose/cast/conclude)](https://forge.timeline0.org/Smartup_Zero/3_1_leadership_team/issues/83) - [ ] [6_6_10_0 - Implement activity tracking + calculate_activity_sk.py](https://forge.timeline0.org/Smartup_Zero/3_1_leadership_team/issues/84) <!-- SMARTUPOS:AUTOGEN:DOD:END --> ## Progress (Autogenerated) <!-- SMARTUPOS:AUTOGEN:PROGRESS:BEGIN --> **Progress: 0%** (0/6 tasks complete) | Status | Count | |--------|-------| | 🔄 In Progress | 1 | | 📌 Assigned | 1 | | 📂 Open | 4 | **Last Activity:** 2026-03-04 by @robbert **Health:** 🔴 Inactive <!-- SMARTUPOS:AUTOGEN:PROGRESS:END --> --- ## Objective Information - **ID:** 5_10_0 - **Type:** team - **Phase:** pre-validation - **Parent:** 5_0 - **Status:** active - **Created By:** robbert on 2026-02-21T10:25:23.732974Z - **Forgejo:** https://forge.timeline0.org/Smartup_Zero/2_workplace/issues/17 ## Governance (ADM) - **Attacker:** 3_1 - **Defender:** 3_7 - **Midfielder:** Engelbot ---
robbert_founder changed title from Social Karma System for Validation Phase to 5_10_0 Social Karma System for Validation Phase 2026-02-21 10:26:01 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
dev_local
corrupt-csv
robbert_ledger_local_fix
No results found.
Labels
Clear labels   
2_workplace

attacker

  
3_1_leadership_team

defender

  
objective

Role: objective

  
pre-validation

Role: pre-validation

  
team-objective

Role: team-objective

  
validation

Role: validation

No labels
2_workplace
3_1_leadership_team
objective
pre-validation
team-objective
validation
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
5_0 SmartupOS MVP ready
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Smartup_Zero/2_workplace#17
No description provided.