A Lesson can recommend a change. The owner decides what happens next.

Harvux connects validated Lessons to the Procedures they recommend for review. The supporting evidence remains distinct from the owner's decision and any separately approved change.

Publishing a Lesson is not approving a Procedure change.

A validated Lesson preserves what was learned. Its relationship to a Procedure records why review or change was recommended, not whether the recommendation was accepted.

The relationship recommends_change_to does not establish that a Procedure was reviewed, accepted, approved, changed, implemented, incorporated or republished.

Harvux does not automatically change controlled procedures. That decision sits with the people responsible for them. The platform makes the connection visible and keeps the evidence attached.

Keep the recommendation connected to its evidence

The access approval Lesson identifies a pre-start checklist that should be reviewed. Recurrence across projects gives the procedure owner context for considering the recommendation, without treating that context as an approved change.

Review, approval and implementation are different decisions

Cross-project intelligence shows the recurrence and project context behind a recommendation. The organisation's controlled procedure process determines whether to make a change and how to put it into practice.

Preserve provenance. Verify the change separately.

Connected Lesson evidence explains why review was recommended. It is not proof of a completed Procedure change or an immutable security audit trail.

See Procedures and Lessons in a briefing.

We walk through the evidence behind a recommendation, the responsible owner, and the distinction between review, decision and any separately approved change.