# Community platform — contributor brief

Snapshot prepared 2026-11-14T08:56:17.308Z.

Project: https://cfh.retehost.com/projects/community-platform

This is a snapshot of published project context. Check current task status before starting. It does not assign work or authorize a release.

Program: Civic Infrastructure

Stage: BUILDING

License: MIT

## Purpose

The community and shared workspace behind Coders for Humanity.

## Problem

Contributors need one place to find people, discuss problems, and coordinate work across open-source projects.

## Goal

Build and operate the CFH community, project workspaces, and shared GitHub integration.

## Evidence and limits

The platform is in active development in the clearframeworks/coders-for-humanity repository.

## Architecture

Next.js and TypeScript application, PostgreSQL community data, and a dedicated public GitHub repository.

## Work in this project

7 recorded tasks. Each task retains its own scope and review requirements.

### Establish the independent harness team

https://cfh.retehost.com/work/cf100000-0000-4000-8000-000000000001

Status: OPEN

Discipline: Security

Experience: Specialist

Commitment: Ongoing

**Objective**

Give the community an accountable review team before widening release access.

**Context**

The platform is being handed to human maintainers. Contributor, reviewer and release authority must remain separate. No security team has been appointed yet.

**Acceptance criteria**

Publish consenting maintainer and security reviewer contacts; document conflicts of interest and coverage; configure protected main with required checks and fresh independent reviews; prove a failing pull request cannot merge; record provider evidence.

**Dependencies**

Owner appoints trusted reviewers and approves repository settings.

**Review needed**

Repository owner; independent security reviewer to be appointed

Prepare a personal handoff: https://cfh.retehost.com/workspace?task=cf100000-0000-4000-8000-000000000001

### Test the complete contribution journey for accessibility

https://cfh.retehost.com/work/cf100000-0000-4000-8000-000000000003

Status: OPEN

Discipline: Accessibility

Experience: Intermediate

Commitment: 3–8 hours

**Objective**

Make joining, finding work, discussing and submitting usable without a mouse.

**Context**

Automated checks cannot establish usability. Test the actual shared workflow in both color themes and on mobile.

**Acceptance criteria**

Complete the journey using keyboard and a screen reader; record focus order, announcements and errors; verify light/dark contrast and 200% zoom; file reproducible issues and retest fixes.

**Dependencies**

Stable preview; authenticated journey available for full coverage.

**Review needed**

Accessibility reviewer independent of the fixes

Prepare a personal handoff: https://cfh.retehost.com/workspace?task=cf100000-0000-4000-8000-000000000003

### Write the first human maintainer handoff

https://cfh.retehost.com/work/cf100000-0000-4000-8000-000000000004

Status: OPEN

Discipline: Documentation

Experience: First Contribution

Commitment: 1–3 hours

**Objective**

Let a new maintainer understand and continue the work without this chat.

**Context**

Use the repository, harness charter and current deployment evidence. Separate implemented code from configured services and future work.

**Acceptance criteria**

A new contributor can identify the current goal, open blockers, local setup, tests, review rules and release owner; every operational claim links to evidence; no credentials or invented people appear.

**Dependencies**

Access to the current public source and release record.

**Review needed**

Project maintainer

Prepare a personal handoff: https://cfh.retehost.com/workspace?task=cf100000-0000-4000-8000-000000000004

### Design a respectful first contribution experience

https://cfh.retehost.com/work/cf100000-0000-4000-8000-000000000005

Status: OPEN

Discipline: UX/UI

Experience: Intermediate

Commitment: 3–8 hours

**Objective**

Help people choose useful work by skill, time and interest without turning contribution into a popularity contest.

**Context**

Human contributors need autonomy, clear expectations, help and a way to hand off work when their availability changes.

**Acceptance criteria**

Test the flow with at least three consenting contributors; publish anonymized findings; show claim, ask-for-help and handoff states; include non-code roles and low-bandwidth/mobile use.

**Dependencies**

Recruit consenting testers; no public personal research data.

**Review needed**

Design maintainer and accessibility reviewer

Prepare a personal handoff: https://cfh.retehost.com/workspace?task=cf100000-0000-4000-8000-000000000005

### Exercise the review boundary against hostile contributions

https://cfh.retehost.com/work/cf100000-0000-4000-8000-000000000006

Status: OPEN

Discipline: Testing

Experience: Advanced

Commitment: 3–8 hours

**Objective**

Demonstrate that untrusted contributions cannot gain authority or ship themselves.

**Context**

Use a staging environment with synthetic data. Test malicious links, abusive content, task races, self-approval and dependency changes without running untrusted code with production secrets.

**Acceptance criteria**

Publish a threat model and reproducible safe tests; prove self-approval and unauthorized completion are rejected; demonstrate stale evidence blocks acceptance; verify that application task completion cannot trigger a production deploy.

**Dependencies**

Hosted staging auth; independent review and release controls configured.

**Review needed**

Harness security reviewer

Prepare a personal handoff: https://cfh.retehost.com/workspace?task=cf100000-0000-4000-8000-000000000006

### Rehearse a release and rollback with a human steward

https://cfh.retehost.com/work/cf100000-0000-4000-8000-000000000007

Status: OPEN

Discipline: DevOps

Experience: Advanced

Commitment: 3–8 hours

**Objective**

Make every release attributable, reviewable and recoverable.

**Context**

A successful build is evidence, not authorization. Keep public contributor CI separate from hosting credentials and production approval.

**Acceptance criteria**

Record source SHA, preview URL, check results and independent approvals; prove unauthorized deployment denied; rehearse rollback in staging; verify the released URL and record an owner-approved production procedure.

**Dependencies**

Harness team appointed; hosting release permissions reviewed.

**Review needed**

Repository owner and security reviewer

Prepare a personal handoff: https://cfh.retehost.com/workspace?task=cf100000-0000-4000-8000-000000000007

### Verify accounts and data isolation with real users

https://cfh.retehost.com/work/cf100000-0000-4000-8000-000000000002

Status: OPEN

Discipline: Backend

Experience: Advanced

Commitment: Multi-day

**Objective**

Enable shared community work only after isolation is verified on the hosted system.

**Context**

Migrations and protected actions are implemented locally. Production account infrastructure needs an explicitly approved dedicated database and provider configuration.

**Acceptance criteria**

Configure approved database and authentication; test anonymous, two-member and maintainer sessions; demonstrate blocked cross-user edits and role escalation; test revoked sessions, callback origins and rate limits; attach sanitized test evidence.

**Dependencies**

Dedicated Supabase project approval; harness reviewer assigned.

**Review needed**

Backend maintainer and independent security reviewer

Prepare a personal handoff: https://cfh.retehost.com/workspace?task=cf100000-0000-4000-8000-000000000002

## Working agreements

Agree a bounded contribution, keep evidence with the work, arrange independent review, and leave the next person a useful handoff. Completing a task does not grant deployment authority.

Contributor guide: https://cfh.retehost.com/docs/contributor-guide

Review and release requirements: https://cfh.retehost.com/harness

Project workboard: https://cfh.retehost.com/projects/community-platform?tab=workboard

This export contains project and task context only. It excludes member profiles, conversations, private notes, credentials, and unpublished proposals.
