Milestones
The Verifluence roadmap is organised into five milestones, each representing a shippable increment of the platform. Use cases are sourced from usecases.md and grouped by Actor within each milestone.
Click any milestone to expand its use cases.
M0
M1
M2
M3
M4
M-IS
M-IR
Milestone definitions
| Milestone | Theme | Goal |
|---|---|---|
| M0 — Escrow Solution | Smart Contract | HTLC contract deployed; all on-chain operations live |
| M1 — Streamer Onboarding | Streamer & Tracking | Streamers register, build a profile, connect a wallet, and get tracked on Kick |
| M2 — Operator Setup | Operators, Campaigns & Discovery | Operators onboard, deposit funds, browse streamers (tiered), and create campaigns |
| M3 — Deal Flow | Core Loop | Full apply → approve → allocate → deliver → pay → refund cycle; plus deal negotiation (typed terms, counter-proposals, HTLC funding gate) |
| M4 — Dashboards & Growth | Analytics & Scale | KPI dashboards, full Trust Score, conversion tracking, advanced filters, referral programme |
What the scores mean
| Score | Interpretation |
|---|---|
| 90–100% | Milestone is fully shipped |
| 60–89% | Core flows work; some edge cases or features missing |
| 30–59% | Partially implemented; main gaps present |
| 0–29% | Planned — not yet started |
Use case status key
| Badge | Meaning |
|---|---|
| live | Fully implemented |
| gaps | Partial — main flow works, edge cases missing |
| soon | Planned — not yet built |
Sources of truth
| Topic | Authoritative document |
|---|---|
| Domain model (entities, schema, status machines) | domain.md |
| Use case specs (flows, actors, preconditions) | usecases.md |
| Implementation bugs & audit findings | All 12 v3 findings resolved — no open bugs |
| Screen-level status & upcoming features | Screen Inventory |
| Deal negotiation UC spec — implemented | Proposal: Negotiation UC |
| Deal negotiation UI — implemented | Proposal: Negotiation UI |
| Operator API — account provisioning | Proposal: Operator API |
| Information Security (IS-9/10/11/12 done) | Proposal: Information Security |
Pages that overlap — what to use when
| If you want… | Go to |
|---|---|
| Which features are built vs planned (milestone view) | This page |
| What screens exist and their deploy status | Screen Inventory |
| Specific bugs and their fix status | All 12 v3 findings resolved — no open bugs |
| Detailed UC flows with preconditions and constraints | usecases.md |
| Entity schema + column-level detail | domain.md |
Open gaps (summary)
The table below consolidates open items across usecases.md.
| ID | Area | Description | Severity |
|---|---|---|---|
| — | all bugs fixed | All 12 findings from the implementation audit are resolved | fixed |
| — | Security | IS-9/10/11/12 implemented — one operational step remaining: set REQUIRE_SESSION_AUTH=true + SESSION_SECRET on VPS | deploy |
| — | Security | IS-1 Threat model, IS-2 Secrets manager, IS-3 Audit log, IS-8 External pentest | planned |
| — | Feature | Dashboard home pages (operator + streamer) | Planned |
| — | Feature | Conversion tracking snippet | Planned |
| — | Feature | Advanced streamer filters (score, viewers, GEO, language) | Planned |
| — | Feature | Negotiation — HTLC funding gate (UC-12.8) | Planned — M3 |
| — | Feature | Negotiation — activity log (UC-12.9) | Planned — M3 |
| — | Feature | Referral programme | Planned |
| — | Feature | Trust Score — Social & Track Record pillars | Planned |
| — | Feature | Operator API — streamer account provisioning | Proposal — spec |
| — | Feature | Twitch OAuth + stream verification | Planned |