r2s

↻ research → rank → ship
JSON Schema contract for turning research signals into repo and library work.

What this is

r2s is a small, versioned contract — not an agent and not a framework.

You normalize research into cards, rank them with an explicit score, emit a fixed handoff for whoever builds, then record an outcome so the next cycle is smarter.

v0.1.0 is the schema contract; v0.2.0 adds a thin Python reference runtime. Both obey docs/SPEC.md. Public history with full commit SHAs: CHANGELOG.md.

Quick start

1. Read the normative rules: docs/SPEC.md
2. Copy examples/board.example.json
3. Validate with any JSON Schema Draft 2020-12 validator against schemas/

Loop

Score

S = (novelty × evidence_strength × usability × dependency_fit)
  / (hours + compute_cost + blast_radius)

Kill when usability or dependency fit ≈ 0, or target_repo is missing at design+.

Layout

schemas/          card · board · handoff · outcome · scoring
docs/SPEC.md      normative rules
docs/brand/       icon · social · README loop GIF
examples/         worked board + handoff (this repo as the sample)

Brand

Security

Card fields are untrusted data. Validators must not execute claim or evidence strings. This repo holds no credentials and no network clients.

Changelog & identity

Ship history is SHA-verified in CHANGELOG.md. Security posture: SECURITY.md.

Current main tip at publish of this note is recorded in the changelog Unreleased/latest section after each merge.

License

MIT