Informational Fresh jira_story: GOV-135

Lesson 6 of 7 — Posture recompute and snapshot on change

Governance Workspace Core · Source: Jira Story GOV-135 (5 pts) · Authority: Informational (the Jira story is authoritative).

Purpose

Keep posture live by recomputing on change.

Why it matters

Posture that doesn't move as work completes is misleading.

Where this lives

Runs in the Customer AI Governance platform (components: workspace, shared). Task closure triggers a recompute that persists a new snapshot anchored to the baseline. Learn teaches this read-only.

Workflow

Given a task that closes
When posture recomputes
Then a new snapshot persists, anchored to the baseline history

Worked example

Several tasks close but the posture score never moves. What's likely broken?

The recompute-on-change step — closing work must produce a new baseline-anchored snapshot.

Acceptance criteria (authoritative — GOV-135)

Given a task that closes, when posture recomputes, then a new snapshot persists, anchored to the baseline history.

Common pitfalls

Recomputing without anchoring to the baseline, breaking trend history.

Knowledge check

Scenario: Several tasks close but the posture score never moves. What's likely broken?
Look for: The recompute-on-change step — closing work must produce a new baseline-anchored snapshot.

Key concepts

posture recompute
snapshot on change
baseline-anchored history

For the AI Tutor

Summary: Keep posture live by recomputing on change.
When to use: teaching or answering questions about "posture recompute and snapshot on change".
When NOT to use: the periodic signed review (that is GOV-136).
Key concepts: posture recompute, snapshot on change, baseline-anchored history.

Completion criteria

Learner passes the scenario knowledge check and can point to the system state that satisfies GOV-135's acceptance criterion.

Module: LEARN-MOD-003 (Governance Workspace Core)
Provenance: LEARN-MAP-001 · Generation standard: LEARN-STD-002
Next: LEARN-LSN-021