Features vs Flows
Dynvo describes a codebase with two primitives. Every metric in these docs is computed against one or both of them.
A capability of the product. Dynvo emits two grains. An engineering feature is a code-grounded module or package boundary — “auth-middleware”, “webhook-processor”, “qr-code-generator” — what an engineer would name from the repo's structure. A product feature is the customer-facing capability those roll up into — “Multi-factor authentication”, “Stripe Checkout” — what a PM would name from the marketing site.
A complete user-facing action threaded through the code — “Create Project”, “Reset Password”, “Cancel Subscription”. Each flow has an entry-point file and line, its contributing files, and is attached to one or more features. A feature is what the code is; a flow is what a user does with it.