How the Dev Crew Works

The Dev Crew is the cooperative's contribution pipeline. Every accepted contribution earns Marks at the cooperative clearing rate (10% for work, 5% for purchase activity), gets stamped to the IP Ledger with your Ring Bearer Ed25519 signature, and accrues toward patent-floater eligibility from the 240-pool reserved for contributing developers.

The pipeline: Fork → Build → Submit via Battery Dispatch → Star Chamber validates (compile + test + spec compliance, automated, no human gate) → Member vote accepts or rejects → IP Ledger attribution stamped, immutable across the Frontier Mesh → Marks accrue → patent-floater eligibility credited.

You cannot buy your way in. Participation and contribution determine eligibility.

Bounty Tiers

NANO — 0.05 Mark

Small scoped contributions: documentation fixes, test coverage, minor UX polish, bug reports with repro steps.

CORE — 1 Mark

Meaningful code contributions: new feature implementation, significant bug fix, performance optimization, integration work.

ULTRA — 10 Marks

Transformative contributions that measurably lift benchmark scores or unlock a new capability. 240-floater patent pool eligibility.

Open Bounties

ULTRA Posse Sub-Claim Splitter v2 10 Marks · floater eligible

Improve the Posse decomposition primitive: the sub-claim splitting logic that fans a hard question into sub-claims for swarm agents. Current implementation is version zero. Target: lift MMLU-Pro score from 61.9% toward ≥90% on the 42-question canonical run. Empirical receipt required — show before/after score on canonical 42Q.

Acceptance criteria
  • Sub-claim split quality measurably higher (Bishop + Star Chamber validate)
  • ABSTAIN cascade fires at correct confidence threshold
  • Round-Up reconciliation receives well-formed sub-answers
  • Canonical 42Q score improves from current 61.9% baseline
  • All tests pass; no SQLite syntax introduced
CORE Mesh Diff Replication Loop 1 Mark · floater eligible

Implement the 15-minute Merkle-diff replication loop for ip_ledger_merkle_diff (Postgres). Diff against Circle of Influence peers, replicate new entries, respect battery-aware default-OFF canon. Composes with peer_artifact_server.ts existing infrastructure.

Acceptance criteria
  • 15-min interval fires correctly
  • Merkle root computation matches between simulated 2-peer exchange
  • Battery-aware pause works (no loop when on battery, resumes on AC)
  • ip_ledger_merkle_diff rows written correctly
  • Unit test: 2-peer diff simulation passes
CORE Star Chamber Variance-to-Risk Calibration 1 Mark · floater eligible

Calibrate the H = Variance/100 risk scoring formula against the MMLU-Pro 42Q canonical run. Document which question domains produce highest variance (highest hallucination risk). Output: calibration report + recommended threshold adjustments for the 15% risk threshold.

Acceptance criteria
  • H scores computed for all 14 MMLU-Pro domains
  • Threshold recommendation backed by empirical receipt
  • Report format: domain · mean H · recommended flag threshold
  • Reproducible: another agent running same inputs gets same H scores (±0.01)
NANO IP Ledger UI — Verifiable Proof Download 0.05 Mark

Wire the 'Download Verifiable Proof' button in MyIPLedgerTab.tsx. Output: a JSON file containing the entry, its Ed25519 signature (Ring Bearer signed), the Ring Bearer public key, and a timestamp. File must be self-verifiable using node:crypto without any cooperative infrastructure.

Acceptance criteria
  • Download button produces valid JSON file
  • JSON contains: entry_id · payload_hash · signature_ed25519 · ring_bearer_pubkey · stamped_at
  • Verification script (included in download or documented) confirms signature using node:crypto
  • Works in Electron renderer without main-process round trip on the download trigger
NANO Battery Dispatch — Code Contribution Submit Flow 0.05 Mark

Add 'Submit Code Contribution' tab to Battery Dispatch UI. Fields: title · description · link (GitHub PR or paste) · bounty_id (optional). On submit: write to ip_ledger_entries via stamp_certify.ts auto-stamp hook. Receipt shown to contributor with their ledger_id.

Acceptance criteria
  • Tab renders in Battery Dispatch without breaking existing tabs
  • Form validates: title required · link required
  • Submit triggers stamp_certify auto-stamp hook
  • ip_ledger_entries row written with contribution_type = 'battery_dispatch_submission'
  • Ledger ID shown in success receipt to contributor

How to Submit

  1. Fork the canonical repo (link published with Dev Crew Open Call)
  2. Build your contribution locally — all tests passing, no SQLite syntax
  3. Open MnemosyneC → Battery Dispatch tab → Submit Code Contribution
  4. Star Chamber validates automatically (compile + test + spec compliance)
  5. Member vote accepts or rejects via Substrate Market
  6. IP Ledger attribution stamped — Ed25519-signed, immutable, portable
  7. Marks accrue at cooperative clearing rate

Questions? Read the How It Works page or reach out via Social@lianabanyan.com.

IP Ledger Attribution

Every accepted contribution is stamped to the IP Ledger — an append-only, Ed25519-signed record that persists regardless of platform fate. Your Ring Bearer public key is your permanent proof of contribution. The ledger replicates across the Frontier Mesh (Circle of Influence peers) via Merkle-diff exchange, so your attribution is not held by any single server. You can download your verifiable proof at any time from the My IP Ledger tab in MnemosyneC.

Last updated: 2026-06-23 · BPBP092