Fundable Futures Docs

Appearance

Reviews ​

Reviews are retrospective: finished work is submitted for owner approval. The owner checks each requirement, leaves feedback, and approves or requests changes. Money moves only on approval.

The review round ​

  1. The worker submits the task with a what-changed comment and links (PR, screenshots, artifacts).
  2. The owner opens the review form: each requirement gets a checkmark or a feedback note.
  3. Approve — the task completes and funding releases.
  4. Request changes — the task returns to in-progress with the feedback attached. Checkmarks persist into the next round, so already-passing requirements stay checked.

A requirement marked done stays checked on subsequent rounds. Resubmissions carry a what-changed comment with the PR link, so you can see exactly what's new.

Writing good feedback ​

Per-requirement feedback should say what's wrong and what "right" looks like:

✅ Good: "The export works, but dates land in column B instead of A — column A is empty." ❌ Bad: "Export is broken."

Feedback renders in the error theme color so it stands out. Review comments support replies, so you can have a thread per requirement.

Review history ​

Every round leaves a visible trail — public comments plus per-requirement feedback — shown in the review modal. Rejected-then-resubmitted work always carries its history. Even a rejection with a blank overall comment leaves a history entry, so there's never a silent round.

The critical-failure handbrake ​

When the entire feature appears to be missing, the owner can hit critical failure: one deliberate tap, a confirm step, and a single overall comment. No per-requirement comments needed. The worker sees it as a critical failure, not an ordinary rejection.

The handbrake hides once any requirement is checked done — at that point it's a normal review, not the handbrake.

Draft reviews ​

In-progress reviews save as drafts server-side, so you can start a review on one device and finish it on another. Drafts never appear in review history; submitting flips the draft to a real review. There's one draft per reviewer per task.

Auto-approval backstop ​

Reviews auto-approve after 3 business days if the owner doesn't act. The review queue shows a countdown per task (red within 24 hours), sorted soonest-to-auto-approve first. This keeps work from stalling on an absent owner.

If you need more time, open the review — any action resets the clock. The countdown is a backstop against forgotten reviews, not a deadline to fear.

The review queue ​

Project → Awaiting Review is your inbox:

  • Each task shows its countdown to auto-approval.
  • Tasks without a deadline sort last.
  • Open a task to see its artifacts (links clickable, images previewable, files downloadable) above the requirements.
  • Approve, request changes, or hit the handbrake — all from the review form.

Next steps ​