No cold start
A marketplace needs buyers and sellers before it is useful to either. Your team is already both sides on day one.
// mode 02 — team
Your AI capacity runs out
mid-task. The task doesn’t.
GoDone team mode is a private task space for one engineering team: when a developer runs out of AI capacity mid-task, they hand it back with a checkpoint and a colleague with capacity left finishes it — with points instead of money.
status: backend built and tested · interface in progress · pilot on our own team
The relay — five steps, and nothing is lost.
One person hits their limit at four in the afternoon with the work half done; another has capacity to spare and nothing urgent. Team mode connects those two moments.
01
Checkpoint
What is done, how to continue, the branch or the work in progress, and roughly how far along it is.
02
Hand off
The task goes back to the team pool with the reason attached. Everything delivered so far is kept.
03
Pick up
A colleague with capacity claims it and downloads one archive — the spec, your checkpoint and the prior artifacts. They attach it in their own AI tool and write GO.
04
Finish
They submit the result. The same QA agent checks it against the same acceptance criteria.
05
Both credited
You earn points for handing off cleanly, they earn the completion. The relay chain stays on the task.
Why this mode launches first.
No payments risk
Colleagues are not customers. Points and achievements replace escrow entirely — an org task can never create one.
Trust is already there
Disputes between strangers need an arbiter. Between colleagues they need a team lead, which you already have.
What is inside.
Four parts, plus the archive that carries a half-finished task from one person to the next.
The shared pool
Tasks are visible only to the team — a hard tenant boundary, checked on every request. Inside the team every member both posts and picks up work; your public role does not apply here.
The same two agents
The intake agent turns a plain-words request into a spec with acceptance criteria and a token estimate. The QA agent grades the result per criterion and escalates to a human when it is unsure.
Points, chat, leaderboard
An append-only ledger — no counter to drift. Weekly and monthly boards computed on read, achievements derived from the ledger so they cannot be handed out by favour.
The same legal core
Colleagues must not swap accounts either. A hand-off note or chat message offering a login, key or session is rejected — in English and in Russian.
the handover artifact
The GO-package, with a relay file
The colleague who picks a task up downloads one archive — order card, super-prompt, acceptance checklist, materials and quality standards — attaches it in their own AI tool and writes GO. Built by the same code as the public marketplace, with two differences: the reward is points, and RELAY.md carries the previous person’s checkpoint so nobody restarts from zero.
Rewarding the behaviour that keeps work moving.
Completing your own task earns nothing. Posting a job and then finishing it yourself is not a favour to the team, and paying for it would make the leaderboard meaningless. The same goes for handing a task off and immediately taking it back.
The full points table
| What you did | Points | The rule behind it |
|---|---|---|
| Finished a colleague’s task | 50 / 75 / 100 / 150 | By difficulty: easy, medium, hard, expert. Only on acceptance. |
| Picked up a stalled task | +20 | Resuming someone else’s hand-off is the behaviour the mode exists for. |
| Handed off cleanly | +15 | Needs a real note plus evidence — a bare “gave up” earns nothing. |
| Passed QA first time | +10 | Rides on the completion when the agent’s verdict is a clean pass. |
| Posted a build-ready brief | +10 | Only if the spec is actually checkable: criteria, a description, a prompt. |
| Saved a checkpoint | +5 | Capped per task per day, so it cannot be farmed. |
| Kept a weekly streak | +25 | Awarded once a week, and only if you also delivered the week before. |
Achievements you can earn
FounderFirst briefGood colleagueClean hand-offRelay runner — 5 resumesCheckpointer — 10 savedGreen QA ×3Ten doneFour-week streakReviewer — 10 acceptedTeam voice — 100 messages
Every badge is derived from the ledger, so none of them can be granted by hand — not even by the team owner.
What exists today, honestly
Built and proven end to end. Teams and invites, dual roles, the shared pool, checkpoints, the hand-off, resuming with credit, delivery through the same code path as the public marketplace, the QA verdict, acceptance, points, leaderboard, achievements and chat. The full relay — one developer hands off, another finishes, both are credited — runs through the real API in the test suite.
Verified, not asserted. 382 automated tests pass and 242 money scenarios run with zero settlement-invariant violations. Team tasks are proven never to create an escrow record and never to touch the money-core counters.
Not there yet. The team interface is still being built, so there are no screenshots on this page — we would rather show nothing than dress up the marketplace screens as something they are not. Sign-up is not open; the first pilot runs on our own engineering team.
Questions people actually ask.
Does team mode use real money?
No. Points and achievements only. An org task cannot create an escrow record — that is enforced in code and covered by tests, not left to convention.
Does a colleague need access to my AI account?
Never. They pick the task up with the spec and your checkpoint and run it on their own account. The credential-sharing guard applies between colleagues exactly as it does between strangers.
Can the same person post and pick up tasks?
Yes — that is the point. Inside a team everyone is both sides. Your public marketplace role has no effect here.
What happens if someone leaves the team?
Any task they were holding returns to the pool with a hand-off note, so nothing is stranded behind a departed account.
Want the other side? The public marketplace is the same machinery with strangers instead of colleagues, and USDT escrow instead of points — with five real screens of the working build.