Report to Keep

Promotion is a retention decision, not an authority decision.

Default

Operational reports are ephemeral by default. Reviews, failed or passed gates, design validation, diagnostics, research notes, and similar execution artifacts belong under ephemeral-reports/ when they need file persistence.

Do not promote a report merely because it is useful during the current workflow.

Method

1. Load report-lifecycle, then use OKF-MCP to locate and read the intended report. Do not recreate report discovery in Loom.
2. Require the source to satisfy the shared ephemeral-report contract and have no OKF validation errors.
3. Confirm the source lives under ephemeral-reports/, then decide whether the report itself has lasting documentary or audit value.
4. If only a conclusion, requirement, design rule, architectural constraint, or user instruction is durable, route that knowledge to the role that owns the proper governed document instead of promoting the raw report.
5. If the raw report deserves retention, choose a non-colliding destination under docs/reports/<producer>/ matching the source producer namespace.
6. State explicitly that the report's semantic authority remains unchanged by the retention decision, whether it stays ephemeral or is promoted.
7. If promoting, call loom_report_promote with source, destination, and a concise reason.