01
Why WEAVE exists
WEAVE Growth SPE began with a question: what if applications could be sustained through a financial and operating mechanism that reduces repeated one-off funding?
WEAVE steers Livepeer applications through their lifecycle.
A living operating layer for agent-assisted product work.
WEAVE helps agents and builders keep more application targets moving with light, explicit human supervision: from intent through research, selection, plan, engineering, QA, KPI setup, marketing, and evidence-backed iteration.
Mission & vision
Fee growth through repeatable application development Living system
02
Why now
Agents are becoming able to keep more useful targets moving in parallel than a single human can manually coordinate, while humans stay focused on intent, review, approvals, and judgment.
03
What compounds
The WEAVE runtime carries context, execution history, evidence, and lessons across app cycles, so each application can make the operating system around the next application better.
04
Target user
The first target user is a Livepeer application builder who needs to move from idea to shipped product, then keep improving that product based on evidence.
05
Network outcome
WEAVE was created as a fee-growth mechanism for Livepeer: a way to create, develop, distribute, and improve apps that can bring useful demand to the network.
06
Current proof
Askuno is the first proof app operated through the WEAVE lifecycle and is now live, reported publicly, and entering advertising/distribution.
WEAVE is designed to be living and evolving: the tool, runtime, applications, incentives, public reporting, and operating lessons improve together as evidence accumulates.
Lifecycle
From intent to evidence-backed iteration 8 stages + loopWithout WEAVE
Disconnected work
- Idea appears in a chat
- Research, code, QA, and GTM split across surfaces
- Evidence and decisions become hard to review
- Iteration slows down
With WEAVE
One lifecycle
- Capture intent, research, and selection
- Plan, engineer, and QA the app
- Set up KPIs, market, and gather evidence
- Iterate and analyze what the data shows
WEAVE is the wrapper around agent-run product work: it keeps the stage, plan, evidence, gates, KPIs, and iteration history visible.
M1 deliverables
Ready for review Scope · publicCanonical M1 scope
Month 1
The Month 1 deliverables define the public review scope: the WEAVE tool, the WEAVE runtime, and public KPI reporting. These are the artifacts now being submitted for review.
Month 1 scope →D1
WEAVE tool
A public tool/repo that packages the lifecycle method, app records, review surfaces, and operator interface direction.
WEAVE repo →D2
Runtime proof
A deployed runtime proof with Askuno as the first running application operated through the WEAVE lifecycle.
Askuno →D3
Public KPIs
A compact public dashboard for product and WEAVE operating signals, designed to report progress without exposing sensitive implementation detail.
KPI dashboard →Roadmap
Marketing, iteration, and incentives M2 · M301
Askuno distribution
WEAVE is now entering the advertising and distribution phase for Askuno while public KPIs track what happens next.
02
Second application
The next phase includes releasing the second WEAVE application and testing how the lifecycle works across more than one app.
03
Incentive layer
M3 is expected to begin opening WEAVE incentives to more builders, shaped by the evidence from M1, M2, and community feedback.
M2 focuses on improving WEAVE itself and running more GTM experiments. M3 is expected to broaden the incentive layer for app builders. The evolution of WEAVE is dynamic and evidence-led.