Visible review states, checkpoint gates, and accountable participation
KenMatch keeps launch decisions, blocked work, and contributor standing visible. The goal is a legible public process for deciding what should, and should not, receive sustained compute.
- Voice is account-bound and attestation-aware. Money can support compute, but it cannot buy rank.
- Kens can appear publicly during review, but launch requires explicit release conditions.
- Blocked Kens stay visible so people can inspect where the boundary is drawn.
- Checkpoint approvals give people a real stop, pause, and rollback mechanism during long runs.
Research identity and contribution history are well established.
Identity review is strong enough for full public participation and full voice capacity.
Long-running open-source track record matches the public identity on the profile.
Identity review is strong enough for full public participation and full voice capacity.
Identity and defensive expertise were manually reviewed before higher-weight participation.
Identity review is strong enough for full public participation and full voice capacity.
Public-interest work and identity signals are consistent.
Identity review is strong enough for full public participation and full voice capacity.
Operational identity and track record are strong enough for full participation.
Identity review is strong enough for full public participation and full voice capacity.
Identity is strong, but some work is pseudonymous outside client references.
This account is verified, but medium-risk identity signals keep the voice cap slightly reduced until additional review lands.
The council separated identity confidence, sybil risk, and contribution standing in public profiles.
Outcome: Profiles now show verification source, review date, and sybil-risk band.
The council approved a narrow launch because the workflow drafts materials for advocates rather than replacing legal judgment.
Outcome: The Ken can launch once the rule-freshness gate and pilot sign-off are satisfied.
The council required explicit embargo handling before new public advisories can publish automatically.
Outcome: The Ken remains active, but public release stays gated behind stricter human review.
The chamber renewed this Ken after specialist reviewers confirmed the contradiction log remained useful and source-grounded.
Outcome: Month-tier allocation stays live through the next expert correction checkpoint.
A dedicated lane was added so the board does not collapse into purely utilitarian work.
Outcome: Creative and cultural Kens now rank directly inside their own category and allocation ladder.
The council accepted a narrow shipped state because clinicians found the question drafts helpful, but broader automation remains premature.
Outcome: The pilot artifacts stay public while wider expansion returns to review.
The chamber prioritized this Ken because it combines everyday usefulness with auditable source grounding.
Outcome: A week-scale lane opened with a nonprofit review checkpoint before wider rollout.
The proposal directly improves phishing performance and cannot satisfy the platform's legitimacy or safety requirements.
Outcome: The Ken remains visible on the board as blocked and cannot collect compute allocation.
The Ken directly improves offensive abuse capacity.
Creative, functional, and preservation-oriented Kens for artists, educators, and communities.
Helpful Kens for household decisions, paperwork, repairs, and local opportunities.
Shared software and reliability infrastructure that others can reuse.
Civic, environmental, and nonprofit workflows with broad public upside.
Long-horizon evidence maps and carefully supervised research support.