EXITR mechanics, in plain language.

$ what's in here

• how matching works (shallow → mid → deep)
• the 14-day countdown
• what you sign and when
• IP escrow, explained
• vesting + the 7-day rule
• success triggers (objective only)
• what happens when a project dies

$ how matching works

Three depths, run in sequence.

Shallow: SQL filters — tier ±1, skill overlap, availability, language, timezone. Sub-100ms. Returns top 50.

Mid: scoring pass on those 50 — GitHub complexity match, commit cadence, tier trajectory. Returns top 10.

Deep: Claude evaluates the top 10 against the full project spec. The spec is never exposed to candidates. Returns top 3 with written reasoning.

Founders pick depth at project creation: Fast (€99), Standard (€99), or Careful (€199).

$ the 14-day countdown

From the moment a founder posts a project, there are 14 days for a team to form. If the team forms, the redroom opens and the contract is signed. If 14 days pass without a full team, the project goes dormant — revivable for 30 days at €19, then archived. The countdown exists because side projects die in weeks, not months. Slow matching is no matching.

$ what you sign and when

You sign exactly once: at redroom join, after the team forms. It's a 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.

$ IP escrow, explained

HEIMLANDR (the entity behind EXITR) holds the IP in escrow. Not the founder. Not the dev. Not the platform. A neutral third party, structured for exactly this purpose. While the project is in flight, no one party can claim, sell, or weaponize the IP. When the trigger fires, ownership transfers atomically per the parameters everyone signed. When the project dies, the agreement expires and the IP returns to the original contributors.

The escrow exists because trust between strangers can't be assumed in 14 days. So we don't ask anyone to trust anyone — we just hold the keys.

$ 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 it objectively from commit history, redroom presence, and async check-ins. No subjective "are they really contributing?" calls. No drama.

$ success triggers (objective only)

The founder picks the success trigger at project creation. It must be objective — meaning a third party can verify it without asking anyone how they feel. The three accepted triggers at v0:

• Stripe revenue threshold (e.g. €10k cumulative MRR)
• Priced funding round (term sheet signed)
• Acquisition LOI (letter of intent received)

No "I declare this successful." No founder mood. The trigger fires from data, or it doesn't fire.

$ what happens when a project dies

Most projects die. That's not a failure of EXITR — it's the entire reason EXITR exists. When a project dies:

• The contingent agreement expires automatically. No legal weight.
• Each contributor keeps the code they wrote. No license claims.
• The founder keeps the spec. The brief is delisted.
• Devs keep their tier, their match history, and their platform access.
• Nothing has to be unwound. Nothing has to be litigated. It just ends.

98% of side projects don't ship. We built EXITR around that fact, not against it.