Interest & Priorities — pick a module to work on

[coopeverything]

Your interest sets our build order. Comment with:

Module (choose up to 3):

• Decidim Integration
• Bri (Bridge) Assistant AI
• Member Profile (Contribution‑Forward UI)
• Support Points
• Learning Module Integration
• Proposal Builder
• Deliberation Room (with safeguards)
• Quorum + Minority‑Report Engine
• Reputation Ledger
• Social Horizon Wallet
• Mutual‑Aid & Time‑Bank
• Project Map (Global → Local)
• Media & Culture Hub
• Liquid Legislation Loop
• Identity & Delegation (Liquid Democracy)
• Notifications & Activity

Why I’m excited: <1–2 lines>
Skills & tools:
Starter approach: <MVP in tiny, verifiable steps>
Links: <portfolio/code>
Contact: <email on profile or Matrix/Signal/Discord>

✅ We triage daily. Declared interest boosts a module’s priority. We’ll reply and tag you when the scoped issue lands.

[coopeverything]

Below are modular, put‑your‑name‑on‑it tasks that directly advance TogetherOS. Each lists why it matters, what you’d build for a first MVP, the key interfaces, and a proof‑of‑delivery line.

Declaring interest boosts the module’s priority.

• Decidim (or similar) Governance Integration

  Why: Bring battle‑tested participatory processes into TogetherOS.

  MVP: SSO + embed of proposals and participatory budgeting; sync proposals into our Issue Pipeline (present→deliberate→vote→deliver).

  Interfaces: OAuth/OIDC SSO; Webhooks to our /api/proposals; read‑only embed in Next.js route /governance.

  Proof: Create a proposal in Decidim → visible & actionable in TogetherOS with status sync both ways.

• Bri (Bridge) Assistant — Deliberation Coach

  Why: Teach common‑good reasoning in‑flow.

  MVP: Chat panel that transforms a messy thread into claims → evidence → options → tradeoffs; prompts steel‑manning.

  Interfaces: /api/deliberation/summarize, /api/deliberation/checklist; UI component <BriCoach />.

  Proof: Given a sample thread, Bri outputs a structured brief and checklists; users can submit revised positions.

• Member Profile (Contribution‑Forward UI)

  Why: Replace follower clout with contribution reputation.

  MVP: Profile showing badges, recent deliveries, Support Points allocations, and “next tiny step.”

  Interfaces: /api/profile/:id, /api/reputation/:id, /api/support-points/:id.

  Proof: New contributions/badges appear on the profile; allocate points and see immediate impact.

• Support Points Service (MVP)

  Why: Turn attention into collective prioritization.

  MVP: 100‑point bank, max 10 per idea, anti‑gaming checks.

  Interfaces: /api/support-points/allocate, /api/ideas.

  Proof: Points allocation updates idea rankings and a personal ledger.

• Proposal Builder (Research→Options Flow)

  Why: Standardize good decision hygiene.

  MVP: Wizard that forces: problem → evidence → options → impacts → safeguards → metrics.

  Interfaces: Form schema + autosave to /api/proposals.

  Proof: Submitting creates a proposal page with all sections and a shareable link.

• Deliberation Room with Safeguards

  Why: Keep discourse productive.

  MVP: Thread with calm‑down timers, empathy prompts, and Bri plug‑ins for summarizing & steel‑manning.

  Interfaces: /api/moderation/cooldown, /api/deliberation/summary.

  Proof: Heat spike triggers a visible cool‑down; Bri summary pinned; thread stays on topic.

• Quorum & Minority‑Report Engine

  Why: Legitimacy + learning baked in.

  MVP: Configurable quorums (stakeholder/impact); minority report template with auto‑review triggers.

  Interfaces: /api/vote/start, /api/quorum/check, /api/minority-report.

  Proof: Passing a vote posts quorum details; a dissent file sets a timed review and re‑opens automatically on metric breach.

• Reputation Ledger (Positive‑Sum Status)

  Why: Reward public contribution, not popularity.

  MVP: Append‑only ledger of deliveries, peer thanks, and upheld dissent that improved outcomes.

  Interfaces: /api/reputation/events, /api/reputation/score.

  Proof: Completing a tiny step emits an event → score updates on profile.

• Social Horizon Wallet (Mock → MVP)

  Why: Seed the cooperative treasury economy.

  MVP: Non‑custodial mock wallet with balances, grants, and dividend receipts; later swap for real chain or ledger.

  Interfaces: /api/wallet, /api/treasury/grants.

  Proof: Grant disbursed → wallet balance updates; activity logged to profile.

• Mutual‑Aid & Time‑Bank Hub

  Why: Immediate real‑world value exchange.

  MVP: Post a need/offer; one‑click match; time‑bank accounting.

  Interfaces: /api/mutual-aid, /api/timebank.

  Proof: A match creates transactions in the ledger and sends notifications.

• Project Map (Global → Local)

  Why: See ourselves at work; recruit by place/skill.

  MVP: Map/list of cooperative projects with filters (pillar, skill, city); contribution button.

  Interfaces: /api/projects, map SDK.

  Proof: Adding a project renders on map; clicking “contribute” opens a scoped issue/task list.

• Learning Module Integration (Collaborative Education)

  Why: Make learning → action seamless; teach common‑good reasoning and skills in‑flow.

  MVP: Integrate a learning platform (e.g., Open edX/Moodle—or the specific module we discussed) for short, scenario‑based courses that unlock platform capabilities and Support Points.

  Interfaces: SSO (OIDC), course progress webhooks → /api/learning/progress, grant points via /api/support-points/grant.

  Proof: Completing a lesson awards points and unlocks a feature (e.g., proposal authoring), visible on the profile and ledger.

• Media & Culture Hub (Narrative Flip)

  Why: Crowd power to change the story.

  MVP: Submit/curate media pieces; up‑rank by Support Points; showcase “viral for good.”

  Interfaces: /api/media, /api/support-points.

  Proof: A featured story rises via points and displays attribution + reuse rights.

• Liquid Legislation Loop

  Why: Keep law subordinate to people.

  MVP: Timeline showing cycles (legislate→amend→monitor→iterate) with metrics and upcoming reviews.

  Interfaces: /api/law/cycle, /api/metrics/:id.

  Proof: Passing a policy auto‑schedules review and renders a live timeline.

• Identity & Delegation (Liquid Democracy)

  Why: Practical participation at scale.

  MVP: Delegate selection, per‑topic delegation, revoke any time; delegates count toward quorum.

  Interfaces: /api/delegation, /api/identity.

  Proof: A voter delegates on “Climate”; votes reflect delegate until revoked.

• Notifications & Activity (Motivation Loop)

  Why: Turn tiny steps into ongoing engagement.

  MVP: Digest and real‑time notifications: “Because you backed X, here’s the latest progress.”

  Interfaces: /api/notifications, web push.

  Proof: Allocating points triggers a confirmation and later a progress ping.

Your choice of module raises its priority.
The build is dynamic and community‑steered—tell us what you want to ship next.

What to do next

Go through the list of modules. Find which interests you more to work on.
Then open an issue to serve as an interest note: