$ room

The redroom — where the team builds, and the AI is in the conversation.

Once a team forms, you sign once, you enter the room, and you ship. The AI mediator joins in v0.4 — for v0, the room is a meeting link plus the contract. Lying gets you outvoted. Missing a standup doesn't.

$ what's in here

$ what you sign and when

You sign exactly once: at room join, after the team forms. One-click signature on a contingent assignment. The contract sits dormant. It does nothing until the success trigger fires — at which point it does everything atomically.

You don't sign at install. You don't sign at interview. You don't sign at match. You don't sign at ping accept. You sign once, at the moment a real team commits to a real build.

More on what the contract actually does → the trigger.

$ the AI mediator

v0 status: the redroom is a meeting link (Meet, Discord, Zoom — your call). Real-time AI mediator + custom UI land in v0.4. What's below is the design intent.

In v0.4, an AI is present in the room at all times. Its job:

$ the guild — outvotes are about behavior, not skill

The team (the "guild") can outvote any member at any time. Anonymous. Triggered by lying, ghosting, bad faith — not by skill gaps. A junior dev who's learning isn't outvoted. A senior dev who lied about their stack is.

Outvotes feed your behavior tier on your dev profile. Many outvotes = fewer pings, demotion to Open platform tier, eventually pool removal.

This is how the platform stays clean without manual moderation. The platform doesn't decide — the team does.

$ vesting + the 7-day rule

Vesting is weekly, baked into the contract. Show up, ship, vest. The 7-day rule: if you go 7 days inactive without an agreed reason, you forfeit your unvested portion.

The AI mediator tracks "active" objectively from commit history, room presence, and async check-ins. No subjective "are they really contributing?" calls. No drama.

Planned breaks (parental leave, holiday, conference week) are agreed upfront and don't trigger the rule.

$ recordings + consent

The room is recorded. Why: IP enforcement at success trigger, dispute resolution, anti-ghosting evidence, anti-fraud either side, regulator audit response. Recording-consent is explicit at room entry — continuing into the room equals consent.

Retention is tiered:

GDPR-default. Right to access, deletion, and portability. Disputes don't go to opinion. They go to the recording.