Product Specification
Avorelo already structures work into contracts with scope, proof tier, approval policy, and safety boundaries. That means there is real product-specification behavior in the kernel today, even though it is not a standalone PRD authoring system.
What exists today
Tasks are converted into work contracts before the rest of the system runs. Those contracts define route, risk, proof tier, approval policy, and safety boundaries that downstream capabilities must respect.
Claim boundary
Product Specification structures work intent and scope boundaries. It does not replace a full product management suite and does not claim to generate complete PRDs automatically.
What it does not do
There is no dedicated visual editor, backlog system, or shipping roadmap engine here. The capability is the contract layer that keeps execution and review aligned to the task.