Problem
The Taskly migration doc defines stop-rules tied to measurable budgets ("startup time", "bundle size", "RPC latency must not be materially worse than duplicated native logic") — but rivet ships no tooling to measure any of them. Budgets without measurement hooks are opinions.
Proposed fix
A raco rivet measure command that, for a given host app build, reports:
- cold start time (process spawn → first RPC answered)
- staged bundle size (total + breakdown)
- per-RPC latency percentiles over a scripted workload
Numbers first; enforcement/gates can layer on top later (e.g. exit code thresholds for CI).
RIVET-LIB-BACKLOG item 6 (P2).
Problem
The Taskly migration doc defines stop-rules tied to measurable budgets ("startup time", "bundle size", "RPC latency must not be materially worse than duplicated native logic") — but rivet ships no tooling to measure any of them. Budgets without measurement hooks are opinions.
Proposed fix
A
raco rivet measurecommand that, for a given host app build, reports:Numbers first; enforcement/gates can layer on top later (e.g. exit code thresholds for CI).
RIVET-LIB-BACKLOG item 6 (P2).