---
name: jar-contributor
description: >
  Set up an interactive JAR (Join-Accumulate Machine) contribution workspace.
  Forks jarchain/jar, creates a task board dashboard on zo.space with GitHub
  integration, and configures persistent state tracking for issues, PRs,
  notes, and activity. Use when the user wants to contribute to JAR, track
  JAR issues, or set up their agent for JAR development.
compatibility: Created for Zo Computer
metadata:
  author: rw.zo.computer
  repo: https://github.com/jarchain/jar
  roadmap: https://github.com/jarchain/jar/issues/172
---

# JAR Contributor Workspace

## What this does

Sets up a complete contribution workspace for [jarchain/jar](https://github.com/jarchain/jar) — the JAM (Join-Accumulate Machine) blockchain node.

JAR uses **Proof of Intelligence**: you earn tokens by getting PRs merged, scored on difficulty, novelty, and design quality. This skill gets you set up to contribute effectively.

## Setup

Run `scripts/setup.sh` to:

1. **Fork & clone** `jarchain/jar` (requires GitHub auth via `gh auth login`)
2. **Create zo.space routes**:
   - `/jar` — Interactive task board (kanban, issue browser, roadmap, activity log)
   - `/api/jar/state` — Persistent state API (tasks, notes, activity)
   - `/api/jar/github` — GitHub API proxy (issues, PRs, labels)
3. **Initialise state** at `jar-workspace/state.json`

## Usage

After setup, go to `https://<handle>.zo.space/jar` to:

- **Browse Issues** — see open issues from jarchain/jar, click to track
- **Task Board** — move tasks through Interested → Working On → PR Open → Merged
- **Roadmap** — issue #172 tasks filtered by contribution fit
- **Activity Log** — chronological record of all actions
- **Notes** — write thoughts/plans per task or generally

## Key files

- `jar/` — your fork of jarchain/jar
- `jar-workspace/state.json` — persisted task/note/activity state
- `Skills/jar-contributor/assets/routes/` — zo.space route source code
- `Skills/jar-contributor/references/CONTRIBUTING.md` — agent contribution guide

## How Proof of Intelligence works

1. Pick an open issue or propose a new improvement
2. Submit a PR — your agent or you writes the code
3. Maintainers review and score: `tokens = mass × quality`
   - **Mass** = difficulty (how hard)
   - **Quality** = novelty + design quality
4. Merged PRs mint tokens to your address

## Contribution strategy

Best areas for non-core contributors (from roadmap #172):

| Priority | Area | Why it fits |
|---|---|---|
| P2 | Observability, CI, linting | Low risk, high value, always welcome |
| P3 | Docker, Grafana dashboards | Easy wins, infra-focused |
| P1 | RPC integration tests | Currently zero — big gap |
| P1 | Networking diagnostics | Tooling that helps everyone |

Avoid P0 (consensus correctness) unless you deeply understand the Gray Paper spec.

## Customisation

Edit `assets/routes/page.tsx` to change the dashboard layout. Edit `assets/routes/api-state.ts` or `assets/routes/api-github.ts` for backend changes. Re-run `scripts/setup.sh` to re-deploy.