refinement-logger

To log refinement outcomes, trigger the logger after a review pass to generate resolution annotations on the report and an optional transcript. This preserves what changed and why for requirements, blueprints, or work orders.

Preserving review rationale is done by capturing resolution annotations and optional session transcripts. These artifacts document what changed and why, ensuring traceability and serving as precedent for future sessions.

Refinement logging maintains a traceable history of decisions by automatically annotating resolutions on review reports. It applies to any reviewed document in product management, ensuring governance and durable precedent.

You need a session transcript when a refinement pass results in precedent-setting decisions. The logger creates this optional transcript alongside mandatory resolution annotations to preserve the session's governance value.

Refinement logging works with any reviewed document, including requirements, blueprints, and work orders. It triggers after any refinement pass to capture changes and generate traceable artifacts.

Decisions lose context without formal logging. By generating resolution annotations and optional transcripts after refinement passes, the rationale behind changes survives the session for future traceability.