A result is one part of a delivery
The report, brief, or artifact is what the user asked for, but it is not the full record of whether the task succeeded. The reviewer also needs to know what was checked, what was found, and what remained uncertain.
LibreTask packages those pieces together. The result is not detached from its proof.
Make acceptance concrete
Each criterion in the task contract should map to a visible result in the package. A structural check might pass automatically. A semantic check might require an evaluation and supporting evidence. A human decision should remain visible as a human decision.
When a criterion is not met, the package should say so. A complete record is more useful than a polished one that hides failure.
Keep uncertainty in the handoff
Open questions are not a defect in the model. They are information the next decision-maker needs. A source may be inaccessible, two documents may conflict, or a conclusion may depend on an assumption that only the user can validate.
The delivery package makes those issues explicit so acceptance is based on the actual state of the work.
A snapshot can outlive the product
The package should be exportable and stable. Markdown and JSON make it readable, archivable, and usable beyond the interface that created it.
A delivery is a durable handoff, not a temporary message.