Milestone Evidence
How proof of delivery will work later
Funds release against delivery, not promises. This page previews how builders will submit milestone evidence and how reviewers and contributors will inspect it — nothing here is live.
Why evidence matters
Evidence is how delivery becomes visible and trust is earned in public. None of this is operational today.
Contributors can see what was delivered
Evidence makes delivery visible. Contributors will be able to look at the proof behind a milestone instead of taking a claim on trust.
Reviewers can inspect proof before approval
A reviewer will be able to check the submitted evidence against the milestone's claims before any approval is considered.
Builders create public accountability
Publishing evidence lets honest builders earn trust openly — delivery is shown in public, not asserted in private.
Settlement and returns depend on milestone state later
Milestone state is intended to inform settlement decisions in a later layer. No settlement, payout, or return is triggered here.
Evidence lifecycle
The planned path from submission to a later settlement decision. No step performs a real upload, review, or settlement today.
- 1
Builder submits milestone evidence
A builder would attach proof of delivery — links, images, a repository, or a written report — to a milestone.
- 2
Evidence is stored later
Submitted evidence would be stored in a later layer. There is no storage, upload, or database write today.
- 3
Reviewer checks claims
A reviewer would inspect the evidence and compare it against what the milestone claimed to deliver.
- 4
Reviewer requests changes or approves later
Based on the evidence, a reviewer would request changes or approve. No review action exists in this preview.
- 5
Contributors can inspect public evidence
Approved evidence would become public so contributors can inspect the proof behind each delivered milestone.
- 6
Settlement decision happens later
Milestone state would inform a later settlement decision. No settlement, payout, refund, or return is triggered here.
Evidence preview
Demo cards only. Every action button is disabled — nothing is uploaded, approved, or changed.
Studio sessions booked
Preview only- Evidence type
- Demo link
- Submitted by
- Demo builder
A link would point to a public schedule or booking confirmation. Demo content — nothing is fetched or stored.
First track mastered
Preview only- Evidence type
- Demo image
- Submitted by
- Demo builder
An image would show the mastered waveform or session. Demo content — no real file is uploaded or displayed.
Validator templates published
Preview only- Evidence type
- Demo repository
- Submitted by
- Demo builder
A repository link would show the published code. Demo content — no repository is read or verified.
Community summit delivered
Preview only- Evidence type
- Demo report
- Submitted by
- Demo builder
A short written report would summarise outcomes and attendance. Demo content — nothing is submitted anywhere.
Preview only — nothing here is live
- No real files are uploaded.
- No storage, S3, or IPFS is used.
- No database write happens; Prisma is not used in any app route.
- No review action is performed and no milestone is approved.
- No settlement, payout, refund, or return is triggered.
This page describes intended process only. Related previews: review workflow, admin preview, a demo campaign, and status & roadmap. Nothing here is legal, tax, or financial advice.