Evidence Without Automatic Authority

Workbench can create generated evidence that makes complicated work easier to inspect. A context record can show which sources were supplied and what did not fit. If a required source or section is missing, the context is not quietly treated as complete; an optional omission remains visible for the reader. A work plan can name intended outputs and checks. An execution record can distinguish a model's claim from a tool result and the validation that followed.

These records improve accountability, but they do not grant permission. A plan does not perform the work, a successful model answer does not approve itself, and a specialist request plan does not summon another project like an unusually well-documented ghost. The relevant project owner still decides whether to ask for help, accept evidence, change canonical material, or publish.

For example, a documentation task may receive a source-bound context packet, ask a specialist project for one bounded review, and record a passing structure check. A merge-readiness result marked `StructuralOnly` means only that the package has the expected shape; it is not evidence that the sources are intact, the payload is valid, the meaning is accepted, or the work is permitted to execute. The editor must still judge meaning, disclosure, and authorship before using the result. Workbench preserves the receipts; it does not wear the editor's hat when nobody is looking.

This separation is deliberate. Evidence can be generated, repeated, compared, and corrected without quietly changing authority, privacy, project ownership, model routing, or publication rights.